Closed
Bug 496081
Opened 16 years ago
Closed 16 years ago
[Crash] nsHTMLTokenizer::ConsumeStartTag when using built-in amazon search plugin or searching on amazon website
Categories
(Core :: DOM: HTML Parser, defect)
Tracking
()
VERIFIED
INVALID
People
(Reporter: TheOne, Unassigned)
Details
(Keywords: crash)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; de; rv:1.9.0.10) Gecko/2009042316 Firefox/3.0.10
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; de; rv:1.9.0.10) Gecko/2009042316 Firefox/3.0.10
I have a fully reproducible crash when you use the built-in amazon.de seachplugin in Fx 3.0.10 german.
Crashes even in safe mode, tried different profiles, even fresh ones.
Reproducible: Always
Steps to Reproduce:
1. Use a german version of Firefox (not tested with other languages)
2. With the amazon.de searchplugin, search for: macbook pro
3. See the crash
Actual Results:
http://crash-stats.mozilla.com/report/index/7ca21cf7-bc8a-4dee-a588-59ad22090603
http://crash-stats.mozilla.com/report/index/be75f848-5c78-47e7-98fb-871042090603
http://crash-stats.mozilla.com/report/index/e0ee90d2-3750-40c0-8906-ed7ca2090603
http://crash-stats.mozilla.com/report/index/3c8f2285-73fa-450f-b2b3-798fd2090603
| Reporter | ||
Updated•16 years ago
|
Version: unspecified → 3.0 Branch
| Reporter | ||
Comment 1•16 years ago
|
||
Having this further investigated, this happens too, when just using the search field on the amazon website, entering any search term you want!
And this is not limited to the german amazon, it's also reproducable with amazon.com.
| Reporter | ||
Updated•16 years ago
|
Summary: [Crash] nsHTMLTokenizer::ConsumeStartTag when using built-in amazon search plugin (german version) → [Crash] nsHTMLTokenizer::ConsumeStartTag when using built-in amazon search plugin or searching on amazon website
Updated•16 years ago
|
Component: Search → HTML: Parser
Product: Firefox → Core
QA Contact: search → parser
Version: 3.0 Branch → 1.9.0 Branch
Comment 2•16 years ago
|
||
That works fine for me with Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.0.10) Gecko/2009042316 Firefox/3.0.10 (.NET CLR 3.5.30729)
Reporter, can you please try to start Firefox in Safe Mode (http://support.mozilla.com/kb/Safe+Mode) and check if this still happens? Just to make sure no add-on is causing this problem. If it's still crashing please create a fresh profile (http://support.mozilla.com/en-US/kb/Managing+profiles) and check again. Thanks.
| Reporter | ||
Comment 3•16 years ago
|
||
(In reply to comment #0)
> Crashes even in safe mode, tried different profiles, even fresh ones.
Already did that!
Comment 4•16 years ago
|
||
Oh, right. So does it also crash with a recent Minefield or Shiretoko builds?
| Reporter | ||
Comment 5•16 years ago
|
||
(In reply to comment #4)
> Oh, right. So does it also crash with a recent Minefield or Shiretoko builds?
No crash with 3.5b4
Comment 6•16 years ago
|
||
Ok, so it's 1.9.0 only. Good to know. Have you also tested another Firefox 3.0.10 locale (en-US would be preferred)? If I get it somehow reproduced I could try to debug this crash.
Oh, and can you please check if any plugin could be the fault here? As what I can see those don't get disabled in safe mode. It will be unlikely but making sure.
Comment 7•16 years ago
|
||
Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.0.12pre) Gecko/2009060205 GranParadiso/3.0.12pre
No crash here with the STR from comment 0.
| Reporter | ||
Comment 8•16 years ago
|
||
1. Freshly downloaded en-US and de-DE setups.
2. Uninstalled de-DE version, installed en-US: no crash
3. Uninstalled en-US version, installed de-DE: no crash
Does anyone have an explanation for this? Firefox folder has been completely deleted after unistall and before install of another version/locale.
Are the crashreports from comment 0 helpful for you in any way?
Comment 9•16 years ago
|
||
We will check on IRC how to get the crash reproduced. We will report back when we have the results.
Comment 10•16 years ago
|
||
Ok, the reporter has a couple of memory failures while running memtest86. Looks like it is not our fault and at least one memory bar is broken.
| Reporter | ||
Comment 11•16 years ago
|
||
Yes, it was a defect memory bar. I removed it from the system and tested with various profiles, no more crashes.
Sorry for the inconvenience.
| Reporter | ||
Updated•16 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → INVALID
Comment 12•16 years ago
|
||
That's fine. Could have also been caused by us. So now it is clear. Let's verify.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•