User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C) Build Identifier: 3.1.4 My wife and i both previously used Outlook for email. Some time ago we changed to Thunderbird and successfully imported all of our Outlook folders and mail. Has worked fine ever since until we upgraded to 3.1.4 yesterday. Now clicking on the arrow to the left of the Outlook Mail folder to expand it causes Thunderbird to crash, hence can no longer see or read these imported items. Reproducible: Always Steps to Reproduce: 1.Open Thunderbird 2.Click to expand Outlook folder 3. Actual Results: Thnderbird crashes...actually get "not responding" message. Expected Results: Have to close and restart Thunderbird to continue....still cant access imported Outlook folders.
Could you follow the instructions at https://developer.mozilla.org/En/How_to_get_a_stacktrace_for_a_bug_report , make sure to replace firefox by thunderbird and get us a stack trace.
We'd need symbols to have a clue about what's happening on the stack. Ludo, can you help get symbols?
Keith can you try to disable BullGuard and restart the procedure ?
this isn't a problem with symbols. reporter please install and use the *32bit* version of windbg, not the *64bit* version.
ludovic: that's the 64bit windbg. it isn't helpful.
(In reply to comment #7) > ludovic: that's the 64bit windbg. it isn't helpful. Wep - saw it after the upload. Keith is working on getting us a proper 32 bit stack trace.
Created attachment 482042 [details] Latest (failed) attempt to run 32-bit Windbg Can anybody give me any pointers as to what I am doing wrong? Following the instructions exactly but Thunderbird fails to open when I press Go under the Debug menu.
(1640.1654): Access violation - code c0000005 (first chance) First chance exceptions are reported before any exception handling. This exception may be expected and handled. eax=00000001 ebx=00000000 ecx=66fa0000 edx=001fdde8 esi=fffffffe edi=777e3ade eip=00000023 esp=0112f87c ebp=0112f8a8 iopl=0 nv up ei pl nz na po nc cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010202 00000023 ?? ??? 0:000> g you shouldn't have used 'g' at this point, but it doesn't look like it mattered. 0x23 0x76992fda ntdll!LdrpInitializeProcess+0x133f ntdll!_LdrpInitialize+0x78 ntdll!LdrInitializeThunk+0x10 is a very strange crash :(
Created attachment 482139 [details] Another attempt...looks better to me...but what do I know. :) Hopefully one of you guys might be able to make something of this.
Created attachment 515215 [details] TB outlook import folder structure (you have all your folders backed up, right? :) ) If you click on the top level folder called Outlook Import there should be nothing to list except other folders. Attached is the folder structure of a simple import which shows this. So if you create a new top level fold XXX in local folders, and then with thunderbird shut down, in windows explorer copy the folders in Outlook Import to XXX, can you open folder XXX after starting thunderbird? (In reply to comment #11) > Created attachment 482139 [details] doesn't look substantially different to me (In reply to comment #0) >... > Has worked fine ever since until we upgraded to 3.1.4 yesterday. Now clicking > on the arrow to the left of the Outlook Mail folder to expand it causes > Thunderbird to crash, hence can no longer see or read these imported items. so, this folder worked in version 2, on this windows 7 machine?
Keith? (In reply to Wayne Mery (:wsmwk) from comment #12) > Created attachment 515215 [details] > > (In reply to comment #0) > >... > > Has worked fine ever since until we upgraded to 3.1.4 yesterday. Now clicking > > on the arrow to the left of the Outlook Mail folder to expand it causes > > Thunderbird to crash, hence can no longer see or read these imported items. > > so, this folder worked in version 2, on this windows 7 machine?
RESOLVED INCOMPLETE due to lack of response to last question. If you feel this change was made in error, please respond to this bug with your reasons why.