Closed Bug 1515262 Opened 6 years ago Closed 6 years ago

Reindexing emails never stops and eats all CPU

Categories

(Thunderbird :: Untriaged, defect)

Product:
Thunderbird
Component:
Untriaged
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 1362483

People

(Reporter: ccomb, Unassigned)

References

Details

(Keywords: perf)

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:64.0) Gecko/20100101 Firefox/64.0 Actual results: Reindexing emails never stops (seems blocked at some point) and CPU is at 100% forever. I don't know how to find which content is blocking the reindexing
I found how to enable debug informations https://wiki.mozilla.org/Thunderbird:Debugging_Gloda Now waiting for the next indexing CPU dinner
Did this begin immediately after an update?
Flags: needinfo?(ccomb)
Keywords: perf
it began shortly after switching to the beta channel, a few months ago
Could not reproduce, I'm closing for now, and will reopen if it happens again
Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Flags: needinfo?(ccomb)
Resolution: --- → INVALID
I'm reopening because I woke up this morning with my disk full with more than 150G of logs generated by Thunderbird, as I forgot to remove the verbose settings. Thunderbird was blocked in an infinite loop, with the following message : Dec 28 07:11:06 ccomb Thunderbird.desktop[1483]: 2018-12-28 07:11:06#011gloda.index_msg#011WARN#011Observed header that claims to be gloda indexed but that gloda has never heard of during compaction. In folder: mailbox://****(mailhidden)****@mail.gandi.net/Inbox sketchy key: 19587 subject: Cloud Expo Europe / Data Centre World Paris 2018
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
Your issue is described in bug 1362483 and bug 1406653. The later reports the problem is gone in version 64.
See Also: → 1362483
The later speaks about 54.0a1. I'm on 64.0b3
Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago → 6 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.