eww, please install syslogd from somewhere.

note that technically a device reboot is not the browser's fault. it means that
the os failed to respond in a timely manner (something like 30s or 1min) to a
watchdog.

the search feature is something that i had written but was helpfully destroyed
before it made it into the sources and i never got back to rewriting it. it's
not relevant to this bug.

note that it's a good idea for you to be a lot more specific and a lot less
wandering when you report bugs. you mention the internal search feature which
generates a very short error page. and then you talk about searching for text.
which presumably involves using the find toolbar, but you didn't specify.

also, when filing bugs, please indicate whether you wait for a page to finish
loading before you take an action.

> eww, please install syslogd from somewhere.

I did and it crashed to fast to produce output, or the version from debian was
unreliable.  

>note that technically a device reboot is not the browser's fault. it means that
>the os failed to respond in a timely manner (something like 30s or 1min) to a
>watchdog.

Lot's of other things can cause a hard crash.  

> the search feature is something that i had written but was helpfully destroyed
> before it made it into the sources and i never got back to rewriting it. it's
> not relevant to this bug.

From the UI it appears that the two are intertwined.  I'm not assessing cause
I'm reporting affect. 

>note that it's a good idea for you to be a lot more specific and a lot less
>wandering when you report bugs. you mention the internal search feature which
>generates a very short error page. and then you talk about searching for text.
>which presumably involves using the find toolbar, but you didn't specify.

Yeah I guess 20 years in the business and 12 working with distro's hasn't
prepped me.  I was searching for text yes.  Since it's a page of text this is a
good thing to search for.  Search also seems to be initiated when you click on
an item on the page as both reproduce the same 1st grade English error message. 

>also, when filing bugs, please indicate whether you wait for a page to finish
>loading before you take an action.

I didn't think you would need to have hung explained.  This means that no
matter how long you wait the page never finishes loading.  

I really think that filing bugs here is a real waste.  It's an attitude thing
worse than the mplayer team....I'm closing the bug.  Thanks.

sorry. here's a definition of hang:the browser user interface including menus
and toolbars are visible but do not respond. it is impossible to close the
browser. using an external application (bookmarks, skype, rhapsody, chat) to
trigger a link does not cause the browser to load a new page.if what you did
was click search, get the stupid error that was written by a non native
speaker, then that's all there is, there's no implementation and there is no
remaining content. that is not a hang. it's just that about:config's search
results in a null page. You can still load any other page you like.If using the
find toolbar's green find arrow causes a hang as I've defined hang above, then
that's a serious problem.on my device it takes about 12s for about:config to
load completely. and it doesn't load incrementally, so that's just what it is.

oh, in case you care, the search feature is already removed in current
versions. i have absolutely no idea why that failed to be put into the public
release.

finally spent the time researching it. the childish error was added because a
contractor thought the feature was missing, the error broke the feature and
confused everyone. the root cause was that the about: protocol doesn't support
the search property. Once the equivalent of search is collected from location,
the feature works.