Closed Bug 1611259 Opened 5 years ago Closed 4 years ago

becomes unresponsive, displays menus and window improperly, and/or OOM crashes after updating to 68.4.1

Categories

(Thunderbird :: General, defect)

Product:
Thunderbird
Component:
General
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

(thunderbird_esr68 affected)

Status:
RESOLVED INCOMPLETE
Tracking Flags:
Tracking Status
thunderbird_esr68 --- affected

People

(Reporter: max, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: crash, Whiteboard: [regression:tb6?])

User Story

fails Windows and Thunderbird safe mode
fails 73 beta
64 beta - fails?

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.117 Safari/537.36

Steps to reproduce:

Basic tasks such as hitting REPLY, attempting to attach a file, typing a medium length email

Actual results:

Program becomes unresponsive, displays menus and window improperly, and/or crashes completely.

Accessibility: Active
AccessibilityInProcClient: 0x400
AdapterDeviceID: 0x1616
AdapterDriverVersion: 20.19.15.4642
AdapterSubsysID: 381c17aa
AdapterVendorID: 0x8086
Add-ons: %7B58D4392A-842E-11DE-B51A-C7B855D89593%7D:3.0.0beta5,wetransfer%40extensions.thunderbird.net:2.0.0,default-theme%40mozilla.org:1.0,google%40search.mozilla.org:1.0,amazondotcom%40search.mozilla.org:1.1,bing%40search.mozilla.org:1.0,ddg%40search.mozilla.org:1.0,twitter%40search.mozilla.org:1.0,wikipedia%40search.mozilla.org:1.0
AvailablePageFile: 10047356928
AvailablePhysicalMemory: 9074921472
AvailableVirtualMemory: 557772800
BIOS_Manufacturer: LENOVO
BlockedDllList:
BreakpadReserveAddress: 115998720
BreakpadReserveSize: 83886080
BuildID: 20200108224327
CPUMicrocodeVersion: 0x2b
ContentSandboxCapable: 1
ContentSandboxLevel: 1
CrashTime: 1579810694
Email: max@anasuya.com
EventLoopNestingLevel: 1
FramePoisonBase: 0000004041080832
FramePoisonSize: 65536
GraphicsCriticalError: |[0][GFX1-]: Failed buffer for 0, 0, 1372, 453 (t=2690.59)
InstallTime: 1579147021
LauncherProcessState: 0
MemoryErrorCorrection: None
ModuleSignatureInfo: {"Microsoft Corporation":["msvcp140.dll","VCRUNTIME140.dll"],"Microsoft Windows":["sxs.dll","wininet.dll","oleacc.dll","uxtheme.dll","FWPUCLNT.DLL","rasadhlp.dll","midimap.dll","msacm32.dll","msacm32.drv","ksuser.dll","wdmaud.drv","sppc.dll","Bcp47Langs.dll","slc.dll","appresolver.dll","msvcp110_win.dll","OneCoreCommonProxyStub.dll","OneCoreUAPCommonProxyStub.dll","winnsi.dll","dhcpcsvc.dll","winsta.dll","mswsock.dll","twinapi.appcore.dll","dataexchange.dll","policymanager.dll","CoreMessaging.dll","CoreUIComponents.dll","TextInputFramework.dll","InputHost.dll","Windows.UI.dll","WinTypes.dll","AudioSes.dll","mscms.dll","DWrite.dll","ntshrui.dll","icm32.dll","dcomp.dll","wscapi.dll","explorerframe.dll","rmclient.dll","wshbth.dll","ColorAdapterClient.dll","nlaapi.dll","winrnr.dll","cscapi.dll","pnrpnsp.dll","NapiNSP.dll","DXCore.dll","dwmapi.dll","dxgi.dll","d3d11.dll","usp10.dll","avrt.dll","wsock32.dll","srvcli.dll","webauthn.dll","linkinfo.dll","credui.dll","fastprox.dll","wbemcomn.dll","dnsapi.dll","gpapi.dll","rsaenh.dll","amsi.dll","ondemandconnroutehelper.dll","devobj.dll","MMDevAPI.dll","propsys.dll","wbemsvc.dll","wbemprox.dll","iertutil.dll","urlmon.dll","WINMMBASE.dll","winmm.dll","ntmarta.dll","IPHLPAPI.DLL","userenv.dll","wtsapi32.dll","version.dll","winhttp.dll","dbgcore.dll","dbghelp.dll","CRYPTBASE.dll","sspicli.dll","sechost.dll","KERNELBASE.dll","msvcrt.dll","windows.storage.dll","shlwapi.dll","rpcrt4.dll","gdi32full.dll","ole32.dll","msasn1.dll","advapi32.dll","oleaut32.dll","ws2_32.dll","cfgmgr32.dll","crypt32.dll","setupapi.dll","bcrypt.dll","nsi.dll","user32.dll","profapi.dll","psapi.dll","win32u.dll","cryptsp.dll","SHCore.dll","umpdc.dll","kernel.appcore.dll","wintrust.dll","imm32.dll","shell32.dll","bcryptPrimitives.dll","msctf.dll","ucrtbase.dll","gdi32.dll","clbcatq.dll","kernel32.dll","msvcp_win.dll","combase.dll","powrprof.dll","ntdll.dll"],"Mozilla Corporation":["thunderbird.exe","xul.dll","nss3.dll","nssckbi.dll","freebl3.dll","ia2marshal.dll","softokn3.dll","mozglue.dll","lgpllibs.dll","prldap60.dll","ldap60.dll"]}
MozCrashReason: MOZ_CRASH(OOM)
Notes:
Has dual GPUs. GPU #2: AdapterVendorID2: 0x10de, AdapterDeviceID2: 0x1341, AdapterSubsysID2: 381c17aa, AdapterDriverVersion2: 21.21.13.7667FP(D10-L1100-W00001000-T000) DWrite? DWrite+ WR? WR- OMTP? OMTP+3
OOMAllocationSize: 32768
ProductID: {3550f703-e582-4d05-9a08-453d09bdfdc6}
ProductName: Thunderbird
ReleaseChannel: release
SafeMode: 0
SecondsSinceLastCrash: 3431
StartupCrash: 0
StartupTime: 1579810424
SystemMemoryUsePercentage: 46
ThreadIdNameMapping: 19180:"Gecko_IOThread",14444:"JS Watchdog",1548:"JS Helper",104:"JS Helper",9904:"JS Helper",8616:"JS Helper",11900:"Link Monitor",9256:"Socket Thread",16500:"Timer",18068:"Cache2 I/O",13364:"Cookie",1000:"GMPThread",17120:"Worker Launcher",9876:"IPDL Background",8208:"WindowsVsyncThread",13940:"Compositor",12712:"ImgDecoder #1",15400:"ImageIO",18220:"DOM Worker",8500:"HTML5 Parser",18476:"DataStorage",13556:"mozStorage #1",16888:"StyleThread#0",17988:"StyleThread#2",5636:"StyleThread#1",4896:"PlayEventSound",7544:"ImageBridgeChild",19208:"ImgDecoder #2",16776:"ImgDecoder #3",4716:"COM MTA",16508:"QuotaManager IO",9616:"ProxyResolution",1220:"localStorage DB",15800:"DNS Resolver #1",17956:"DNS Resolver #2",19412:"DNS Resolver #3",18852:"mozStorage #2",18884:"mozStorage #3",12348:"mozStorage #4",5920:"mozStorage #5",18840:"mozStorage #6",2776:"Font Loader",2032:"StreamTrans #8",16160:"URL Classifier",4604:"Classifier Update",10464:"DNS Resolver #4",12840:"IndexedDB #2",7448:"SSL Cert #2",13516:"SSL Cert #3",19304:"SSL Cert #4",
Throttleable: 1
TotalPageFile: 19640303616
TotalPhysicalMemory: 17090166784
TotalVirtualMemory: 4294836224
URL:
UptimeTS: 2696.22013
Vendor:
Version: 68.4.1
Winsock_LSP: Hyper-V RAW : 2 : 34 : 1 : 1 : 0x20026 : 0x8 : %SystemRoot%\system32\mswsock.dll : : 1234191b-4bf7-4ca7-86e0-dfd7c32b5445
AF_UNIX : 2 : 1 : 1 : 0 : 0x20026 : 0x8 : %SystemRoot%\system32\mswsock.dll : : a00943d9-9c2e-4633-9b59-0057a3160994
MSAFD Tcpip [TCP/IP] : 2 : 2 : 1 : 6 : 0x20066 : 0x8 : %SystemRoot%\system32\mswsock.dll : : e70f1aa0-ab8b-11cf-8ca3-00805f48a192
MSAFD Tcpip [UDP/IP] : 2 : 2 : 2 : 17 : 0x20609 : 0x8 : %SystemRoot%\system32\mswsock.dll : : e70f1aa0-ab8b-11cf-8ca3-00805f48a192
MSAFD Tcpip [RAW/IP] : 2 : 2 : 3 : 0 : 0x20609 : 0xc : %SystemRoot%\system32\mswsock.dll : : e70f1aa0-ab8b-11cf-8ca3-00805f48a192
MSAFD Tcpip [TCP/IPv6] : 2 : 23 : 1 : 6 : 0x20066 : 0x8 : %SystemRoot%\system32\mswsock.dll : : f9eab0c0-26d4-11d0-bbbf-00aa006c34e4
MSAFD Tcpip [UDP/IPv6] : 2 : 23 : 2 : 17 : 0x20609 : 0x8 : %SystemRoot%\system32\mswsock.dll : : f9eab0c0-26d4-11d0-bbbf-00aa006c34e4
MSAFD Tcpip [RAW/IPv6] : 2 : 23 : 3 : 0 : 0x20609 : 0xc : %SystemRoot%\system32\mswsock.dll : : f9eab0c0-26d4-11d0-bbbf-00aa006c34e4
RSVP TCPv6 Service Provider : 2 : 23 : 1 : 6 : 0x22066 : 0x8 : %SystemRoot%\system32\mswsock.dll : : 9d60a9e0-337a-11d0-bd88-0000c082e69a
RSVP TCP Service Provider : 2 : 2 : 1 : 6 : 0x22066 : 0x8 : %SystemRoot%\system32\mswsock.dll : : 9d60a9e0-337a-11d0-bd88-0000c082e69a
RSVP UDPv6 Service Provider : 2 : 23 : 2 : 17 : 0x22609 : 0x8 : %SystemRoot%\system32\mswsock.dll : : 9d60a9e0-337a-11d0-bd88-0000c082e69a
RSVP UDP Service Provider : 2 : 2 : 2 : 17 : 0x22609 : 0x8 : %SystemRoot%\system32\mswsock.dll : : 9d60a9e0-337a-11d0-bd88-0000c082e69a
MSAFD L2CAP [Bluetooth] : 2 : 32 : 1 : 256 : 0x20006 : 0x8 : %SystemRoot%\system32\mswsock.dll : : 9fc48064-7298-43e4-b7bd-181f2089792a
MSAFD RfComm [Bluetooth] : 2 : 32 : 1 : 3 : 0x20026 : 0x8 : %SystemRoot%\system32\mswsock.dll : : 9fc48064-7298-43e4-b7bd-181f2089792a
useragent_locale: en-US

