Comment #11 on issue 23894 by [email protected]: crash in sqlite3_close http://code.google.com/p/chromium/issues/detail?id=23894
I was going to comment on the ones we get on the Mac side, but ... we don't really get that many. I do notice that we had a Mac crasher in malloc() on the history backend thread, which is the type of crash we used to get when someone was passing a non-threadsafe refcount to that thread, leading to a double-free. Suspect it's not really all that special WRT close. That just happens to be where you run through all your memory and call free(), so you're likely to thoroughly exercise the machinery. The problem node may have been latent for awhile. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings -- Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs
