> I put a pointer to the mozilla bug report here:
I probably should have mentioned our bug report as well. It's bug 408518 [1].
> These stack traces don't make any sense to me either. The definition
> of sqlite3_enable_shared_cache() in SQLite cvs is:
That, and as far as I can tell it's ever called by any other sqlite code.
> int sqlite3_enable_shared_cache(int enable){
> sqlite3SharedCacheEnabled = enable;
> return SQLITE_OK;
> }
>
> sqlite3SharedCacheEnable is a file scoped int.
hmm, are there some threadsafty issues there with setting and reading
that value from (possibly) multiple threads? I don't think it's
related to this (I don't think anything in core code in mozilla
actually toggles those - but add-ons can do it) however.
> Stack overflow possibly? Will keep thinking this.
Someone mentioned in the mozilla bug that the new allocator we
switched to may have landed around the time we started seeing this.
I'll look into it further.
Cheers,
Shawn Wilsher
Mozilla Developer
[1] https://bugzilla.mozilla.org/show_bug.cgi?id=408518
_______________________________________________
sqlite-users mailing list
[email protected]
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
