CPU pegged for archive message from Google search using Firefox

The following link gives me no problems.
http://archive.midrange.com/midrange-l/200608/msg00004.html

:: Skip to [][][] bottom of this message. Between there and here is just my debugging the problem.

However from the Google search [first link] noted below, if I open the link identifying that same message [by flyover, the same URL as above] or even choose to open the cache link, my CPU climbs to 100% using Mozilla Firefox 3.0.8.

http://www.google.com/search?hl=en&lr=&as_qdr=all&num=100&q=ATCONTXT+&btnG=Search

If I locate that message using a less verbose search, then there is no issue; the first link is rewritten as the second. In this case the obviously missing "&lr=&as_qdr=all"; not sure what &lr and &as_qdr refer to, or if indeed that might be origin.? Any ideas?

http://www.google.com/search?q=ATCONTXT
http://www.google.com/search?hl=en&num=100&q=ATCONTXT&btnG=Search

Also reproduces... Seems narrowed to as_qdr or the '+' so far...
http://www.google.com/search?as_qdr=all&q=ATCONTXT+&btnG=Search

Also reproduces... Arghh! Seems that /plus/ symbol causes it!
http://www.google.com/search?q=ATCONTXT+

Now if only I could figure out where that character came from. I do recall an intermediate search where I had some "OR" criteria added, but I do not recall how I got back to the search without. I thought it was back in the _Advanced search_ panel.

[][][]

Yepper! When I removed the extra criteria from the search using the Advanced search page, the text in the URL after I clicked the Advanced search button from that page then had the extraneous '+' symbol. So two questions remain. 1> Any idea why the '+' symbol is causing the CPU issue? 2> Is there a /report problem/ link for Google search [the search /quality form/ seems somewhat off-base given its _list of concerns_ limited choices, where all seem to relate only to content, but perhaps that is the best option]?

I guess I will use that available feedback, but still curious if there is anything else. I guess I will also include a link to this message in the archive.

Regards, Chuck