openDatabase failing

Scott Fujan

unread,

Jun 14, 2011, 9:00:00 AM6/14/11

to Chromium-extensions

I am having a problem with a webDatabase that is failing intermittently (as far as I can tell). Reload the extension as it works as intended. The symptoms are that db.transaction never calls the callback function and subsequent calls to openDatabase return a SECURITY_ERR. Also, the database still shows up in the inspector, but the table is no longer listed.

> db.transaction(function(){console.log("test")})
undefined
> db = openDatabase('mydatabase', '1.0', 'test', 2000000);
Error: SECURITY_ERR: DOM Exception 18

I thought it might have something to do with the size of the database, so I added "unlimitedStorage", but nothing has changed. Has anyone else seen this behavior or have an idea of what is going on?

PhistucK

unread,

Jun 14, 2011, 10:29:52 AM6/14/11

to Scott Fujan, Chromium-extensions

Does it only happen with extensions (or apps)? does it also happen with web pages?

On what version of Chrome is this occurring for you?

Chrome 13 (dev) has a new quota manger (not sure it is implemented for Web Databases in Chrome 13, though), which may cause this issue (since you tried to posit that it may be related to size issues), but it is probably not the cause.

☆PhistucK

--
You received this message because you are subscribed to the Google Groups "Chromium-extensions" group.
To post to this group, send email to chromium-...@chromium.org.
To unsubscribe from this group, send email to chromium-extens...@chromium.org.
For more options, visit this group at http://groups.google.com/a/chromium.org/group/chromium-extensions/?hl=en.

Scott Fujan

unread,

Jun 14, 2011, 12:05:26 PM6/14/11

to PhistucK, Chromium-extensions

I was encountering the issue on 14.0.788.0 (daily), but I switched to 12.0.742.91 (stable) and continue seeing the same issue. I have only encountered this with 1 extension. I use the webDatabase quite often in this 1 extension. Maybe there is a frequency of access quota?

PhistucK

unread,

Jun 14, 2011, 1:24:57 PM6/14/11

to Scott Fujan, Chromium-extensions

I do not think so, but others probably know better.

You can search crbug.com for an existing issue and star it. If you cannot find one, file a new issue at new.crbug.com.

Please, do not add a "+1" or "Me too" or "Confirmed" (or similar) comment. It just wastes the time of Chrome engineers and sends unnecessary e-mails to all of the people who starred the issue.

Attach your extension (or a really reduced version of it that still exhibits this issue, preferably).

Also, if you can somehow mock your extension up with a simple web page that gets the same error, please, mention it and attach it to the case (because that would mean it is not an issue with the extension and web databases integration, but a general issue).

Thank you.

☆PhistucK

Mihai Parparita

unread,

Jun 14, 2011, 4:12:14 PM6/14/11

to phis...@gmail.com, sc...@fujan.name, chromium-...@chromium.org

This may be similar to http://crbug.com/85522, which is also about
openDatabase failing in Chrome 13. If you have a minimal extension
that exhibits this problem, please attach it to the bug.

Mihai

Scott Fujan

unread,

Jun 14, 2011, 5:51:56 PM6/14/11

to Mihai Parparita, phis...@gmail.com, chromium-...@chromium.org

I will look into creating a reduced test case, but its not going to be easy because I don't know when it starts failing yet. What I can say is that there is one query that that is called a lot which uses nested queries; nested queries seem like they _might_ be related to virtual tables.

Reply all

Reply to author

Forward