Closed Bug 567106 Opened 14 years ago Closed 14 years ago

crash during initial fetch from imap account [@ msg_parse_Header_addresses]

Categories

(Thunderbird :: General, defect)

defect
Not set
critical

Tracking

(blocking-thunderbird3.1 rc1+, thunderbird3.1 rc1-fixed)

RESOLVED FIXED
Thunderbird 3.3a1
Tracking Status
blocking-thunderbird3.1 --- rc1+
thunderbird3.1 --- rc1-fixed

People

(Reporter: edoardo, Assigned: standard8)

References

Details

(Keywords: crash, Whiteboard: [fixed 3.1 RC 1 build 2])

Crash Data

Attachments

(1 file)

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; it; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3
Build Identifier: Gecko/20100519 Thunderbird/3.1

thunderbird crash during email fetch (some thousand)

after a restart it chashes again than starts work the next time.


Reproducible: Sometimes

Steps to Reproduce:
1.download Gecko/20100519 Thunderbird/3.1
2.rm rm -r ~/Library/Thunderbird 
3.start thunderbird
4.create new imap account (no password)
5.accept security exception (for smtp server)
6.click on "download mail" put password, don't check "use password manager"
7.click on a imap subfolder

I did many try but about 5/7 fails.

Actual Results:  
thunderbird crash 4/7 and 1/7hangs
Blocks: TB3.1meta
I had hoped that the fix for bug 564698 might have fixed this as well, but it looks like you're running a build with that fix.
the last crash report is: bp-bc5e4070-ee17-4550-9367-091112100520

(i am sorry but during test I removed the thunderbird setting folder)
Edoardo, is this just one message you are getting the issue on?

Is there a way you could try and view that, either on disk or webmail and find out what the to: and from: headers consist of?
blocking-thunderbird3.1: --- → ?
(In reply to comment #3)
> I had hoped that the fix for bug 564698 might have fixed this as well, but it
> looks like you're running a build with that fix.

We did do a subsequent change in that code in bug 549931, but I'm not yet sure what is going on here to cause that, unless we're going too far.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: crash during initial fetch from imap account → crash during initial fetch from imap account [@ msg_parse_Header_addresses]
I am sorry for my english... i think that i didn't understand....

(In reply to comment #5)
> Edoardo, is this just one message you are getting the issue on?
the issue is not regarding a particolar message as far as can I see: can I make
specific test (the inbox uses about 10 folders and thousand of messages)


> Is there a way you could try and view that, either on disk or webmail and find
> out what the to: and from: headers consist of?
I can't confirm that the problem regards a particular message. I use lanikai in
my work account and this isssue in not present. (it never hangs)


can I do some particular tests?
did other tests:

launch fresh instalation and fill all the informations: 2 tests OK

launch fresh instalation and fill all but password, then ask to download mail (don't remember password): 2 test fails
bp-a9e6f30d-e895-485c-8594-ae8332100520
bp-0beb878f-ac25-49d3-aab3-e70352100520

launch fresh instalation and fill all but password, then ask to download mail (remember password): 2 test fails
bp-0a9f532d-09f0-4941-ad30-2b3cf2100520 
no report for second crash (is it usefull to send all the reports?)

launch fresh instalation and fill password(don't remember password): 2 test OK

I compare two successive crashes, it does not occurs on the same message.
(In reply to comment #8)
> did other tests:
> 
> launch fresh instalation and fill all the informations: 2 tests OK
> 
> launch fresh instalation and fill all but password, then ask to download mail
> (don't remember password): 2 test fails
> bp-a9e6f30d-e895-485c-8594-ae8332100520 msg_parse_Header_addresses
> bp-0beb878f-ac25-49d3-aab3-e70352100520  ""
> 
> launch fresh instalation and fill all but password, then ask to download mail
> (remember password): 2 test fails
> bp-0a9f532d-09f0-4941-ad30-2b3cf2100520  nsSSLThread::requestRead(nsNSSSocketInfo*, void*, int, unsigned int) - no bug report
Attached patch Proposed fixSplinter Review
Tidy up our handling of group separators.
Assignee: nobody → bugzilla
Status: NEW → ASSIGNED
Attachment #446707 - Flags: superreview?(bienvenu)
Attachment #446707 - Flags: review?(bienvenu)
Comment on attachment 446707 [details] [diff] [review]
Proposed fix

probably should add a test for the ':' handling in a mailbox as well.
Attachment #446707 - Flags: superreview?(bienvenu)
Attachment #446707 - Flags: superreview+
Attachment #446707 - Flags: review?(bienvenu)
Attachment #446707 - Flags: review+
Checked into trunk: http://hg.mozilla.org/comm-central/rev/d6a6df09a1b3
Status: ASSIGNED → RESOLVED
blocking-thunderbird3.1: ? → rc1+
Closed: 14 years ago
OS: Mac OS X → All
Hardware: x86_64 → All
Resolution: --- → FIXED
Target Milestone: --- → Thunderbird 3.2a1
Edoardo: I've done a test build here that includes the patch:

http://s3.mozillamessaging.com/build/try-server/2010-05-21_08:10-bugzilla@standard8.plus.com-st8-567106-parse/bugzilla@standard8.plus.com-st8-567106-parse-mail-try-mac.dmg

If you're able to test it and confirm it fixes the crash, that would be useful.
2 tests, all OK. 

thank you.
(In reply to comment #14)
> 2 tests, all OK. 
> 
> thank you.

Thanks for the confirmation.
My mistake - that was 3.1 rc1 build 1, and this was fixed in a later build
Crash Signature: [@ msg_parse_Header_addresses]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: