Closed
Bug 497428
Opened 15 years ago
Closed 15 years ago
crash while recalculating frecency
Categories
(Toolkit :: Places, defect)
Tracking
()
VERIFIED
DUPLICATE
of bug 493538
People
(Reporter: dietrich, Unassigned)
References
()
Details
(Keywords: crash)
see URL
Reporter | ||
Comment 1•15 years ago
|
||
windows only, 29 crashes on b4 and newer in the last week: http://is.gd/XZpn
Comment 2•15 years ago
|
||
All since June 3rd, even. Maybe bug 494370 - Better query for mDBGetItemProperties or bug 494371 - Get itemType only once per itemAdded notification
Comment 3•15 years ago
|
||
a previous instance of a similar crash has been addressed in bug 493538. in such a case it was due to GetDBInvalidFrecencies, that was not taking in count column number differences between real tables and temp tables.
Comment 4•15 years ago
|
||
The line seems to be: nsresult rv = aStatement->BindInt32Parameter(0, aCount); So yeah this sounds familiar where aStatement (GetDBInvalidFrecencies()) is returning null because it fails to create the statement.
Comment 5•15 years ago
|
||
Actually looking at link in comment 1, i don't see any crash after 19 May build. so this is probably simply a dupe since that crash has been fixed from 20 May build.
Comment 6•15 years ago
|
||
FWIW, this happened on a branch-nightly build from 05/15 (built from changeset a6445e2e8691) so Marco's probably right.
Comment 7•15 years ago
|
||
Yeah, this has been fixed. Sorry for the bad report, folks!
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → INVALID
Updated•15 years ago
|
Resolution: INVALID → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•