523868 - [faceted search] stopped at "Searching...". No search results.

Status: RESOLVED WORKSFORME

(Thunderbird :: Search, defect)

Description

[Wayne Mery (:wsmwk)]

[followon to bug 523809]

I had typed "Updated Subscriber Notice" into Search all messages, hit enter, and the screen stayed at "Searching".  Did this in the third tab. Had recently been moving local folders around and eventually crashed, as described in bug 523809.  High CPU for some period of time, but then it backed down. But never got search results.

Filing as Unconfirmed, as this may well be a duplicate but I didn't find one.

Comment 1

[Wayne Mery (:wsmwk)]

maybe related to bug 519543 Gloda search while indexing hangs and is very slow; search activity should suppress indexing.

However, I don't see 519543 mention that results might never get returned.

Comment 2

[Bob Clary [:bc] (inactive)]

dupe of bug 523806 ?

I see that all of my saved searches of news or rss feeds fail to display the page. I see tons of 

2009-10-22 10:28:03	gloda.indexer	WARN	Problem during [job:folder delta:0 id:110 items:0 offset:1 goal:1473], trying to recover.  Problem was at undefined:2668: [Exception... "Component returned failure code: 0x80004003 (NS_ERROR_INVALID_POINTER) [nsIMsgFolder.GetMessageHeader]"  nsresult: "0x80004003 (NS_ERROR_INVALID_POINTER)"  location: "JS frame :: file:///Applications/Shredder.app/Contents/MacOS/modules/gloda/indexer.js :: gloda_indexMessage :: line 2668"  data: no]


Error: uncaught exception: [Exception... "Component returned failure code: 0x80550006 [nsIMsgFolder.msgDatabase]"  nsresult: "0x80550006 (<unknown>)"  location: "JS frame :: chrome://messenger/content/mailWidgets.xml :: parseFolder :: line 2006"  data: no]

Comment 3

[Bob Clary [:bc] (inactive)]

PS. The behavior I am seeing is a regression on 3.0/Mac with today's build from yesterday. I can't reproduce it with 3.1 from today.

Comment 4

[Wayne Mery (:wsmwk)]

Thanks. but I don't get that far.  

today's successful search would indicate that there are indeed messages in folders which would have been properly indexed at the time of my failure.  build is several days old  - Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.5pre) Gecko/20091016 Shredder/3.0pre

Comment 5

[Bob Clary [:bc] (inactive)]

Hmm. Mine just started today. I try to updated every day. My last comment is wrong about 3.1. After selecting several different saved search folders, my messages stopped displaying again.

Comment 6

[Wayne Mery (:wsmwk)]

Attachment: stopped at Searching ...

seeing more consistently, with other search terms.
thobber to left of "Searching..." is spinning

Comment 7

[Andrew Sutherland [:asuth] (he/him)]

Wayne, does this still happen?  If it does, there should really be some form of message in the error console...

Comment 8

[Wayne Mery (:wsmwk)]

I can't reproduce ATM on two PC, 3.0RC1 and 3.0rc2. 
=> WFM
My guess is I checked the console and didn't see anything.

(docked error console would be nice for testers)

Comment 9

[Wayne Mery (:wsmwk)]

seen again. work gateway vista. Mozilla/5.0 (Windows NT 6.0; rv:2.0b9pre) Gecko/20110106 Thunderbird/3.3a2pre

I don't know if today's case is a match to the original report, but the symptom is the same, so reopening. Haven't attempted to reproduce.

1. renamed .sqlite db because I wanted to rebuild gloda
2. start tb, login to two imap accounts
3. search on first account [e-mail] - 46 results
4. click open list
5. search on second account [e-mail] - stuck at Searching...
repeat #3 and #5, same results

- big memory usge - TB currently using 480MB (my normal usage is 125MB-200MB)
- error console shows ...
Error: row is undefined
Source File: chrome://gloda/content/glodacomplete.xml
Line: 88


partial repeat (did not delete db), this time watching memory usage, and not logged in to imap
2. start tb, 
-- memory usage settles in at about 225MB
3. search on first account [e-mail] - 1,477 results
4. click open list
-- memory usage at 240MB
5. search on second account [e-mail] - after several seconds at Searching... it returns with 18,718 results
-- memory usage at 500MB
(10 minutes later)
-- memory usage at ~530MB

Comment 10

[Wayne Mery (:wsmwk)]

logged in to 1 imap account. doing nothing special. 
no 580MB-590MB

Comment 11

[Wayne Mery (:wsmwk)]

(In reply to comment #10)
> logged in to 1 imap account. doing nothing special. 
> no 580MB-590MB
now 580MB-590MB


...now that indexing is finished I tried #5 again. waited 130 seconds for results, during which time memory increased by 500MB for 70+K responses in facet results

Comment 12

[Wayne Mery (:wsmwk)]

We don't have steps for this bug, so I don't that the following is a solid match to this bug, but here goes ...

I can make "Searching..." happen by removing a single account from mail.accountmanager.accounts, restart, then attempt any search. (I want to keep the account definition, but not be hounded by it in the UI for a few weeks)

Comment 13

[Wayne Mery (:wsmwk)]

seen again, similar to comment 9.

I had disabled gloda for a few days and deleted the db. today reenabled and indexing is still in progress (50% done?).  Tried a couple searches, waited forever - no results. Retried, suddenly, started getting search results.  But the ones that didn't get results never completed

Comment 14

[Wayne Mery (:wsmwk)]

don't see this now.
comment 13 turned out to be something else