Closed Bug 752749 Opened 13 years ago Closed 13 years ago

After upgrade to Tb 12, very slow message reading and Thunderbird is almost unusable

Categories

(MailNews Core :: Database, defect)

x86
Windows XP
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 750781

People

(Reporter: gerald.guillot, Unassigned)

Details

(Whiteboard: [regression?])

User Agent: Mozilla/5.0 (Windows NT 5.1; rv:12.0) Gecko/20100101 Firefox/12.0 Build ID: 20120420145725 Steps to reproduce: I have migrated to Thunderbird v 12 Actual results: Very slow message reading. All other functions seem ok (i.e. working and quick). After a lot of tests and reinstallation of the software, I discovered that some errors were shown in the console : 2012-05-08 01:30:11 gloda.datastore ERROR Unexpected error when trying to open the database: ReferenceError: aDBFile is not defined 2012-05-08 01:30:11 gloda.everybody ERROR !!! error loading resource:///modules/gloda/fundattr.js 2012-05-08 01:30:11 gloda.everybody ERROR (resource:///modules/gloda/datastore.js:1423) TypeError: this.asyncConnection is null 2012-05-08 01:30:11 gloda.explattr ERROR Error in init: TypeError: this.asyncConnection is null 2012-05-08 01:30:11 gloda.everybody ERROR (resource:///modules/gloda/datastore.js:1555) TypeError: this.asyncConnection is null 2012-05-08 01:30:11 gloda.everybody ERROR !!! error loading resource:///modules/gloda/noun_mimetype.js 2012-05-08 01:30:11 gloda.everybody ERROR (resource:///modules/gloda/datastore.js:1423) TypeError: this.asyncConnection is null 2012-05-08 01:30:11 gloda.abattrs ERROR Error in init: TypeError: this.asyncConnection is null 2012-05-08 01:30:11 gloda.everybody ERROR !!! error initializing resource:///modules/gloda/index_ab.js 2012-05-08 01:30:11 gloda.abattrs ERROR Error in init: TypeError: this.asyncConnection is null Thunderbird is almost unusable. Thanks a lot for your help.
Severity: normal → critical
I also saw same errors every time when I started Tb 12.0.1 using a Tb's profile which was used by many Tb releases of some localizations and beta/aurora/trunk daily builds. Because I suspected broken global-messages-db.sqlite, I disabled Gloda and deleted global-messages-db.sqlite, and problem disappeared even after I re-enabled Gloda. After it, I couldn't observe such error messages from Gloda. As I didn' keep backup of the profile, I can't see errors any more. I might have used add-on related to Gloda(e.g. GlodaQuilla) by the profile in the past. Do you see your problem with -safe-mode of Tb? Can you reproduce your problem with newly created Tb profile by Tb 12?
Thanks Wada for your help. I tried to delete (in reality move in another directory) "global-messages-db.sqlite" and "global-messages-db.sqlite-journal and disable Gloda. The console shows now the following message : "Horodatage : 08/05/2012 11:22:01 Erreur : this.asyncConnection is null Fichier Source : resource:///modules/gloda/datastore.js Ligne : 1555" I tried to start TB12 in safe-mode : no change from the precedent state I didn't try to start a newly created profile, because I'm afraid to make some mistakes. Please note that : - I have a very big number of professional emails (but until now, TB hadn't any problem to manage them very quickly), - TB is installed on C:, but the emails are on E: (local disk), - The HDD have enough disk space.
Additional comment : Beyond the error message of the console, what is the most important for me is that the initial problem is still present : TB takes between 4 and 20 seconds to display a message ! It is almost unusable.
Component: General → Database
Product: Thunderbird → MailNews Core
QA Contact: general → database
Whiteboard: [regression?]
(In reply to gerald.guillot from comment #0) > Build ID: 20120420145725 > Steps to reproduce: > I have migrated to Thunderbird v 12 Tb 12.0.0? Tb 12.0.1? What is shown at User Agent of Help/Troubleshooting Information? If Tb 12.0.1(win 32), following is shown. > Mozilla/5.0 (Windows NT 5.1; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
@Wada : Yes, I'm using TB 12.0.1 Mozilla/5.0 (Windows NT 5.1; rv:12.0) Gecko/20120428 Thunderbird/12.0.1 @Ludovic Hirlimann : - I looked at https://bugzilla.mozilla.org/show_bug.cgi?id=750781#c11 - I deleted the folders called "places.sqlite-wal" and "places.sqlite-shm" located in the profile folder - TB 12.0.1 works very well now !! Thanks a lot ! Problem is solved Thunderbird is still the best ! Many thanks to Wada, Wayne and of course, Ludovic Hirlimann.
I could see the error messages from Gloda again by Tb trunk 2012-05-09 daily build. (1) With Tb 12.0.1, Gloda is disabled, global-messages-db.sqlite is deleted, Tb 12.0.1 is restarted. (2) With Tb 12.0.1, Gloda is enabled, global-messages-db.sqlite is created. Tb 12.0.1 is restarted multiple times, and no problem occurs around Gloda. (3) With Tb 12.0.1, Gloda is disabled. global-messages-db.sqlite(size=41 KB) created by Tb 12.0.1 remains. (4) Start Tb trunk 2012-05-09 build8Tb 15.0a1, using same profile. => Error messages from Gloda in comment #0. This occurs upon each restart of Tb trunk. (5) Start Tb 12.0.1, using same profile. => Error messages from Gloda in comment #0. This occurs upon each restart of Tb 12.0.1. Add-on of Extended Folder Column and Test Pilot for Thunderbird is disabled(no other add-ons), so add-on is irrelevant to problem. Incompatibility of global-messages-db.sqlite due to different SQLite version?
Status: UNCONFIRMED → NEW
Ever confirmed: true
Previous comment was not accurate. I perhaps used profile by older Tb versions than Tb 12 for testing. It looks incompatibility between Tb 9 and Tb 12/Tb 15. (I don't have Tb 10) (1-1) With Gloda disabled, restart Tb 9.0.1, terminate Tb. (1-2) With Gloda disabled, restart Tb 12.0.1 or Tb 15.0a1 => Error is observed. (2-1) With Gloda disabled, restart Tb 9.0.1, terminate Tb. (2-2) With Gloda disabled, restart Tb 11.0.1 => Error is not observed. (2-3) With Gloda disabled, restart Tb 12.0.1 or Tb 15.0a1 => Error is not observed. If Gloda is disabled and the Gloda error doesn't occur, global-messages-db.sqlite looks re-initialized by the Tb release.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
Changing bug summary according to comment #0 and duping, because Gloda's error message was irrelevant to original Slowness problem.
Summary: Gloda database errors → After upgrade to Tb 12, very slow message reading and hunderbird is almost unusable
In reality, I had two bugs : - slow message reading : duplicate of bug 750781 (solved) - Gloda database error : still present, see Description and comment #7 (not urgent for me : I'll check the bugs database and Wada messages to solve it in the future)
Following message is shown by Tb 9.0.1 and Tb 11.0.1. > gloda.datastore WARN Global database has been purged due to schema change. Tb 11.0.1 detects schema change from Tb 9, and re-initializes global-messages-db.sqlite. Tb 12.0.1/Tb 15.0a1 looks; Not torerant with schema of Tb 9. => Error occurs. Fails to change/upgrade schema from Tb 9. global-messages-db.sqlite is not initialized, not re-usable. Torelant with schema of Tb 11. => No error occurs, global-messages-db.sqlite is re-used or re-initialized. Torelant with other's schema each other, or schema is same or compatible. => No error occurs, even when profile is shared by Tb 12 and Tb 15.0a1. From which version of Tb did you migrated to Tb 12? > Build ID: 20120420145725 Migrated to Tb 12.0.0 first? (20120420 is date of Tb 12.0.0) Or migrated to Tb 12.0.1 since initial? (should be dated 20120420)
Summary: After upgrade to Tb 12, very slow message reading and hunderbird is almost unusable → After upgrade to Tb 12, very slow message reading and Thunderbird is almost unusable
(In reply to gerald.guillot from comment #11) > In reality, I had two bugs : > (snip) > - Gloda database error : still present, see Description and comment #7 Don't worry about it. If gloda error of comment #0 is shown at Error Console due to "scheme change detection failuire" of Tb 12 or later, Global Search won't work(return nothing to local Global Search). So, bug will be opened sooner or later.
FYI. I've opened Bug 754780 for gloda error message part you found.
You need to log in before you can comment on or make changes to this bug.