239297 - faulting module firefox.exe, version 0.8.0.0, fault address 0x00211d6a. After about 30 Hours open on page with refresh Mechanism.

Status: VERIFIED INCOMPLETE

(Firefox :: General, defect)

Description

[Reinder Kraaij]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.6) Gecko/20040206 Firefox/0.8
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.6) Gecko/20040206 Firefox/0.8

The Firefox Browser seems to have problems when the browser is open for a long
time, on a page, which is auto refreshing itself.

Window Crashes, and gives :
Faulting application firefox.exe, version 0.8.0.0, faulting module firefox.exe,
version 0.8.0.0, fault address 0x00211d6a.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Reproducible: Always
Steps to Reproduce:
1. Browse to DWaal.net
2. Login as Guest, Using something like "Dumm90"
3. Keep your browser open for about 1 and a half day.

Actual Results:  
FireFox Crashed.

Expected Results:  
Keep on Running.

The Browser is Talking to a Apache Module, Which keeps on the Request for a long
while, and releases it when there is a event. If no events are being send. The
Server  waits "X" Seconds, and answers the client -- which then sends out a
request again.

I don't think a exploit could be created from this (normal people don't have
their browser that long open on a site). But since it really crashed (i have now
seen this 3 times) I have marked the Security Flag

Comment 1

[Jesse Ruderman]

Browser crashes aren't considered security holes unless:

- the crash could be exploited in a way that it does more than just crash the
browser.  For example, buffer overflows often appear as crashes, but many buffer
overflows can also be exploited to compromise the program.

or

- the crash is in NSPR or NSS, because some server software uses those portions
of Mozilla code.  Crashes in servers *are* considered security holes.

Firefox for Windows will include Talkback soon (hopefully), which lets you send
stack traces to mozilla.org.   After Talkback sends the stack trace to
mozilla.org, you can give Asa Dotzler the talkback id and ask him to get the
stack trace from the Talkback server.  I suggest that you wait for Talkback to
be included, download a new build, and test again.

Comment 2

[Reinder Kraaij]

Ok. I will wait till the moment talk back is inclucded. Meanwhile, i have
started a Browser again, to the same url, to check the Error One more time again.

Comment 3

[Daniel Veditz [:dveditz]]

The chances are good that the crash is in the shared browser engine and not
anything Firefox specific. If you can reproduce this in a recent Mozilla nightly
we have talkback for that one again.

Comment 4

[Daniel Veditz [:dveditz]]

Clearing confidential flag.

Would love to get some talkback id's for this crash.

Comment 5

[Jesse Ruderman]

Clearing [sg:needinfo] because this isn't more likely to be a security hole than
any other crash we don't have a stack trace for.

Comment 6

[Samuel Sidler (old account; do not CC)]

Reinder, are you still seeing this crash using Firefox 2.0.0.3 or a recent nightly?

Comment 7

[Samuel Sidler (old account; do not CC)]

Without any word back, I'm closing this bug as INCOMPLETE. We need a talkback ID or stack to move further.