Closed Bug 536617 Opened 15 years ago Closed 6 years ago

FF startup crash [@ sqlite3DbFree]

Categories

(Toolkit :: Storage, defect, P5)

x86
All
defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox47 --- affected
firefox48 --- affected

People

(Reporter: wsmwk, Unassigned)

References

()

Details

(Keywords: crash, Whiteboard: [startupcrash])

Crash Data

FF startup crash [@ sqlite3DbFree]

FF 3.5.5 and 3.5.6.
places?

Mac bp-e8c2a562-cca7-41bc-a1d4-29ce52091127
0	libsqlite3.dylib	sqlite3DbFree	 db/sqlite3/src/sqlite3.c:15682
1	libsqlite3.dylib	sqlite3VdbeMemGrow	db/sqlite3/src/sqlite3.c:45322
2	libsqlite3.dylib	sqlite3VdbeMemNulTerminate	db/sqlite3/src/sqlite3.c:45408
3	libsqlite3.dylib	sqlite3VdbeRealValue	db/sqlite3/src/sqlite3.c:45617
4	libsqlite3.dylib	sqlite3Step	db/sqlite3/src/sqlite3.c:52693
5	libsqlite3.dylib	sqlite3_step	db/sqlite3/src/sqlite3.c:49447
6	libsqlite3.dylib	sqlite3_exec	db/sqlite3/src/sqlite3.c:72032
7	XUL	mozStorageConnection::ExecuteSimpleSQL	storage/src/mozStorageConnection.cpp:372
8	XUL	nsNavHistory::PreparePlacesForVisitsDelete	toolkit/components/places/src/nsNavHistory.cpp:4400
9	XUL	nsNavHistory::RemovePagesInternal	toolkit/components/places/src/nsNavHistory.cpp:4360
10	XUL	nsNavHistory::RemovePagesByTimeframe	toolkit/components/places/src/nsNavHistory.cpp:4698 


windows bp-4f2f101c-f8cf-49ba-9f0d-d4b522091219
0	sqlite3.dll	sqlite3DbFree	 db/sqlite3/src/sqlite3.c:15680
1	sqlite3.dll	releaseMemArray	db/sqlite3/src/sqlite3.c:47126
2	sqlite3.dll	sqlite3VdbeDelete	db/sqlite3/src/sqlite3.c:48323
3	sqlite3.dll	sqlite3_finalize	db/sqlite3/src/sqlite3.c:49100
4	xul.dll	mozStorageConnection::Initialize	storage/src/mozStorageConnection.cpp:178 


bp-db0a898f-d65c-428c-9761-1c7b62091219
0	sqlite3.dll	sqlite3DbFree	 db/sqlite3/src/sqlite3.c:15680
1	sqlite3.dll	sqlite3Pragma	db/sqlite3/src/sqlite3.c:74512
2	sqlite3.dll	sqlite3BtreeParseCellPtr	db/sqlite3/src/sqlite3.c:37559
3	sqlite3.dll	sqlite3VdbeExec	db/sqlite3/src/sqlite3.c:56394
4	xul.dll	mozStorageConnection::ExecuteSimpleSQL	storage/src/mozStorageConnection.cpp:372
5	xul.dll	mozStorageConnection::Initialize	storage/src/mozStorageConnection.cpp:205
6	xul.dll	nsJSIID::NewResolve	js/src/xpconnect/src/xpcjsid.cpp:524
Seeing pretty consistent stacks with this crash.
Crash Signature: [@ sqlite3DbFree]
(In reply to Shawn Wilsher :sdwilsh from comment #1)
> Seeing pretty consistent stacks with this crash.

for current versions of firefox, only a couple crashes a month now 
https://crash-stats.mozilla.com/query/query?product=Firefox&version=ALL%3AALL&date=&range_value=4&range_unit=weeks&query_search=signature&query_type=exact&build_id=&process_type=all&do_query=1&query=sqlite3DbFree

bp-81d1daf0-ace7-4a85-ab1c-414af2130401
Whiteboard: [startupcrash]
Crash volume for signature 'sqlite3DbFree':
 - nightly (version 50): 0 crash from 2016-06-06.
 - aurora  (version 49): 0 crash from 2016-06-07.
 - beta    (version 48): 56 crashes from 2016-06-06.
 - release (version 47): 7 crashes from 2016-05-31.
 - esr     (version 45): 0 crash from 2016-04-07.

Crash volume on the last weeks:
             Week N-1   Week N-2   Week N-3   Week N-4   Week N-5   Week N-6   Week N-7
 - nightly          0          0          0          0          0          0          0
 - aurora           0          0          0          0          0          0          0
 - beta             0          0          0         51          0          4          1
 - release          1          0          1          0          0          3          1
 - esr              0          0          0          0          0          0          0

Affected platform: Windows
Priority: -- → P5
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INACTIVE
almost No crashes in last 6 months for current Thunderbird versions (just 2-3)
Resolution: INACTIVE → WORKSFORME
You need to log in before you can comment on or make changes to this bug.