Closed Bug 1416508 Opened 7 years ago Closed 7 years ago

Indexing freezes

Categories

(Thunderbird :: Search, defect)

56 Branch
Unspecified
macOS
defect
Not set
major

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: mitra_lists, Unassigned)

Details

I'm seeing Gloda freezing during Indexing. Its consistent, though freezes at a different message each time (I'm not sure if it indexes in order. Having deleted global-messages-db.sqlite it means I have no way to search Archived mail :-( (prior to deleting it, I could get old messages from there, but nothing new was being added). I suspect the Conversations add-on because a) I think it started around the time I started using it again and b) because prior experience of it being problematic since it does a lot of things itself and disables other TB features. I've tried: Disabling Conversations Add-On (and restart) as I saw a bug report related to that and freezing. Disabling all Add-Ons Rebuilding Inbox (it always freezes in that folder, but maybe because its the first folder it tries) Deleting the global-messages-db.sqlite file (after rebuilding inbox) I saw a similar issue: https://bugzilla.mozilla.org/show_bug.cgi?id=881829 which refered to the GlodaQuilla add-on but it wont let me install that since it doesnt support current version. The Error Console has two related messages repeated multiple times. 2017-11-12 07:44:57 gloda.datastore ERROR adjustMessageAttributes: [Exception... "Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [mozIStorageAsyncStatement.bindByIndex]" nsresult: "0x8000ffff (NS_ERROR_UNEXPECTED)" location: "JS frame :: resource:///modules/gloda/datastore.js :: gloda_ds_adjustMessageAttributes :: line 2974" data: no] log4moz.js:685 2017-11-12 07:44:57 gloda.datastore ERROR adjustMessageAttributes: [Exception... "Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [mozIStorageAsyncStatement.bindByIndex]" nsresult: "0x8000ffff (NS_ERROR_UNEXPECTED)" location: "JS frame :: resource:///modules/gloda/datastore.js :: gloda_ds_adjustMessageAttributes :: line 2974" data: no]
I just saw 57.0b1 is out and it has the same problem. The Error Messages (and I just noticed I can expand one for better stack trace) are now ... 2017-11-12 08:16:50 gloda.datastore ERROR adjustMessageAttributes: [Exception... "Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [mozIStorageAsyncStatement.bindByIndex]" nsresult: "0x8000ffff (NS_ERROR_UNEXPECTED)" location: "JS frame :: resource:///modules/gloda/datastore.js :: gloda_ds_adjustMessageAttributes :: line 2974" data: no] 2017-11-12 08:16:51 gloda.datastore ERROR adjustMessageAttributes: [Exception... "Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [mozIStorageAsyncStatement.bindByIndex]" nsresult: "0x8000ffff (NS_ERROR_UNEXPECTED)" location: "JS frame :: resource:///modules/gloda/datastore.js :: gloda_ds_adjustMessageAttributes :: line 2974" data: no] log4moz.js:685 CApp_append resource:///modules/gloda/log4moz.js:685:7 Logger_log resource:///modules/gloda/log4moz.js:379:7 Logger_error resource:///modules/gloda/log4moz.js:387:5 gloda_ds_adjustMessageAttributes resource:///modules/gloda/datastore.js:3006:7 gloda_ns_grokNounItem resource:///modules/gloda/gloda.js:2215:5 next self-hosted:1188:9 gloda_index_workBatch resource:///modules/gloda/indexer.js:1027:19 next self-hosted:1188:9 gloda_index_callbackDriver resource:///modules/gloda/indexer.js:820:18 gloda_index_timerCallbackDriver resource:///modules/gloda/indexer.js:750:5
And another point of reference - I also recently updated to OSX 10.13.1 (High Sierra) so the start of this problem could have been tied to that ?
Yes, conversations had an issue at one point. Reproduces in safe mode? https://support.mozilla.org/en-US/kb/safe-mode-thunderbird
Flags: needinfo?(mitra_lists)
Wayne - sorry, not seeing this problem any more, it happened for months with Gloda searches being essentially unusable, then one day it started working again.
Flags: needinfo?(mitra_lists)
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.