User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.6) Gecko/20060804 Firefox/1.5.0.6 (mahowi) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.12pre) Gecko/20080115 Thunderbird/2.0.0.12pre ID:2008011503 VC runtime error on shutdown Reproducible: Always Steps to Reproduce: 1.Send a mail (pop3) 2.Close the app (By X or File>>exit) 3.VC Runtime error R6025 Actual Results: R6025 Expected Results: Normal Termination Problem started in the last few days. Problem seen also by testers here, with some variations http://forums.mozillazine.org/viewtopic.php?p=3220759#3220759 FWIW I updraded my MSN runtime to VC8 a while back so, symptoms may vary.

Regression range confirmation: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.12pre) Gecko/20080114 Thunderbird/2.0.0.12pre ID:2008011404 Does not show the Runtime error.

I don't know if it can be defined as a variation, or a different bug: As of this build: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.12pre) Gecko/20080114 Thunderbird/2.0.0.12pre Mnenhy/0.7.5.0 ID:2008011503 thunderbird crashes whenever a compose window is closed, i.e., either when "Send" is pressed, or the window is manually closed/canceled. At first, I thought it was related to sending, but I can confirm that both sending, and writing of the sent message in the Sent folder are successful in all pop, imap or news accounts. It's precisely when the compose window starts closing that Tb crashes. I tried safe mode; the problem is there as well. And it occurs in each of my three Windows machines.

http://bonsai.mozilla.org/cvsquery.cgi?branch=MOZILLA_1_8_BRANCH&date=explicit&mindate=2008-01-14+03:00&maxdate=2008-01-15+04:00 my crash on exit on linux branch after sending a message was TB40312024Z, nsCSSFrameConstructor::RestyleEvent::HandleEvent() dec5a01c (-> bug 412701 -> bug 279505), which sounds like something that could be triggered by 2008-01-14 19:56 bzbarsky%mit.edu mozilla/layout/base/nsIPresShell.h 3.158.4.9 MOZILLA_1_8_BRANCH 11/1 Make all stylesheet changes do an async style reresolve, not a sync one. Bug 396613, bug 394337, bug 314776.

The crash you're seeing is bug 279505. Is the crash the same as the VC runtime error reported in comment 0? (My guess is no.)

Sorry for the "double posting". (I've posted this on the forum, too) I've already done today's update: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.12pre) Gecko/20080117 Thunderbird/2.0.0.12pre ID:2008011703 It's very interesting - I'm no longer getting the runtime error, only "TBird has encountered an error". (I'm using XP Pro.) If anyone would like to see it happen, I've made a screen-capture movie. It's in .avi format (7.1mb) because I wanted you to be able to see the details. http://www2.tu-berlin.de/zems/greenman/tbird_problem.avi By the way, my wife's machine (XP home) has also already been updated today, and she's still getting the "report to M$" version. I was getting the runtime error with yesterday's build.

Thanks Joe. I'm almost 100% sure that you're all seeing the same bug as bug 279505, which became very visible on the branch recently. The difference is, I don't believe the people commenting in this bug have Talkback installed. That video you created would show Talkback (the Quality Feedback Agent) appearing after your crash, which then would have sent a report to our servers where we could determine if the crashes were the same. For now, I'll leave this bug open, but I'm pretty sure this is a duplicate.

You're welcome. I've looked at the discussion of bug 279505 and of Bug 412701. The latter sounds similar, but as a layman, I'm afraid I really can't see any relation to the former. I'm afraid I'm not sophisticated enough. Anyway (if this is the place to express it), I sincerely appreciate all the work all you guys contribute to make FF and TB the great programs they are.

Not due to bug 283493, looks like a dupe of bug 412701 but I'll hold off a bit on that.

Is this the same crash? Getting it at close also.

(In reply to comment #9) > Created an attachment (id=297851) [details] > screenshot > > Is this the same crash? Getting it at close also. > Yes, it's the same, but after further testing, I do get some crashes rather than the runtime error. TB40373506G for one. Marking as Dup

Clearing blocking request. Thanks for filing and testing guys!