298779 - visit a page with an image and 0-2 words below. right after clicking View Image with Images turned off. [@ nsCOMPtr_base::~nsCOMPtr_base]

Status: VERIFIED DUPLICATE of bug 246351

(Firefox :: General, defect)

Description

[Ivo Goncalves]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4

I have been noticing this I think since version 1.03, but I have noticed more of
this situation on 1.04. I have very slow connection, thus I browse without
images to speed browsing up. However, sometimes I want to see the images, on IE
that I used before Fx, I just selected Show Image, which would return the image
on the same page in the exact location it should be. Fx does not do this, it
loads the image alone leaving the page I was browsing behind. Ok, I can live
with this. The problem is that I noticed that some sites that were just a joke
or incredibly lame, as in they included only one large Image with one or two
words below or above it there was a problem. What happened is that when I try
see that image through View Image option (on right click), the browser
completely crashes. It does not matter if I was browsing with a tab, or with two
windows open separately, or even just a tabless one window--it all vanishes for
Firefox closes itself and leaves no shadow on the task and/or process list.
Since I came across one of such sites recently, I have been testing on it and it
always happens, so it's not occasional, but a constant problem. It can be
checked here: [ http://spikedies.com/ ] but remember to turn images off before
accessing the site. I have also checked the source code, but aside some
non-standard w3c html (HTML not in its best) there is nothing wrong. No Scripts,
either Javascript, ActiveX, VBScript or Flash or Java, nothing strange aside an
embed midi, but since I do not remember a midi in the other web sites that
crashed the same way, I don't believe this is the issue. I do think due to my
experience that the problem is either with the rendering of the JPEG format
(unlikely, but one never knows) or because the site did not load any page in the
address bar, just a domain (albeit it loaded the index.html, it does not show on
the address bar) and although this is of course normal behaviour for a browser,
maybe it's the reason of this issue. I do not really know, but I hope this
report will help you developers. Thank you for reading it.

P.S: I am not a natural english speaker, so I apologize for the weird way of
making sentences... I hope you can understand. I also want to point out that I
do not use any extension that deals with the right click menu or with image
rendering. I have the PURL Links, the Live HTTP headers, the MediaConnectivity
(for QuickTime movies) and the Disable Target for Downloads. Hmm, while writing
this Postscript, I realized that maybe I should have tested removing those
extensions before reporting so that I can be 100% sure it is a browser issue. I
am sorry, but even if it maybe is the extensions to be blamed I cannot
understand how they are affecting rendering images in a way to crash the browser.

Reproducible: Always

Steps to Reproduce:
1. Load http://spikedies.com/ with Images turned off
2. Click View Image
Actual Results:  
Browser Crashes in all circunstances tested by me.

Expected Results:  
Show the Image outside the HTML page.

No themes used, nor any other special software outside a few extensions. I do
not have any Error message, like Application Violation either...

Comment 1

[Ria Klaassen (not reading all bugmail)]

WFM both in 1.0.4 and in 1.0+ new profile.

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050625
Firefox/1.0+ ID:2005062511

Comment 2

[Maarten Aertsen]

WFM in Fx 1.0.4 on Windows XP SP 1

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511
Firefox/1.0.4

Comment 3

[Ivo Goncalves]

(In reply to comment #2)
> WFM in Fx 1.0.4 on Windows XP SP 1
> 
> Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511
> Firefox/1.0.4

I am sorry, but what does WFM stand for?

Comment 4

[Matthias Versen [:Matti]]

http://www.acronymfinder.com/af-query.asp?String=exact&Acronym=wfm&Find=Find
(Works for me)

Comment 5

[Peter van der Woude [:Peter6]]

Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b2) Gecko/20050625
Firefox/1.0+ ID:2005062508

WFM

reporter,
can you try in Firefox-safemode (windows start menu->Firefox->safemode).
Close all instances of Firefox before you do.

Maybe one of your extensions is acting up.

Comment 6

[Ivo Goncalves]

(In reply to comment #5)
> reporter,
> can you try in Firefox-safemode (windows start menu->Firefox->safemode).
> Close all instances of Firefox before you do.
> 
> Maybe one of your extensions is acting up.

Same result... Although after more testing (meaning actual browsing as I
normally would) I have noticed that Fx is now crashing also everytime I try to
see a QuickTime .mov, so maybe those two events are related. Who knows? All I
know is that apparently it's just me who is affected by this :(

Comment 7

[Steve England [:stevee]]

Ivo, when your firefox crashed did you submit any crash info to the Talkback
server? if you did, then please post the TalkBackIDs of the crashes you
reported. You can find the TBIDs by running ../firefox/components/talkback.exe

Comment 8

[Ivo Goncalves]

(In reply to comment #7)
I can see three reports there, all of them sent at same day (yesterday, 25
June). The IDs are as following (in the order they are displayed):
TB6977482W
TB6977433Z
TB6976349Y
All of them are type = program Crash, and status field states they were sent.
Does this information help or should I do something else?

Comment 9

[Peter van der Woude [:Peter6]]

I checked, this seems to be a branch only problem.

Comment 10

[timeless]

Product ID	Firefox10
Build ID	2005051112
Trigger Time	2005-06-25 12:45:32.0
Platform	Win32
Operating System	Windows NT 5.1 build 2600
Module	xpcom.dll + (0003d243)
URL visited	http://spikedies.com
User Comments	
Since Last Crash	384619 sec
Total Uptime	384619 sec
Trigger Reason	Access violation
Source File, Line No.
d:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.0_Depend/mozilla/xpcom/glue/nsCOMPtr.cpp,
line 81
Stack Trace 	
nsCOMPtr_base::~nsCOMPtr_base 
[d:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.0_Depend/mozilla/xpcom/glue/nsCOMPtr.cpp,
line 81]
XPCJSRuntime::GCCallback 
[d:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.0_Depend/mozilla/js/src/xpconnect/src/xpcjsruntime.cpp,
line 495]
js_GC 
[d:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.0_Depend/mozilla/js/src/jsgc.c, line
1387]
js_ForceGC 
[d:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.0_Depend/mozilla/js/src/jsgc.c, line
1000]
GlobalWindowImpl::RunTimeout 
[d:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.0_Depend/mozilla/dom/src/base/nsGlobalWindow.cpp,
line 5424]
GlobalWindowImpl::TimerCallback 
[d:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.0_Depend/mozilla/dom/src/base/nsGlobalWindow.cpp,
line 5786]
nsAppShellService::Run 
[d:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.0_Depend/mozilla/xpfe/appshell/src/nsAppShellService.cpp,
line 495]
main 
[d:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.0_Depend/mozilla/browser/app/nsBrowserApp.cpp,
line 58]
kernel32.dll + 0x2141a (0x77e7141a)

Comment 11

[Robin Monks]

Dupe of bug 246351, that bug may need to be reopened.

Reporter, if you feel this was done in error, please REOPEN.

Robin

*** This bug has been marked as a duplicate of 246351 ***

Comment 12

[Ivo Goncalves]

(In reply to comment #11)
That other bug report although the issue may be due to the same bug in Fx Win32,
is not exactly similar. The way of causing it and the circunstances behind it
are different. The other reporter is also using a laptop which may have some
kind effect on his/her own crash. I do not really know, but since there is much
more details here and the crash info sent to Talkback, I assume it will be
better to have this bug report open until the situation is figured out. I
however cannot seem to add any more information, but I am willing to help in
case there is something I can do. According to mr. Peter van der Woude this is a
branch only bug, as such I will mark it as VERIFIED.