console.error: gloda.index_msg: "Exception while attempting to mark message with gloda state afterdb commit"
Categories
(Thunderbird :: General, defect)
Tracking
(Not tracked)
People
(Reporter: mkmelin, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(1 obsolete file)
console.error: gloda.index_msg: "Exception while attempting to mark message with gloda state afterdb commit" ({})
Happens e.g. during comm/mail/base/test/browser/browser_searchMessages.js
Comment 1•1 year ago
|
||
I think this is a dup of Bug 1635029 or the other way round.
I uploaded the names of all the tests where the error occurred in Bug 1635029.
The number of the errors during mochitest, 112, is a bit staggering. Something is definitely wrong.
| Reporter | ||
Updated•1 year ago
|
| Reporter | ||
Comment 3•1 year ago
|
||
I kind of found the problem and a fix. But not yet the right fix as what I did apparently causes leaks :-(
Comment 4•1 year ago
|
||
noteFolderDatabaseGettingBlownAway() didn't keep _indexedMessagesPendingCommitByGlodaId in sync with _indexedMessagesPendingCommitByKey, causing _commitCallback() to report errors when there had been pending commits prior to repairing or compacting a folder.
Updated•1 year ago
|
Comment 5•1 year ago
|
||
Comment on attachment 9488338 [details]
Bug 1903744 - Fix gloda console errors after folder repair or compact. r=#thunderbird-reviewers
Revision D249790 was moved to bug 1963490. Setting attachment 9488338 [details] to obsolete.
Comment 6•1 year ago
|
||
Sorry, wrong bug ID. The patch that was moved does not solve the issue for the cases reported here or in the duplicate bug 1635029, which seem to occur mainly in automated tests.
Comment 7•23 days ago
|
||
This is being fixed as well by the proposed patch for bug 1899236.
Description
•