Comment #14 on issue 30403 by [email protected]: Crash on CHECK in DoesTableExist http://code.google.com/p/chromium/issues/detail?id=30403
That result means someone else has the lock. There's not something to do to seize control, you need the other guy to commit or rollback to release the lock. On Linux it should be impossible to have the lock stay outstanding if there are no processes holding it (I don't mean impossible at the SQLite level, I mean impossible w/in the kernel), so most likely you have a zombie process or something. [Err ... is this guy on NFS?] -- 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
