Search result count vanishes [was: Search on Local Folders never stops]
Categories
(Thunderbird :: Search, defect)
Tracking
(Not tracked)
People
(Reporter: hrdubwd, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: hang, perf)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:134.0) Gecko/20100101 Firefox/134.0
Steps to reproduce:
Use Ctrl-Shift-F, search all local folders for subject; body text; to, from or cc.
Actual results:
There are hits, very quickly (mere seconds), but the search itself never stops. One cannot have confidence that all folders (and subfolders) have been searched and that all hits have been found.
Expected results:
On a fast machine, as is this, search should be completed rapidly, not apparently still running the following day!
If the search is done on top level folders, it does indeed stop very quickly indeed = one or two seconds mostly. I have tested all such. While searching body is slower, it is certainly taking longer than the aggregate times.
The absence of any indication of which folder is being searched makes it hard to know where the hangup lies.
It is essential that all folders be searchable - as used to be the case.
Comment 1•7 months ago
|
||
There's a checkbox for whether to include search subfolders or not. And whether to run the search on server or not.
Reporter | ||
Comment 2•7 months ago
|
||
Yes, I always want to search subfolders, and that is what I am reporting. I never see a 'server' checkbox, in fact I cannot find any setting for searching on the server (which I do not want to do anyway, ever, since everything is downloaded. As far as I can tell, this should not be happening when searching "Local Folders" or anything below that.
Either way, how is that relevant? If there is any condition where a problem arises it should be announced, not hang.
(I search I started 2 days ago has still not "stopped" ...)
Comment 3•7 months ago
|
||
(That would be for imap, you didn't say it was a local account.)
Check the Error Console for anything relevant. It normally works.
Reporter | ||
Comment 4•7 months ago
|
||
Sorry, I thought saying 'search all local folders ' was enough.
Many like this:
12:29:05.556 NS_ERROR_FILE_CORRUPTED: Component returned failure code: 0x8052000b (NS_ERROR_FILE_CORRUPTED) [mozIStorageStatement.executeStep]
all referencing:
Source of: jarf11e:///C:/Program%20Files/Mozilla%20Thunderbird/omni.ja!/modules/SQLiteDirectory.sys.mjs - Mozilla Thunderbird
No idea how to deal with that.
Comment 5•7 months ago
|
||
That could certainly cause issues. In your profile delete the addressbook that's corrupted (abook.sqlite, history.sqlite ...)
Reporter | ||
Comment 6•7 months ago
|
||
Delete my address book? Lose everything?
I am puzzled by history.sqlite : last written in 2023-02-05 ! Delete this? What is it for?
(The -wal (0 bytes!, July last year) and -shm (2 days old) seem non-functional.)
"Clear recent history" is greyed out.
Comment 7•7 months ago
|
||
Well, you'd only need to delete the one(s) corrupted. Find out which (by trial and error?), before deleting.
Reporter | ||
Comment 8•7 months ago
|
||
History I do not much care about - it seems entirely defunct anyway.
But there is only one address book, other than 'v2' (2021-20) and 'v3' (2022-08). How does one deal with losing everything? I know there is no repair mechanism, which is a bit poor. But how about export and re-import? How to find where the corruption is, presumably in a record or two.
Reporter | ||
Comment 9•7 months ago
|
||
Closed TB, renamed 3 history files zzz*.sqlite*, restarted:
13:18:54.695
Uncaught NS_ERROR_NOT_INITIALIZED: Component returned failure code: 0xc1f30001 (NS_ERROR_NOT_INITIALIZED) [nsIMsgSendLater.hasUnsentMessages]
haveUnsentMessages chrome://messenger/content/mail-offline.js:86
shouldSendUnsentMessages chrome://messenger/content/mail-offline.js:165
loadStartFolder chrome://messenger/content/messenger.js:820
mail-offline.js:86
13:18:56.173
Invalid or corrupted PDF file.
PDF.js v4.4.10 (build: 5c51d5622)
Message: Invalid PDF structure. viewer.mjs:11135:13
13:18:56.176 Uncaught (in promise)
Object { message: "Invalid PDF structure.", name: "InvalidPDFException", stack: "BaseExceptionClosure@resource://pdf.js/build/pdf.mjs:455:29\n@resource://pdf.js/build/pdf.mjs:458:2\n" }
13:23:02.295 NotFoundError: No such JSProcessActor 'BrowserToolboxDevToolsProcess'
13:24:12.981 tb.account.size_on_disk - Truncating float/double number.
I then did a search on Local Folders | Subfolders | Subject : very quickly completed (13 hits) , but NO count message in the status bar.
I hit 'Search' again, it found 4 items and has not stopped.
Console (after restarting it, there is no auto update, it seems):
13:30:30.696 NotFoundError: No such JSProcessActor 'BrowserToolboxDevToolsProcess'
So was history the problem for thos many errors? But search is still not behaving.
Restart TB, repeat the search: 13 hits (the count showed for a mere fraction of a second in the status bar!). Search again, it does not stop, 4 hits only. No further errors in the console, just:
13:35:15.232
Uncaught NS_ERROR_NOT_INITIALIZED: Component returned failure code: 0xc1f30001 (NS_ERROR_NOT_INITIALIZED) [nsIMsgSendLater.hasUnsentMessages]
haveUnsentMessages chrome://messenger/content/mail-offline.js:86
shouldSendUnsentMessages chrome://messenger/content/mail-offline.js:165
loadStartFolder chrome://messenger/content/messenger.js:820
mail-offline.js:86
13:37:29.709 NotFoundError: No such JSProcessActor 'BrowserToolboxDevToolsProcess'
Now what?
Comment 10•7 months ago
|
||
(In reply to Dr B W Darvell from comment #8)
But there is only one address book, other than 'v2' (2021-20) and 'v3' (2022-08). How does one deal with losing everything? I know there is no repair mechanism, which is a bit poor. But how about export and re-import?
Does export+import not work?
How to find where the corruption is, presumably in a record or two.
For now, keep a copy of the original file.
Reporter | ||
Comment 11•7 months ago
|
||
I had kept the original history items, so that was safe.
I had not found the export and import options before - the pop-up on the address book names is erratic to say the least - I spotted it once then could not get it back no matter what I tried. I then realized it was under Tools as well, not where I would have expected it under Files ... all address books saved as csv.
I renamed history (3 files), imported the Collected addresses, which appeared to be the one causing the problem since leaving Personal in place (abook, I assume) did not give the errors, as I reported above.
Repeating the search sequence above, first time 13 hits (momentary status line message!) with a clear and quick end. The second time as before - 4 hits only and NO stop, just "Searching ..." ... for ever.
The only errors are these on start up:
16:05:51.205 Uncaught NS_ERROR_NOT_INITIALIZED: Component returned failure code: 0xc1f30001 (NS_ERROR_NOT_INITIALIZED) [nsIMsgSendLater.hasUnsentMessages]
haveUnsentMessages chrome://messenger/content/mail-offline.js:86
shouldSendUnsentMessages chrome://messenger/content/mail-offline.js:165
loadStartFolder chrome://messenger/content/messenger.js:820
and
16:08:44.042 NotFoundError: No such JSProcessActor 'BrowserToolboxDevToolsProcess'
after a search.
After a while I see:
16:10:35.199 tb.account.size_on_disk - Truncating float/double number. 2 (2)
16:13:34.487 NotFoundError: No such JSProcessActor 'BrowserToolboxDevToolsProcess' (2)
The search problem is not in the address books, but is clearly in the search mechanism itself. Closing the search window and re-opening it has not effect, the search still fails. It needs TB to be restarted, and then only one search is effective. That is not a practical way of working.
Export-import has helped in that those address book-related errors have been cleared, which is good in itself, but not now relevant, obviously.
What next?
Thanks.
Reporter | ||
Comment 12•6 months ago
|
||
The 'not stopping' problem seems to have gone away at the last update (128.7.0).
However, the momentary flash of the found count persists. Blink and you miss it.
Comment 13•6 months ago
|
||
Please modify the title to reflect the remaining issue, IF it still happens in 128.8.0 which comes out next week.
Reporter | ||
Comment 14•6 months ago
|
||
Will do.
Thanks.
Reporter | ||
Comment 15•5 months ago
|
||
The message shows for half a second ...
Updated•5 months ago
|
Reporter | ||
Comment 16•11 days ago
|
||
See also 1959382.
Description
•