Closed
Bug 605996
Opened 14 years ago
Closed 13 years ago
startup crash [@ fts3NodeAddTerm] (all OSes), [@ memcpy | fts3NodeAddTerm] (windows), [@ fastcopy_I]
Categories
(MailNews Core :: Database, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 552050
People
(Reporter: wsmwk, Unassigned)
References
()
Details
(Keywords: crash, Whiteboard: [gs][gssolved])
Crash Data
crash [@ fts3NodeAddTerm] (all), [@ memcpy | fts3NodeAddTerm] (windows) #21 crash for v3.0.8, [@ fastcopy_I] - [@ fts3NodeAddTerm] fastcopy_I bp-9c85ded0-e069-4b90-a627-5d19e2101007 v3.1.4 0 mozcrt19.dll fastcopy_I 1 mozcrt19.dll _VEC_memcpy 2 mozcrt19.dll _VEC_memcpy 3 sqlite3.dll fts3NodeAddTerm db/sqlite3/src/sqlite3.c:104903 4 sqlite3.dll fts3NodeAddTerm db/sqlite3/src/sqlite3.c:104945 5 sqlite3.dll fts3NodeAddTerm db/sqlite3/src/sqlite3.c:104945 6 sqlite3.dll fts3NodeAddTerm db/sqlite3/src/sqlite3.c:104945 7 sqlite3.dll fts3SegWriterAdd db/sqlite3/src/sqlite3.c:105134 8 sqlite3.dll fts3MergeCallback db/sqlite3/src/sqlite3.c:105414 9 sqlite3.dll sqlite3Fts3SegReaderIterate db/sqlite3/src/sqlite3.c:105531 10 sqlite3.dll fts3SegmentMerge db/sqlite3/src/sqlite3.c:105703 11 sqlite3.dll fts3AllocateSegdirIdx db/sqlite3/src/sqlite3.c:104278 12 sqlite3.dll sqlite3Fts3PendingTermsFlush db/sqlite3/src/sqlite3.c:105747 13 sqlite3.dll fts3PendingTermsDocid db/sqlite3/src/sqlite3.c:104080 14 sqlite3.dll sqlite3Fts3UpdateMethod db/sqlite3/src/sqlite3.c:105864 15 sqlite3.dll fts3UpdateMethod db/sqlite3/src/sqlite3.c:100420 bp-ce64c1c6-ee83-4696-9fe5-9a65f2101020 memcpy - fts3NodeAddTerm v3.1.5 0 mozcrt19.dll memcpy memcpy.asm:250 1 sqlite3.dll fts3NodeAddTerm db/sqlite3/src/sqlite3.c:113556 2 sqlite3.dll fts3SegWriterAdd db/sqlite3/src/sqlite3.c:113787 3 sqlite3.dll fts3MergeCallback db/sqlite3/src/sqlite3.c:114067 4 sqlite3.dll sqlite3Fts3SegReaderIterate db/sqlite3/src/sqlite3.c:114184 5 sqlite3.dll fts3SegmentMerge db/sqlite3/src/sqlite3.c:114356 6 sqlite3.dll fts3AllocateSegdirIdx db/sqlite3/src/sqlite3.c:112931 7 sqlite3.dll fts3SegmentMerge db/sqlite3/src/sqlite3.c:114313 8 sqlite3.dll fts3AllocateSegdirIdx db/sqlite3/src/sqlite3.c:112931 9 sqlite3.dll sqlite3Fts3PendingTermsFlush db/sqlite3/src/sqlite3.c:114400 10 sqlite3.dll sqlite3VtabSync db/sqlite3/src/sqlite3.c:94013 bp-6925cd75-4228-4b7c-9386-2a5ac2101013 fts3NodeAddTerm 0 sqlite3.dll fts3NodeAddTerm db/sqlite3/src/sqlite3.c:104908 1 sqlite3.dll fts3NodeAddTerm db/sqlite3/src/sqlite3.c:104957 2 sqlite3.dll fts3SegWriterAdd db/sqlite3/src/sqlite3.c:105134 3 sqlite3.dll fts3MergeCallback db/sqlite3/src/sqlite3.c:105414 4 sqlite3.dll sqlite3Fts3SegReaderIterate db/sqlite3/src/sqlite3.c:105590 5 sqlite3.dll fts3SegmentMerge db/sqlite3/src/sqlite3.c:105703 6 sqlite3.dll fts3AllocateSegdirIdx db/sqlite3/src/sqlite3.c:104278 7 sqlite3.dll sqlite3Fts3PendingTermsFlush db/sqlite3/src/sqlite3.c:105747 8 sqlite3.dll sqlite3VtabSync db/sqlite3/src/sqlite3.c:86328 9 sqlite3.dll vdbeCommit db/sqlite3/src/sqlite3.c:48783 10 sqlite3.dll sqlite3VdbeHalt db/sqlite3/src/sqlite3.c:49241 11 sqlite3.dll sqlite3VdbeExec db/sqlite3/src/sqlite3.c:54843
|
||
Comment 1•14 years ago
|
||
Duplication of the signature [@ fts3NodeAddTerm] within the description of this bugzilla entry was causing problems in the Socorro/Bugzilla cron. I've removed the duplicated term from this bug to allow Socorro to get past this problem. Bug 620990 addresses this issue within Socorro.
Summary: crash [@ fts3NodeAddTerm] (all), [@ memcpy | fts3NodeAddTerm] (windows), [@ fastcopy_I] - [@ fts3NodeAddTerm] → crash [@ fts3NodeAddTerm] (all), [@ memcpy | fts3NodeAddTerm] (windows), [@ fastcopy_I]
|
Reporter | |
Comment 2•14 years ago
|
||
based on http://getsatisfaction.com/mozilla_messaging/topics/crashes_everytime_it_starts_unless_i_unplug_the_ethernet_cable ... this crash should get resolved when bug 552050 is fixed.
|
Assignee | |
Updated•13 years ago
|
Crash Signature: [@ fts3NodeAddTerm]
[@ memcpy | fts3NodeAddTerm]
[@ fastcopy_I]
|
|
Reporter | |
Comment 3•13 years ago
|
||
the original issue of this was fixed in bug 552050. so duping. however, as protz has noted on irc, there is a resurgence of corrupt db in recent versions. bp-9b4910ab-8731-4e8e-8151-402d92111104 may be an example. xref Bug 616859] gloda needs to better detect and correct for corrupt databases. and perhaps we need a new crash bug for the remaining crashes
Status: NEW → RESOLVED
Crash Signature: [@ fts3NodeAddTerm]
[@ memcpy | fts3NodeAddTerm]
[@ fastcopy_I] → [@ fts3NodeAddTerm]
[@ memcpy | fts3NodeAddTerm]
[@ fastcopy_I]
Closed: 13 years ago
Resolution: --- → DUPLICATE
Summary: crash [@ fts3NodeAddTerm] (all), [@ memcpy | fts3NodeAddTerm] (windows), [@ fastcopy_I] → startup crash [@ fts3NodeAddTerm] (all OSes), [@ memcpy | fts3NodeAddTerm] (windows), [@ fastcopy_I]
Whiteboard: [gs] → [gs][gssolved]
|
||
Comment 4•13 years ago
|
||
Just for the record, corrupt DBs symptoms are: gloda not working, conversations stopped working suddenly, tons of gloda-related errors in the error console. If Thunderbird crashes, I'm not sure it's the same problem. Anyway, bug 616859 is about corrupted database which can be opened without errors, but that we cannot subsequently use. Hope it's making things clearer :)
You need to log in
before you can comment on or make changes to this bug.
Description
•