Closed Bug 540952 Opened 16 years ago Closed 15 years ago

Freezes system as soon as inbox is accessed if Global Search indexing is enabled

Categories

(MailNews Core :: Backend, defect)

x86
All
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: phil, Unassigned)

References

()

Details

(Keywords: hang, perf, qawanted, Whiteboard: [has trace][gs])

Attachments

(1 file)

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.4) Gecko/20091028 Iceweasel/3.5.6 (like Firefox/3.5.6; Debian-3.5.6-1) Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1 I recently tried to upgrade from TB 2 to TB 3. TB3 immediately opens 4 tabs: 2 migration assistant tabs, a "what's new" tab, and the inbox. I can do as much as I want in the Migration Assistant tabs or the What's New tab, but as soon as I switch to the inbox tab, the status bar says "Loading Message..." and the application freezes. From there the entire system quickly goes into 100% IO Wait, and if I don't catch it quickly enough the machine will completely lock. I have 2 POP accounts and 1 IMAP account, and my account size is pretty small: [phil@rider ~]$ du -sh .thunderbird/ 989M .thunderbird/ I have tried many times, but this is consistent. Going back to TB2 works fine, and switching back to TB3 fails again. Reproducible: Always Steps to Reproduce: 1. Open Thunderbird 3 2. Wait for indexing to complete 3. Click Inbox tab. Actual Results: TB froze, then system goes into IO Wait, then machine freezes Expected Results: See a message from my inbox. I have an strace I can upload. stracing helps because it slows the whole thing down preventing my machine from dying before I kill TB.
Strace showing the behavior.
Version: unspecified → 3.0
Try disabling next two new/big features by Tb3, which are enabled by Tb3 by default, first, please. (1) Tools/Options/Advanced/General, disable "Global Search and Indexer" (2) Disable auto-sync of all IMAP account. Check "Keep messages for ...", then Uncheck it. ("offline use" of all folders of the IMAP account is set to "off" by this) > Steps to Reproduce: > 1. Open Thunderbird 3 > 2. Wait for indexing to complete Which indexing? Rebuild-Index? Global Indexer? How did you comfirm that the indexing completed? If you want to enable above features again, watch "Tools/Activity Manager" panel, and wait for completion of auto-sync of all mails in all IMAP folders and wait for end of indexer for all mails, before open bug for performance related issue just after upgrade. After that, check Tb3's behaviour of auto-sync and Global Indexer just after upgrade from Tb2, please.
OK, so this is odd. IN the migration assistant I had chosen to not sync ANY imap accounts, but my 1 IMAP account was still set to Sync in "Accounts". I turned both off, TB3 worked fine. I turned both back on, TB3 still works. Then I re-disabled IMAP syncing for my 1 IMAP account. Thanks. > Which indexing? Rebuild-Index? Global Indexer? I"m not sure, it said "Determining which messages to index" and listed various local folders in POP accounts for over an hour. When it was done, I clicked on the inbox tab and things froze. I didn't know about the new Activity Manager feature or I would have checked that. I went by the lack of anything in the status bar and the fact that the processes was seemingly idle (in top).
(In reply to comment #3) > > Which indexing? Rebuild-Index? Global Indexer? > I"m not sure, it said "Determining which messages to index" (snip) It's message by Global Indexer.
So - it seems like there's some bug in migration, thought I don't know how to reproduce it now. If there's something I can do to help track it down, great. If not, you can close this bug. Thanks for your help. - Phil
before closing, can you/we summarize what (theoretically) set of conditions or steps might reproduce the problem? xref Bug 528505 - hang after starting 3.0rc1
Keywords: hang, perf
Summary: Freezes system as soon as inbox is accessed → Freezes system as soon as inbox is accessed with "Loading Message..."
It's funny you should ask, since I just reproduced it yesterday by accident. I mistakenly opened thunderbird 2. Closed it. Opened TB3, and had the same thing. I had to kill it, disable the Global Indexer (without going to the "main" tab as it were), exit, restart, go to the main tab, let a message load, and then re-enable the Global Indexer. Note that this is with 3.0.1.
ludo, bwinton, does this sound familiar? (In reply to comment #7) > I mistakenly opened thunderbird 2. Closed it. Opened TB3, and had the same > thing. I had to kill it, disable the Global Indexer (without going to the > "main" tab as it were), exit, restart, go to the main tab, let a message load, > and then re-enable the Global Indexer. <chuckles> and it also gave you the migration assistant, etc?
Yes, it did. Two of them (just like it did when I first installed TB3, which I never understood), plus the "what's new" tab.
No, I didn't run TB 2 that much, and think I created a new profile for TB3, so never really did much migration. Since Phil mentioned the Global Indexer, maybe asuth has an idea?
Phil does your strace with symbols??
Whiteboard: [has trace]
inbox is one possibility. It can be any folder with new messages in it. I see similar things sometimes when switching to a folder that gets new messages via filter - ui hangs 5-10 sec other bugs which cite "Determining which messages to index" bug 528499, bug 539641, bug 542498, bug 545993 Perhaps this is related to one of the gloda issues andrew is working on
Status: UNCONFIRMED → NEW
Component: General → Backend
Ever confirmed: true
Keywords: qawanted
OS: Linux → All
Product: Thunderbird → MailNews Core
QA Contact: general → backend
Summary: Freezes system as soon as inbox is accessed with "Loading Message..." → Freezes system as soon as inbox is accessed with "Loading Message..." and "Determining which messages to index"
Version: 3.0 → Trunk
blocking-thunderbird3.1: --- → ?
Wayne: Comment 11 doesn't parse for me. What? As for Comment 12 - this isn't a 5-10 second hang (I get that sometimes too), this is a "entire system gets hosed, and if I'm not quick enough to kill it, I have to reboot". Note that when I upgraded to 3.0.2 the problem returned... I had to disable the Global Indexer, go to the inbox, exit, re-open, and re-enable the Global Indexer in order for TB3 to work.
(In reply to comment #13) > Wayne: Comment 11 doesn't parse for me. What? sorry. i mean, does your strace have thunderbird symbols? see https://developer.mozilla.org/En/How_to_get_a_stacktrace_for_a_bug_report#Alternative_ways_to_get_a_stacktrace > As for Comment 12 - this isn't a 5-10 second hang (I get that sometimes too), > this is a "entire system gets hosed, and if I'm not quick enough to kill it, I > have to reboot". > > Note that when I upgraded to 3.0.2 the problem returned... I had to disable the > Global Indexer, go to the inbox, exit, re-open, and re-enable the Global > Indexer in order for TB3 to work. you are saying those steps are a workaround?
The TB I'm using is the statically compiled one from mozilla.org. That appears to be stripped: thunderbird-3.0.1/thunderbird-bin: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.9, stripped (ignore the directory, the auto-update has upgraded it to 3.0.2) So there's no dbg package I could install that would match the binaries ya'll are providing. So, no, it doesn't have the debug symbols. As for the work-around, yes, please see the first few comments in this bug - I was unable to use TB3x until WADA suggested that in comment 2, which I confirmed worked in Comment 3. However, it's worth noting that it comes *back* if I either launch TB2 and then switch back to TB3, or upgrade the TB3 version. In either case I must re-do the work around to make TB usable.
We're resetting the blocking flag for 3.1 on this bug and instead setting the wanted-thunderbird+ flag. We have too many blocking-3.1 bugs, to the point where it doesn't mean much, and managing the list is making it hard to actually work on closing bugs, which helps no one. Thunderbird 3.1's primary purpose is to allow us to offer a prompted major update to Thunderbird 2 users, to ensure their continued ability to safely use Thunderbird. Thunderbird 2 is built on an outdated version of Gecko, and our long-term ability to maintain the users' safety for Thunderbird 2 users is limited. If you think this bug meets the requirements below, please renominate with a detailed explanation of how it meets the following two criteria, and we will reconsider. To qualify, this bug must either: a) make the upgrade experience from TB2 very painful for a large number of users or b) be a new, reproducible, severe quality issue (eg dataloss, frequent crashes) Just because this bug doesn't block TB3.1 doesn't mean it can't or won't make the release. Once they're done with their blockers (if any), we encourage developers to keep working on non-blocking bugs, and to try to land them as early in the cycle as possible, as non-blocking bugs will become increasingly difficult to land in the later stages of the cycle.
blocking-thunderbird3.1: ? → ---
Flags: wanted-thunderbird+
does stacktrace reveal anything? if not, I'm inclined to change this back to UNCO until there is greater clarity
This is very likely the gloda deletion efficiency bug; we should have the reporter try a 3.1 nightly.
I tried 3.1b2 at the suggestion of Wayne's email to me, but had the same behavior - in fact, my machine froze and I had to reboot. It was, "determining which messages it index in Sent" However, it's worth noting (since, as I mentioned before, the system goes into IOWait), what I'm running Linux software RAID 1 across to drives, on top of which is an LVM setup. While it's not necessarily unusual in something being IO intensive, I did see the md kernel threads being quite busy (though not as busy as thunderbird) as the system ground to a halt. It made me wonder if maybe, just maybe, TB is doing something during it's initial scan that tickles MD in the wrong way...?
Phil, can you update status next week or two based on using version 3.1.5 please (will be out next week). Thanks. note: http://getsatisfaction.com/mozilla_messaging/topics/v3_is_slow_and_hangs_on_determining_which_messages_to_index has gone stagnant and is perhaps unrelated.
Wayne, sorry for the delay, I was relocating across the globe, which puts a dent in response time. Anyway, I had this problem on my upgrade to 3.1.6.
(In reply to comment #18) > This is very likely the gloda deletion efficiency bug; we should have the > reporter try a 3.1 nightly. asuth, was that ^^ fixed?
Deletion got much more efficient, yes, and should be present in any supported builds.
sounds then like the issue might not be gloda related. Phil, 1. can you briefly redescribe the current symptoms of what you see in status bar, activity manaager and error console? 2. is the issue as severe as what you describe in comment 0 3. does the issue go away if you disable global indexing in tools > options > advanced > general
perhaps this is a dup of bug 551209?
wsmwk: 1. Not easily - I can only seem to reproduce it when upgrading. 2. Yes 3. Yes, it does. The issue only exists when the global indexer is enabled.
Phil, doe sthis reproduce with version 5?
Summary: Freezes system as soon as inbox is accessed with "Loading Message..." and "Determining which messages to index" → Freezes system as soon as inbox is accessed if Global Search indexing is enabled
Even with 4, after a complete hardware overall and re-install I can't reproduce it. Of course, I went from p4xeon to a i5, so new arch, new everything... but that machine had to die....
thanks for the update. there might still be an issue, but since we don't have access to the affected machine, let's call this incomplete
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: