189078 - trunk topcrash [@ nsARTDecoder2::EndART]

Status: VERIFIED INVALID

(Core :: Graphics: ImageLib, defect)

Description

[Jan Carpenter]

This stack signature is a topcrasher for trunk

Crash data range: 2003-01-07 to 2003-01-13
Build ID range: 2003010708 to 2003011308
	 Count 	 Platform 
	    3 Windows NT  5.1 build 2600
	    2 Windows NT  5.0 build 2195
(sorry, but guessing on the component, feel free to switch.)

Stack Trace: 

	 nsARTDecoder2::EndART
[c:/builds/seamonkey/ns/imaging/decoders/art/src/nsARTDecoder2.cpp  line 240]
	 art_write	[c:/builds/seamonkey/ns/imaging/decoders/art/src/art2.cpp  line 646]
	 imgContainerART::Notify
[c:/builds/seamonkey/ns/imaging/decoders/art/src/imgContainerART.cpp  line 120]
	 nsTimerImpl::Fire	[c:/builds/seamonkey/mozilla/xpcom/threads/nsTimerImpl.cpp 
line 395]
	 nsTimerManager::FireNextIdleTimer
[c:/builds/seamonkey/mozilla/xpcom/threads/nsTimerImpl.cpp  line 616]
	 nsAppShell::Run	[c:/builds/seamonkey/mozilla/widget/src/windows/nsAppShell.cpp
 line 176]
	 nsAppShellService::Run
[c:/builds/seamonkey/mozilla/xpfe/appshell/src/nsAppShellService.cpp  line 471]
	 main1	[c:/builds/seamonkey/mozilla/xpfe/bootstrap/nsAppRunner.cpp  line 1559]
	 main	[c:/builds/seamonkey/mozilla/xpfe/bootstrap/nsAppRunner.cpp  line 1907]
	 WinMain	[c:/builds/seamonkey/mozilla/xpfe/bootstrap/nsAppRunner.cpp  line 1927]
	 WinMainCRTStartup()
	 kernel32.dll + 0x214c7 (0x77e814c7)
 
 	Source File :
c:/builds/seamonkey/ns/imaging/decoders/art/src/nsARTDecoder2.cpp line : 240

COMMENTS/URLs:

     (16153480)	URL: http://media.aoltimewarner.com
     (16131330)	URL: http://www.angelfire.com
     (15941741)	URL: http://www.tnt.tv
     (15921014)	URL: www.angelfire.com/band/unofficialpillar

Comment 1

[Christian :Biesinger (don't email me, ping me on IRC)]

this is invalid, mozilla does not contain an art decoder. put it in bugscape.

Comment 2

[[e-mail] (gone - use [e-mail] instead)]

Jan, this lives in Bugscape as
http://bugscape.netscape.com/show_bug.cgi?id=19929... ;-)

FWIW, all of the crash incidents are mine, too, so it's not really a topcrasher.
 Though it's 100% reproducable and should be fixed for our next RTM.