1876882 - UI unresponsive and crashing during long filtering operation on wayland

Status: RESOLVED WORKSFORME

(Thunderbird :: Filters, defect)

Description

[andy]

Steps to reproduce:

For a gmail account, I created a new filter.

• Filter name: workspace
• Match any of the following:
• From is [e-mail]
• From is [e-mail]
• From ends with [e-mail]
• Perform these actions: Move Message to a folder called workspace

After creating the filter I selected Run now.

Actual results:

The UI got very unreponsive, but I saw the unread messages number go up on the folder called workspace. However the program crashed.

I was already running thunderbird from the cmdline and the last output line was: Gdk-Message: 16:48:05.163: Lost connection to Wayland compositor.

I tried re-opening thunderbird several times to see if it would complete the filtering and not crash.

The second time it also crashed eventually with "Gdk-Message: 16:48:36.234: Lost connection to Wayland compositor."

The third time it crashed with "Gdk-Message: 16:49:06.076: Error flushing display: Broken pipe"

The fourth time, it did not crash. And when I went to look at my filters the filter was gone. Did something roll back my config after three consecutive crashes? Yet I had edited some other filters before the first crash and those changes are still there.

Properties for the workspace folder show it containing 168 messages. It looks like it filtered everything. If I create a new filter again with "From ends with [e-mail]" no additional items are moved into the workspace folder.

Expected results:

Responsive UI during filtering.
No crashing.

Additional details:
OS: Arch Linux
Desktop environment: KDE Plasma v5.27.10 on Wayland
Thunderbird is running as a native wayland application
Thunderbird package version 115.6.1-1

Comment 1

[andy]

For the crashes after the first one, the application would open and look normal but be unresponsive, and the crash was after ~5-10 seconds.

Comment 2

[Wayne Mery (:wsmwk)]

yogesh, does this reproduce for you?

Comment 3

[Yogesh]

System: KDE Plasma 5.27.10 on Wayland
Thunderbird: 123.0b2 en-GB

I am unable to reproduce this issue. Possibly because (1) I don't have a large inbox or (2) my system resources can handle it.

I tried other emails that I could experiment with and none of the filters I tried caused the issue described by andy. I also have 32GB memory so that may have had something to do with it. That said, when I started Thunderbird first, it crashed (123.0b1 and 123.0b2) with the following error in the console :

Warning: ConnectToCompositor() try again : Connection refused

As I am running the application now, I see this in my console:

Error: ConnectToCompositor() connect() : No such file or directory

But the application seems to be working fine.

andy, there are a few things you can do to gather more information about the issue.

1. Try enabling logging for the Gecko engine. Might shed some light - https://wiki.mozilla.org/MailNews:Logging#Linux.2Funix
2. All crashes are logged under $HOME/.thunderbird/Crash Reports directory or `$HOME/.thunderbird/<profile_dir>/crashes/. You will find directories for pending and submitted crash logs.
3. You can also go to "Troubleshooting Information" section from the hamburger menu. If you scroll all the way down, you will see links to submitted crash reports which will open in the public crash log viewer.

Comment 4

[andy]

I am unable to reproduce this issue. Possibly because (1) I don't have a large inbox or (2) my system resources can handle it.

For (2), my system has an i9-9900k and 64GB of ram, so should be handling most things. Load is generally not maxed out, and generally have 20-30GB free.

For your suggestions 2 & 3, find ~/.thunderbird | grep -i crash has no results, and Ctrl+F on the troubleshooting information page I have no "crash" on the page.

Maybe related: I'm now getting similar firefox crashes with "Lost connection to Wayland compositor". Having not seen these crashes before, the difference today is I have a ton of tabs open (window 1: 43 tabs, window 2: 32 tabs, window 3: 15 tabs). Maybe it's an underlying GDK issue? Maybe related to this being a multi-gpu system, and/or when there is high cpu/resource use by firefox/thunderbird.

In firefox I'm finding simply opening a new tab or opening a new window freezes the UI and I get a crash after 10-60 seconds. The crash reports include e.g.

https://crash-stats.mozilla.org/report/index/bp-eaf60d74-c40f-46e7-88c2-aeedd0240214

• GraphicsCriticalError: |[0][GFX1-]: More than 2 GPUs detected via PCI, secondary GPU is arbitrary
  (t=0.315819) |[1][GFX1-]: Failed to create EGLSurface!: 0x3000 (t=6273) |[2][GFX1-]: Failed to create EGLSurface. 10 renderers, 8 active. (t=6273)
• MozCrashReason: Error 104 (Connection reset by peer) dispatching to Wayland display.

https://crash-stats.mozilla.org/report/index/bp-bdedcde6-1415-4a8d-979f-5e7130240214

• GraphicsCriticalError: |[0][GFX1-]: More than 2 GPUs detected via PCI, secondary GPU is arbitrary
• MozCrashReason: Lost connection to Wayland compositor.

https://crash-stats.mozilla.org/report/index/bp-17dc50ca-9558-484f-8bb3-d6dd80240215

• GraphicsCriticalError: |[0][GFX1-]: More than 2 GPUs detected via PCI, secondary GPU is arbitrary
• MozCrashReason: Lost connection to Wayland compositor.

When I start thunderbird I get that same "More than 2 GPUs detected" message in the console (normal startup without any crashes).

[ImapModuleLoader] Using nsImapService.cpp
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: More than 2 GPUs detected via PCI, secondary GPU is arbitrary
 (t=0.236737) [GFX1-]: More than 2 GPUs detected via PCI, secondary GPU is arbitrary

JavaScript error: chrome://messenger/content/aboutMessage.js, line 119: NS_ERROR_ILLEGAL_VALUE: Component returned failure code: 0x80070057 (NS_ERROR_ILLEGAL_VALUE) [nsIWebProgress.addProgressListener]
console.debug: "Found 0 public keys and 0 secret keys (0 protected, 0 unprotected)"
JavaScript error: chrome://messenger/content/mailWindow.js, line 570: NS_ERROR_NOT_INITIALIZED: 
console.error: (new TypeError("NetworkError: Network request failed", "resource://services-settings/Utils.sys.mjs", 229))

Comment 5

[Wayne Mery (:wsmwk)]

Andy, how many messages in these folders, both the source and the target?

Also, please check version 128 late(r) this week and report results. Thanks.

Comment 6

[Martin Stránský [:stransky] (ni? me)]

This should be fixed by 128 version and wayland-proxy.