This report also contains technical information about the state of the application when it crashed.

Expected results:

Nothing. It should have just remained working properly.

There are quite a few recent crash reports https://mzl.la/30P16nb
We need your crash id. see https://support.mozilla.org/en-US/kb/mozilla-crash-reporter-tb#w_viewing-reports-outside-of-thunderbird on how to obtain the ID

Flags: needinfo?(max)
Keywords: crash
Summary: Ever since updating to 68.4.1, Thunderbird crashes after only 2-3 tasks → becomes unresponsive, displays menus and window improperly, and/or crashes after updating to 68.4.1

Here are some for starters... :)

bp-6c273d46-d4ad-4152-842c-162580200119
bp-7e654a39-6eaa-454d-8b3a-057d00200123
bp-8a46608d-731c-4b37-a07b-79b5d0200122
bp-8c67fe06-b6b0-4765-8ff2-694820200119
bp-8cc4fb74-5962-4497-af33-53c470200120
bp-8d54a83c-6314-4045-8909-d821a0200121
bp-9ddd9a9a-8c26-41aa-a7ae-74d3d0200121
bp-22bab21c-9412-4776-9c0c-29a9c0200122
bp-24b8cf77-9924-45dc-8562-13e610200118
bp-30fcc284-e349-4025-ad24-151bb0200122
bp-44ec9e23-3c33-4d0b-8190-97c470200116
bp-51e12711-0c52-4543-9874-c90ce0200117
bp-59bea3be-3723-431f-964f-2ee540200121
bp-60afa88b-f116-47f0-b3c3-a75e70200118
bp-70c9cdc7-4fcb-49ea-91e5-6e4860200120
bp-78ec94e1-48ad-4172-85cd-20ec00200122
bp-90de3eb9-0ec7-401d-bea3-2c28c0200118
bp-190a5327-51b6-4abc-b51b-faf1a0200116
bp-671e7b7f-7889-4143-83e2-49ebc0200121
bp-672fa223-6998-40c3-ac22-af5d60200121
bp-883c99be-84e7-4d67-930e-abe560200123
bp-4385cdfc-0c4d-4772-bbfc-22a9e0200122
bp-17629c0c-8e24-4682-8f1a-1bb950200119
bp-38230b05-4dad-4e73-8246-991550200121
bp-621981f3-f972-4658-9b58-5765a0200119
bp-4080187c-ddc9-464f-8958-4acf50200117
bp-a440e85a-37e4-4f41-a092-b627b0200117
bp-a294251a-2d35-4ccc-8ed4-94cf60180525
bp-ac67abd2-c5c0-4ac8-b82f-bee420200119
bp-b9e6aaa8-9fa4-42c5-a1a9-99c040200122
bp-b3181980-43bf-4ef4-8ea4-adfd60200121
bp-ba729de6-4081-40c1-a9c6-4acf50200121
bp-bb822dd9-e13a-4986-8f59-de6e70200119
bp-bfeafbb5-e86a-4f65-ad23-e01d00200122
bp-c22a1d4e-fe75-425e-a889-70ae80200122
bp-c715b0a2-ffc2-4877-a88b-b28040200121
bp-c7381d69-aff8-47a4-ae48-cacaa0200122
bp-cbb51dea-ed0f-45c8-a6a9-bf9eb0200116
bp-d01fec48-f4a1-41f0-9ff9-40a010200121
bp-d6f0d723-fd5f-4091-acb3-fd2310200122
bp-d7b81866-68fa-45d6-83c1-d14730200121
bp-d2939b0a-763d-44b5-a0af-677d10200121
bp-d4509e38-8a8d-47d1-a383-c84620200122
bp-e1c7a2c7-fca7-4fca-9b31-740bf0200121
bp-e96c6f13-6439-4a85-a814-ed9600200116
bp-e141a821-eee9-4081-91e9-7ee870200118
bp-e0291a28-198c-4f5c-ba5f-12a9b0200119
bp-ea529e82-b3fa-4d7d-8554-7b7d50200121
bp-ee749c98-f933-46fd-b542-b44db0200120
bp-f1f54b4b-3734-49a3-97a6-5abdf0200118
bp-f7f359e4-a697-4b30-a3d0-8d01c0200123
bp-f8cf2875-3042-4244-a106-634080200122
bp-f42f76b5-e629-482d-80ee-5c5d90200119
bp-fb83e6dc-5c38-46c4-a3ea-4f3c70200123
bp-fcace8b2-962f-4b4e-82f2-0a1610180527
bp-00fc31cd-102e-4570-b926-ce1ad0200120
bp-0ccd557f-3f2a-4ca0-be1c-ec6220200117
bp-0cce7e60-7595-4742-868f-734c50200123
bp-2e53f3aa-b1a8-4757-9955-bf58f0200120
bp-4a9eaf89-45e8-45c0-b695-eb62d0200121
bp-4ec15f5c-9d6f-4a1b-8d4a-c6df30200121
bp-05bbf3c0-fc8e-4765-9de9-b56b50200123
bp-5d4bfbcb-4a6a-4cb1-959c-0f8430200121
bp-5fa95e06-06d4-4a86-8521-422f60200117
bp-5faa6f70-9c8d-466b-bf3b-79cdf0200117
bp-6ab52a76-2ff8-4528-9140-cb7820200122

