279302 - random crash when composer window open for "long" time (random) [@ FULLSOFT.DLL + 0x111a]

Status: RESOLVED EXPIRED

(Thunderbird :: Message Compose Window, defect)

Description

[michele.casalgrandi]

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)
Build Identifier: Firefox version 1.0 (20041206)

If I compose an email and take my time in composing it (> 5 min) the client 
crashes soon after the progress window for sending pops up.
I could not find any other recurring issue other than the time the window is up.
However, I cannot guarantee that is the trigger as it happens randomly (about 
20-30% of the times).

Reproducible: Sometimes

Steps to Reproduce:
1. Compose email over a long period of time (5-10 minutes).
2. Send to SMTP server
3. Crash (randomly)

Actual Results:  
Crash and Quality Feedback Agent comes up

Expected Results:  
First save the email to draft folder and remove once Send is successful - maybe 
as a selectable option.

Incidents: 
- TB3120649K
- TB2989098Q

Comment 1

[michele.casalgrandi]

You can add TB3328624W to the list. thanks.

Comment 2

[michele.casalgrandi]

and TB3206429X

Comment 3

[timeless]

Incident ID: 3206429
Stack Signature	FULLSOFT.DLL + 0x111a (0x0209111a) 99e5575b
Product ID	Thunderbird10
Build ID	2004120606
Trigger Time	2005-01-21 12:58:12.0
Platform	Win32
Operating System	Windows NT 5.0 build 2195
Module	FULLSOFT.DLL + (0000111a)
URL visited	
User Comments	
Since Last Crash	267857 sec
Total Uptime	1580950 sec
Trigger Reason	Access violation
Source File, Line No.	N/A
Stack Trace 	
FULLSOFT.DLL + 0x111a (0x0209111a)
FULLSOFT.DLL + 0x1285 (0x02091285)
FULLSOFT.DLL + 0x73af (0x020973af)
msafd.dll + 0x6273 (0x74fd6273)
msafd.dll + 0x8d4f (0x74fd8d4f)
msafd.dll + 0x4c6a (0x74fd4c6a)
WS2_32.DLL + 0xc21d (0x7503c21d)
_PR_MD_CONNECT 
[e:/builds/tinderbox/thunderbird-branch/WINNT_5.0_Clobber/mozilla/nsprpub/pr/src/md/windows/w95sock.c,
line 145]
nsSocketTransport::OnSocketEvent 
[e:/builds/tinderbox/thunderbird-branch/WINNT_5.0_Clobber/mozilla/netwerk/base/src/nsSocketTransport2.cpp,
line 1321]
0xf18b0c24

reporter: could you possibly give me some information about your 
msafd.dll and WS2_32.DLL files?
i need the information that would be gathered by following the steps listed at
http://www.utdallas.edu/~mkp021000/mssymbols.htm

Comment 4

[michele.casalgrandi]

Attachment: msafd.dbg

Comment 5

[michele.casalgrandi]

Attachment: msafd.pdb

Comment 6

[michele.casalgrandi]

Attachment: ws2_32.dbg

Comment 7

[michele.casalgrandi]

Attachment: ws2_32.pdb

Comment 8

[michele.casalgrandi]

It was a pain to get then info :) Let me know if you need more LOL - Thx, Michele.

Comment 9

[timeless]

addr: 0x000061F0     symbol: _WSPRecv@36 (PublicSymbol)
addr: 0x00006549     symbol: _WSPRecvFrom@44 (PublicSymbol)
addr: 0x00008CB7     symbol: _WSPCloseSocket@8 (PublicSymbol)
addr: 0x00009008     symbol: _WSPGetSockOpt@24 (PublicSymbol)
addr: 0x00004BDF     symbol: _WSPEventSelect@16 (PublicSymbol)
addr: 0x00004CC9     symbol: _SockEventSelectHelper@12 (PublicSymbol)
addr: 0x0000C218     symbol: _WPUCloseSocketHandle@8 (PublicSymbol)
addr: 0x0000C2E0     symbol: _WPUQuerySocketHandleContext@12 (PublicSymbol)

this is the first time i've tried to do something like this, i'm going to get
better *very* slowly. (symbol info from 
Microsoft Visual Studio .NET 2003\Visual Studio SDKs\DIA SDK\Sample
debug\dia2dump)

note that this doesn't seem to include privatesymbols :) [if such a thing exists]

Comment 10

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 11

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.