381261 - Yahoo UK sometimes causes crash [@ MarkGCThingChildren] [@ nsViewManager::HandleEvent]

Status: RESOLVED WORKSFORME

(Firefox :: General, defect)

Description

[Dan Soper]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3

Sometimes, visiting Yahoo's UK homepage makes Firefox 2 crash. This behaviour seems to be new to FF2 - I did not see it in 1.x.

Reproducible: Sometimes

Steps to Reproduce:
1. Go to above URL
2. Firefox is redirected to http://uk.yahoo.com/index_narrow.html
3. The page downloads and begins to render

Actual Results:  
Firefox crashes - sometimes without any GPF message or Talkback dialogue.

Expected Results:  
Page loads as normal.

Talkback IDs: TB32244673K TB31211987Y
This crash has also happened without any GPF or TalkBack or anything else: the Firefox window just disappeared.

Session-restore doesn't quite work as it should either, it tends to give me the page I was on before going to Yahoo, even though the Yahoo page had downloaded and (partially) rendered.

Comment 1

[Steve England [:stevee]]

Incident ID: 32244673
Stack Signature	MarkGCThingChildren 3094eb6a
Product ID	Firefox2
Build ID	2007030919
Trigger Time	2007-05-17 14:33:23.0
Platform	Win32
Operating System	Windows NT 5.0 build 2195
Module	js3250.dll + (0001f86b)
URL visited	uk.yahoo.com/index_narrow.html
User Comments	Loading above page.
Since Last Crash	386160 sec
Total Uptime	840663 sec
Trigger Reason	Access violation
Source File, Line No.	c:/builds/tinderbox/Fx-Mozilla1.8-release/WINNT_5.2_Depend/mozilla/js/src/jsgc.c, line 2065
Stack Trace 	
MarkGCThingChildren  [mozilla/js/src/jsgc.c, line 2065]
js_MarkGCThing  [mozilla/js/src/jsgc.c, line 2452]
js_GC  [mozilla/js/src/jsgc.c, line 2887]
JS_GC  [mozilla/js/src/jsapi.c, line 1884]
nsAppStartup::Run  [mozilla/toolkit/components/startup/src/nsAppStartup.cpp, line 152]
main  [mozilla/browser/app/nsBrowserApp.cpp, line 61]
KERNEL32.dll + 0x289a5 (0x7c5989a5)



Incident ID: 31211987
Stack Signature	nsViewManager::HandleEvent 8d999c8d
Product ID	Firefox2
Build ID	2007030919
Trigger Time	2007-04-15 09:10:43.0
Platform	Win32
Operating System	Windows NT 5.0 build 2195
Module	firefox.exe + (001eaa9f)
URL visited	mail.yahoo.com
User Comments	clicked a link on the Yahoo home-page.
Since Last Crash	363762 sec
Total Uptime	454503 sec
Trigger Reason	Access violation
Source File, Line No.	c:/builds/tinderbox/Fx-Mozilla1.8-release/WINNT_5.2_Depend/mozilla/view/src/nsViewManager.cpp, line 2578
Stack Trace 	
nsViewManager::HandleEvent  [mozilla/view/src/nsViewManager.cpp, line 2578]
0x80000001


Reporter, can you reproduce this crash with a new firefox profile?
- http://kb.mozillazine.org/Profile
(Don't delete your existing profile)

Comment 2

[Dan Soper]

This may be just coincidence, but both just now and on the occasion that prompted me to report this as a bug, I was scrolling through the page (using the mouse-wheel) before it had finished loading, when the crash occurred.

Today's crash: TB32539405M

Steve, this crash is so intermittent that I fear I'd be using the new profile for a very long time before it became possible to conclude it's a profile-related issue, if that's what it is. Also, a "new" profile would never be entirely new, since I'd have to import my bookmarks (as an absolute minimum), to make the browser useable.


How could a corrupt profile cause the browser to crash on *some* visits to a *single, specific* website?

Comment 3

[Steve England [:stevee]]

Hmm, the TB32539405M stack looks useless (not your fault). Bookmarks should never cause a crash such as your seeing; however, an extension could well do. But yes, if the problem is intermittent and not reproducible on demand then making a new profile is a hard way of testing it is related to an extension.

Since it's not reproducible on demand, then there's not a lot we can do to further this bug report, except hope that someone else files a more reproducible bug that, when fixed, also fixes this one.

Comment 4

[Dan Soper]

A couple more talkback IDs: TB32776789K and TB34092439Y (both look similar to the last one I posted, however).

These are about six weeks apart, and there have been no Yahoo-triggered crashes in the interim that failed to initiate Talkback. I was beginning to think that something in the Yahoo page had changed so as not to cause this crashing any more.

Comment 5

[Dan Soper]

Same again: TB34160183Z

Odd that this should disappear for 6 weeks then pop up twice in 2 days.

Comment 6

[Dan Soper]

For the last 11 months or so I've been sticking this bug's number into the Talkback dialogue box, rather than reporitng crashes here and annoying you guys with bug-spam.

Yesterday I upgraded to Firefox 3. Now I find that Yahoo's UK homepage causes Firefox to hang. No crash or Talkback or anything, just a failure to reposnd to anything but the Windows "Close" box in the top-right corner. Clicking that results in one of the "This program is not responding ..." messages with an attractive "End Now" button.

I'm not sure yet that it happens *every* time, but it does seem more frequent than the crashing under Firefox 2.

Comment 7

[timeless]

for hangs:
http://developer.mozilla.org/en/docs/How_to_get_a_stacktrace_with_WinDbg
!analyze -v -hang

Comment 8

[u88484]

This bug was reported using a version of Firefox that security and stability updates are no longer provided for.  All users are strongly encouraged to upgrade to Firefox 3 by selecting 'Check for Updates' in the Help menu or by going to http://www.mozilla.com/en-US/firefox/firefox.html

If you can no longer reproduce this bug using the latest Firefox 3.0.x version, please change the status of this bug to 'RESOLVED' 'WORKSFORME'.

If you can still reproduce this bug, please provide additional details to help resolve this issue.

Comment 9

[Dan Soper]

After posting comment #6 (which pertains to Firefox 3.0.x) I have not observed Yahoo to cause a Firefox crash. Nor have I seen the behaviour described in that comment, despite sticking with Firefox 3.0.x and using the automatic updates.

I suspect the reason for this is a change to the Yahoo page (probably in the ads it contains) and not anything different in Firefox. It's the only reason I can think of why the bug should have been intermittent in the first place.



Setting status to "resolved worksforme" if bugzilla lets me....