Closed Bug 313311 Opened 19 years ago Closed 17 years ago

Frequently crashes when sending e-mail

Categories

(Thunderbird :: General, defect)

x86
Windows XP
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: braden, Assigned: mscott)

Details

(Keywords: crash)

Thunderbird frequently crashes when sending e-mail.
Do you have the talkback ids?
Have you tried hunderbird 1.5b2? 
I have sent talkback reports; how would I go about finding the ids?

No, I have not tried 1.5b2.
braden, all three reports are like this:

Incident ID: 11295628
Stack Signature	FULLSOFT.DLL + 0x111a (0x0171111a) 7cf10450
Product ID	Thunderbird10
Build ID	2005092314
Trigger Time	2005-10-31 11:53:10.0
Platform	Win32
Operating System	Windows NT 5.1 build 2600
Module	FULLSOFT.DLL + (0000111a)
URL visited	
User Comments	
Since Last Crash	863308 sec
Total Uptime	1984433 sec
Trigger Reason	Access violation
Source File, Line No.	N/A
Stack Trace 	
FULLSOFT.DLL + 0x111a (0x0171111a)
FULLSOFT.DLL + 0x1285 (0x01711285)
FULLSOFT.DLL + 0x73af (0x017173af)
mswsock.dll + 0xdb32 (0x71a5db32)
mswsock.dll + 0xd9bf (0x71a5d9bf)
mswsock.dll + 0x55af (0x71a555af)
mswsock.dll + 0x542c (0x71a5542c)
WS2_32.dll + 0x40bd (0x71ab40bd)
_PR_MD_CONNECT  [e:/builds/tinderbox/Tb-Aviary1.0.1/WINNT_5.0_Depend/mozilla/nsprpub/pr/src/md/windows/w95sock.c, line 145]
nsSocketTransport::OnSocketEvent  [e:/builds/tinderbox/Tb-Aviary1.0.1/WINNT_5.0_Depend/mozilla/netwerk/base/src/nsSocketTransport2.cpp, line 1321]
0xf18b0c24
nsWebBrowserPersist::StoreURIAttribute  [e:/builds/tinderbox/Tb-Aviary1.0.1/WINNT_5.0_Depend/mozilla/embedding/components/webbrowserpersist/src/nsWebBrowserPersist.cpp, line 3048]
0xa5a5a5a5
Keywords: crash
Braden, do you still get this with a trunk build?  my Bug 322598 is similar in some ways, but the stack is different.
what does the stack mean?  is 2005092314 was just a bad build?


Version: 1.0 → 1.5
Braden, you changed the version to 1.5. Please supply the talkbackid or copy the contents to the bug.

Does bug 316176 match your symptoms?
Incident id TB14080133K

Hard to say if this is the same as bug 316176. The symptoms are similar; but some of the comments in that bug suggests it's something that only started occurring recently. The bug I'm observing here has been around a while.
bug 316176 is now fixed. Does a newest trunk build fix your problem?
It does not. See TB17811102X.
that stack is very weird - it looks like talkback itself is crashing, and that's the crash report we're seeing. I wonder if the symbol info is correct.
Thunderbird crashes every time I send an email. It may take seconds or minutes, but TB always crashes.

I have sent many talkback reports (they're on auto-send now).

I have tried the following:
- re-install latest stable version in empty folder, test on new profile
- idem for latest nightly build (version 3 alpha 1 20070102)
- installed Seamonkey, copied mail folders from TB, Seamonkey crashes after sending

Any help would be appreciated.
could you paste some talkback incident id's in here?
(In reply to comment #12)
> could you paste some talkback incident id's in here?
> 

(In reply to comment #12)
> could you paste some talkback incident id's in here?
> 

I could if I knew where to find them ;-)

I can't find a number in the talkback agent.

I saved the details on one occasion, but I can't find an incident id in that file.

Please let me know where to find the id.
(In reply to comment #13)

> I could if I knew where to find them ;-)
> 
> I can't find a number in the talkback agent.

instructions at
http://kb.mozillazine.org/Quality_Feedback_Agent#Getting_an_incident_ID

Thanks for the pointer.

I have two incident of today: TB28083386M, TB28082934H.

TFD: your crashes are not the same crash. follow the links from your comment on this bug and use that to search for other bugs. don't paste the stacks here as they do *not* relate to this bug.
I haven't seen this since upgrading to Thunderbird 2. WORKSFORME
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.