98875 - Stack Overflow in Mail

Status: VERIFIED WORKSFORME

(MailNews Core :: Backend, defect)

Description

[Peter Jones]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.3) Gecko/20010801
BuildID:    2001080110

On a Laptop, memory was autosaved to disk due to low battery. When I connected
power, and restarted, Mozilla crashed. I have DrWatson dump.

Reproducible: Didn't try
Steps to Reproduce:
1. Start reading received mail.
2. Have batter power fail, causing machine to checkpoint memory on disk and
power down.
3. Plug in main power, restart machine.

Step 2 would be difficult to reproduce, unless a variable power test jig setup
is used to simulate a battery near end of a discharge.

Actual Results:  Crashed, taking DrWatson dump. Then, when I tried to submit the
dump, Windows began to get frequent blue-screen crashes (space to resume,
CTRL-ALT-DEL to restart). I used the space bar, then Windows froze. Had to
restart Windows, going through Scandisk sequence.

Expected Results:  Should resume execution.

Comment 1

[Peter Jones]

Attachment: DrWatson stack overflow dump after restoring power after battery low while reading mail

Comment 2

[Asa Dotzler [:asa]]

If you are crashing in Mozilla the best thing you can do to help the developers
fix your bug is to attach a stacktrace. If you're not building yourself you are
not out of luck.  Mozilla (thanks to a very cool donation from Netscape)
releases nightly and milestone builds with Full Circle's Talkback. Talkback
should catch most crashes and offer to send in a crash report. I can retrieve
that crash report and attach it to your bug report if you provide either the
Incident ID (you can get it by running the talkback program from
/components/talkback/) or you can let me know the email address you used to
submit the report and the time of sending. Thanks for your help in testing
Mozilla and reporting bugs.

Comment 3

[Peter Jones]

Sorry, I don't have a Talkback. Checking dates, I have:
TB34939224G, dated Sept 4, and TB35317784K, dated Sept 13; nothing in between.

This bug occurred under rather esoteric conditions (low battery interrupt), so I
don't personally mind if it ends up WONTFIX. Maybe someone would like to tackle
the DrWatson.

Comment 4

[Matthias Versen [:Matti]]

Reporter: 
Sorry that no one extracted the talkback data. Can you give us a new TB ID ?
Other Application are working fine after autosave ?
Can you reproduce this with 0.9.4 or later ?

Comment 5

[Peter Jones]

Other applications worked fine (resumed) after the autosave.

It would be very difficult to reproduce this bug, for it is difficult to know
exactly when a low-battery shutdown will occur. The low power interrupt would
have to occur while reading mail (just a few seconds). I'd need an electronic
testbench
to try to reproduce this, and there's no guarantee I'd get a Talkback.

So unless someone can use the DrWatson dump, I'be happy with the idea of closing
this for now, and reopening if it occurs again.

Comment 6

[Matthias Versen [:Matti]]

ok thanks.
We need a Stack with symbols to find the place where we are crashing.
We can get a stack with symbols if you use a debug build (and generate the 
stack) or if you give us a TB ID or clear steps to reproduce. 
(this one isn't easy to reproduce....)
But the TB server stores the stack only 2-4 weeks (AFAIK) and now your Talkback 
is lost.

You can reopen this bug and I will see it (I'm CCed) or file a new bug (and you 
can CC me there).

Thanks !
  Matthias

marking worksforme

Comment 7

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

verified per reporter's comments.  will re-file if he sees again.