Flags: needinfo?(max)

After a while, drop down menus just turn to black rectangles and the message area mirrors the message LIST that's above it, instead of displaying the message itself (and that in a jumbled way). Incidentally, in my desperation I installed 73.0b1 meanwhile, but it does the same thing as 68.4.1

Crash signatures:

A huge range of crash signatures suggests memory corruption, perhaps from faulty memory or other hardware. Because you are crashing so frequently I would first try the following

  1. Start Windows' safe mode with networking enabled
  1. If problem did not go away in safe mode, then if you are able to access memory chips - if you have spare memory swap it with what's on the machine, or if the machine has multiple chips swap the two chips. If you cannot or the problem persists, then test memory https://www.thewindowsclub.com/windows-memory-diagnostics-tool-in-windows-7

Also, I see you are on a Lenovo Windows 10 with 8gb ram. How old is this hardware?

Flags: needinfo?(max)

Thank you. Let me ask you this, though:

  • the problem never occurred before until updating to 68.4.1
  • problem does not occur on any other software, which all continues to run perfectly

Would a memory problem specifically begin to affect Thunderbird at the exact moment it was updated? Seems unlikely?

Flags: needinfo?(max)

It seems to run fine in safe mode.

(In reply to max from comment #6)

It seems to run fine in safe mode.

which safe mode? (there are two)

Windows in regular mode, I simply started Thunderbird in safe mode, and it runs and runs... so far

It did finally crash out on me, but ran a LOT longer than in regular mode.

Ah crap, seems to be back to its old tricks again after all. Initially seemed promising.

OK, Windows SAFE mode and Thunderbird SAFE mode, it still crashes just the same.

Memory scan yielded NO anomalies, either.

The BIOS on this machine is dated 9/22/2015

What happens if you disable your GPU?

After disabling the NVIDIA GeForce 840M, the issue persists - no difference.

I have also swapped the two RAM chips, but the issue persists.

Any more ideas, sir? It's a real conundrum...

And you also ran Thunderbird in safe mode when Windows was in safe mode? This Windows 10 machine is running as 64bit? How old is the hardware?

If you are finding safe mode does not help, and you have imap accounts, I suggest creating a new profile and test a couple of your accounts in the new profile https://support.mozilla.org/en-US/kb/using-multiple-profiles

Flags: needinfo?(max)
Summary: becomes unresponsive, displays menus and window improperly, and/or crashes after updating to 68.4.1 → becomes unresponsive, displays menus and window improperly, and/or OOM crashes after updating to 68.4.1

Yessir. Windows 10 64bit and Thunderbird BOTH in safe mode still had the problem. Like stated above, the BIOS is dated 9/2015, I don't remember exactly when I got this laptop, but I believe that BIOS date would be the best indicator of the system's age.

Flags: needinfo?(max)

OK, I created a new profile for my Gmail IMAP account, and it displays the same characteristics - jumbled or blank windows, blackened pull-downs. I could not get it to crash, but that's probably because I couldn't really do anything much as far as actual functional steps, i.e. when I hit REPLY, the window that came up was blank, etc.

Same thing when I tried to start a new message, I never even got to a point where I could try and test adding an attachment, changing color or size of the font, etc. because the message window was corrupt and nut functional to begin with.

Please post all your new crash IDs when you go through a new iteration

OK, here are the more recent ones:

bp-f35205d1-d09e-4d1c-8086-9ae180200128
bp-1bf4a15a-7464-4259-93d3-658350200128
bp-a3b3d777-09d3-4f55-bc0e-8e8e60200128
bp-1e08a72e-e35a-430c-8fda-f47c10200128
bp-c71cab67-9248-4546-a69b-6689d0200128
bp-48f93c64-9445-472c-ad2f-bffcf0200128
bp-09346aaa-5fec-417e-afac-a98480200128
bp-4626bb41-b38d-413c-8510-c44900200128
bp-cdf1ec23-34de-4e9b-b621-2844e0200128
bp-8f0caf0d-4509-417e-88ce-d90880200127
bp-b43fe121-7cb1-4bf6-a6c9-6e1340200127
bp-5fe7903e-e960-4a52-9644-9355c0200127
bp-7a44faa2-4c48-4c41-b745-cfc030200127
bp-0babad46-602e-4c48-ad31-8a2ba0200126
bp-7ea38e89-babc-44d6-bc35-cdc930200126
bp-b0558b5e-78f7-4c8c-a205-19ae10200126
bp-1c8d09e8-7dda-4f22-9707-39ad20200126
bp-ccfa7b7e-a18a-4b20-9613-0438f0200126
bp-3f29b033-8782-4827-8bba-d8f4d0200126
bp-7ba980cc-12ea-4125-a5c7-b2ed50200126
bp-05e28a28-481e-40e8-b033-7947f0200126
bp-fe77db42-7de7-476f-81ac-c6d2f0200126
bp-02d74443-fc33-45e0-8fa1-44eb30200126
bp-ba2c7342-246d-4b60-9601-7b4140200126
bp-aa3547a0-ef04-40cf-8412-afd840200126
bp-53ad8233-bdb6-48d6-ae92-b55530200126
bp-c97a0b56-ba8f-48a0-b01d-2aad80200126
bp-ce42869a-c72e-46cf-9aea-d24ab0200125
bp-3f63f5c4-3ecc-487a-b936-d49770200125
bp-4a6259fb-1597-4ff5-91fb-7f7160200124
bp-df843bb0-7719-40d5-8ea4-809ce0200124
bp-2a27d75e-3e23-4be1-9df1-159710200124
bp-c908148b-c75a-4c8e-92c8-0cbb70200124
bp-b080fd30-93e3-4b9b-b2c1-07ce30200124
bp-b13a92a0-aafe-4436-a7d5-701b20200124
bp-98c20589-eb11-4bf4-ae7a-681150200124
bp-82ad5e8e-7831-4cfb-ac0e-b227e0200124
bp-00736a2f-86e8-4a2e-a019-0b83f0200124
bp-3ac52201-c935-4fb4-abe5-70a220200124
bp-be234123-158f-45d8-b539-bfa100200124
bp-77a6d29a-759d-44d7-a597-34dd90200124
bp-307d1e45-a6fa-4744-9382-e72580200124
bp-9bd0e49e-0572-4aec-a8a5-600d40200124
bp-2c51aae0-5ac8-4087-9474-fcc070200124
bp-4db21812-8c2a-4920-ab34-cda8d0200129
bp-3d61ec45-12a4-4b98-b04f-06f0c0200129
bp-e9adde8d-db18-411c-a38d-b2ff90200129
bp-3f39df61-1fc8-4342-9914-c959e0200129
bp-4c526421-76c3-4ff9-b324-775a90200129
bp-ee3ac06d-57a5-42ff-9420-0d4ea0200129

I sampled several and they are the same crash signatures.

I think your next step is to try beta https://www.thunderbird.net/en-US/#channel If you have Thunderbird extensions they likely won't work, except calendar, which I don't seen enabled in your crash reports.

But I still suspect a hardware issue.
FWIW, other OOM crashes of the past year https://mzl.la/2uMEiZh

I actually switched to Beta days ago in desperation, because I thought that might help the problem. I have been running 73.0b1 (32-bit) all this time.

I will download the official Beta you linked to now, though.

The latest phenomenon is that I sometimes get emails twice for no reason (such as all your latest notifications coming through Bugzilla)

Oh, OK... it turns out that suggested BETA version is the same one I have already been running.

By the way, instead of upgrading, I wanted to downgrade back to an earlier version (which was working perfectly), but was then told that I can't, because something had been changed in the profile structure with the new version, and the profiles are not retro-able.

Couple more notes: Thunderbird Portable seemed to work just fine (that release still 60.9.1 Portable). Finally uninstalled the new crap, moved my profile, and restored an old email profile from before the 68.4.1 update.

Now reinstalled 60.9.1 (not portable), and it went back to working like a charm. Yeah, I did lose a bunch of my email, but I can't keep wrestling with my email client like this every day, it's seriously impacting my productivity.

You've been very patient and sorry I've been distracted/not paying enough attention, including forgetting that version 60 was running fine for you. But you shouldn't have needed to restore an old profile to run version 60 - it should run OK using your latest profile unless you have reason to believe your data as been corrupted.

Also based on your testing a code regression between version 60 and 68 should be causing this. If you are willing it would be very helpful to determine where in time that regression occurs - with your record of crashing in 5 minutes to 20 hours (many less than 60 and 30 minutes) we can probably determine that in a few iterations of installs that won't affect you running version 60 - two version of thunderbird using two profiles can run side by side.

Severity: normal → critical
Status: UNCONFIRMED → NEW
status-thunderbird_esr68: --- → affected
User Story: (updated)
Component: Untriaged → General
Ever confirmed: true
Whiteboard: [regression:tb6?]

also, might be a bug in our graphics code. Do you run Firefox?

The first time I tried to regress just leaving my profile as was, I was literally told by a pop-up window that I can't do that, because something had changed in the way profiles were now organized (sorry, I don't remember the original wording). Since I already lost a bunch of email trying to migrate to another client, then uninstalling that client and subsequently seeing my Thunderbird (!) data folder deleted in the process, I didn't really have much to lose.

I do have Firefox of course, but don't often use it. 71.0 is my current install.

Would be glad to be of help with trying to get to the bottom of this (since it's PERSONAL now!!) as long as it doesn't mess with my regular email based productivity. Does this mean we would need to go through every in-between version to figure out when exactly the pattern occurs?

Blocks: 1330872

max do you still crash using a current beta version?

Flags: needinfo?(max)

Max seems to be gone

Status: NEW → RESOLVED
Closed: 4 years ago
Flags: needinfo?(max)
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.