Closed Bug 439459 Opened 17 years ago Closed 17 years ago

crash when i try to write a URL address sqlite3VdbeMemFinalize: Assertion `0==(pMem->flags&0x0040) && !pMem->xDel' failed

Categories

(Core :: SQLite and Embedded Database Bindings, defect)

1.9.0 Branch
x86
Linux
defect
Not set
critical

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: mrwaltercool, Unassigned)

Details

User-Agent: Opera/9.50 (X11; Linux i686; U; MEGAUPLOAD 1.0; en) Build Identifier: Firefox 3.0 RC3 I have installed sqlite 3.5.9 in Gentoo, and that's the problem: firefox: ./src/vdbemem.c:255: sqlite3VdbeMemFinalize: Assertion `0==(pMem->flags&0x0040) && !pMem->xDel' failed. Aborted Reproducible: Always Steps to Reproduce: 1. Write ww 2. Crash Actual Results: Crash Expected Results: Can write www.web.something
Do you get the same problem with an original Mozilla.org binary build ? Can you pelkase attach a full stack trace ? Do you use the Mozilla.org sqlite or a system one ?
Component: Location Bar and Autocomplete → Places
QA Contact: location.bar → places
From Mozilla.org source, i get the problem... Now im using the binary build... Tomorrow i will try the 3.0 official :)
You build from the source and got the problem, a binary works, correct ? That means that you use different build options and i think that you configured your build to use the system librarys and not with the included sqlite (in this case) and your system sqlite seems to be either old or broken.
Component: Places → Storage
Product: Firefox → Toolkit
QA Contact: places → storage
Summary: crash when i try to write a URL address → crash when i try to write a URL address sqlite3VdbeMemFinalize: Assertion `0==(pMem->flags&0x0040) && !pMem->xDel' failed
Version: unspecified → 1.9.0 Branch
Uhmmm... i dont think so, because i have compiled mozilla firefox 3.0 final reciently using same methods and works nice. So, i must declare that like fixed, because my problem was with a RC and now seems without problems. Good job
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Now patch attached to the bug -> WORKSFORME
Resolution: FIXED → WORKSFORME
Product: Toolkit → Core
You need to log in before you can comment on or make changes to this bug.