Closed Bug 1581849 Opened 5 years ago Closed 4 years ago

Thunderbird Daemon lives after closing - Spawns many instances... causing very sluggish response (eats up memory eventually)

Categories

(Thunderbird :: OS Integration, defect)

x86_64
Linux
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: john, Unassigned)

References

Details

Attachments

(3 files)

User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/78.0.3895.5 Safari/537.36 OPR/65.0.3443.0 (Edition developer)

Steps to reproduce:

1.) Open Thunderbird
2.) Close It using the X SYMBOL (TOP RIGHT) - (Using File > Close terminates the Daemon Properly)
3.) Open Thunderbird Again
4.) Close Using X SYMBOL (TOP RIGHT)
Repeat as needed.

Actual results:

Application daemon remains live using the X symbol and after many days if not weeks it's very easy for this to bring a system to it's knees resource wise as the daemons continue spawning as new instances. If you select file close the daemon terminates properly - it's only when utilizing the graphical X. Once you kill the initial daemon you will get a series of graphic closing errors equal in the amount of instances open.

Expected results:

The program daemons should terminate? Unless this was by design to bg/fg but since this is a X11 based version - no real command line integration I'm guessing this a defect.

Attached image Close thunderbird

This Error Spawns AFTER CLOSING - unlike past errors I can open and close without issue... I can only generate this after running the kill command on the residual daemons that are backlogged... after killing one the entire que crashes and throws this error for each and every daemon in the background that was still in existence

Component: Untriaged → OS Integration
OS: Unspecified → Linux
Hardware: Unspecified → x86_64
Flags: needinfo?(vseerror)

We've seen other reports of this on linux - both on shutdown and startup - and none of them caused by Thunderbird iirc.

for some reason this query https://mzl.la/350xkxI is messed up, but looking at the "invalid" bugs in https://mzl.la/2NlHUK2yields
Bug 1559857 - Thunderbird 68b1 infinite loop (100% cpu usage) and hanging on startup
Bug 891314 - Thuderbird starts many processes under Linux

Severity: normal → critical
Flags: needinfo?(vseerror)
Flags: needinfo?(unicorn.consulting)
Flags: needinfo?(john)

See also Bug 1585695 which seems a similar issue on Windows.

John, which full version number did this start?

John ?

See Also: → 1559857, 891314
Whiteboard: [closeme 2019-11-15]
See Also: → 1585695

FYI as per Jork confirmation in 1585695 comment 3 it seems the issue is by design:

"...
File > Exit will close all windows. Clicking the [X] on the main window will not close the application and will leave non-modal windows open, most prominently the compose window.
..."

Personally, as I reported in Bug 1585695 and John here, I would expect inuitively that pressing [X] at the top right corner of main TB window would have the same effect than File > Exit... to close TB and all related processes/remaining windows at once.

Resolved per whiteboard

Status: UNCONFIRMED → RESOLVED
Closed: 4 years ago
Resolution: --- → INCOMPLETE
Whiteboard: [closeme 2019-11-15]
Flags: needinfo?(unicorn.consulting)
Flags: needinfo?(john)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: