Closed
Bug 783619
Opened 13 years ago
Closed 10 years ago
Some IM conversations are not fully indexed
Categories
(Thunderbird :: Instant Messaging, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1146698
People
(Reporter: mconley, Unassigned)
References
Details
Symptoms:
IM Conversations (usually Twitter conversations for me, but I'm not sure how much that matters) aren't being fully indexed. The first one or two messages will be added to imConversations_content, but after that, it appears as if the row stops being updated as the conversations continue.
I discovered this while fiddling with bug 783022, but this one differs because it seems as if the partially-indexed messages are *not* re-indexed when TB restarts. I think that rules lastModifiedTime bugs out, unless we're somehow able to cache lastModifiedTime and write to the JSON cache before the indexing completes, and then do a shutdown or something.
I can't find a reliable way of reproducing this one, but I've noticed it happening periodically on my Windows machine.
Just something to keep an eye out for.
Comment 1•10 years ago
|
||
(note this bug is quite old, but as you are currently fixing this code...)
Flags: needinfo?(nhnt11)
Updated•10 years ago
|
tracking-thunderbird38:
--- → ?
tracking-thunderbird_esr38:
--- → ?
Comment 2•10 years ago
|
||
Sounds a lot like bug 1146698, provisionally duping.
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(nhnt11)
Resolution: --- → DUPLICATE
Comment 3•10 years ago
|
||
Removing tracking request since this is now duped, and the duped-to bug has had no progress either.
Updated•10 years ago
|
tracking-thunderbird38:
- → ---
tracking-thunderbird_esr38:
- → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•