search

ChrisNZL / Fauxbar

An alternative to Chrome's Omnibox.
https://chrome.google.com/webstore/detail/fauxbar/hibkhcnpkakjniplpfblaoikiggkopka
MIT License
89 stars 13 forks source link

SQL database error: "could not execute statement (778 disk I/O error)" #12

Closed fhoshino closed 7 years ago

fhoshino commented 7 years ago

Does not seems to affect usability.

chrome_2017-02-05_12-31-51

ChrisNZL commented 7 years ago

The lines mentioned are used with chrome.history.onVisited and chrome.tabs.onUpdated which are super common as you browse the web and use Chrome. If it's only happened a couple times, I assume the disk I/O error is an issue with Chrome, possibly a file-locking issue, something that Fauxbar has no control over.

Please try:

Does this resolve the issue?

fhoshino commented 7 years ago

Seems not, does this affects on massive page loads?

ChrisNZL commented 7 years ago

I've no idea. I've tried reproducing this issue by opening lots of pages and at once but no luck. An I/O error sounds like an issue with Chrome, perhaps the WebSQL database file that Chrome has stored for Fauxbar is getting locked for some reason.

If the issue persists after restarting your computer, I'd suggest uninstalling Fauxbar and reinstalling Fauxbar, just so Chrome can wipe the extension's files completely. If you want to backup your options first, check Fauxbar's Options > Management section for backup instructions.

fhoshino commented 7 years ago

Will close this first, and let me observe for a while.

fhoshino commented 7 years ago

Reopen as restarting machine and reinstall extension does not help. 2017-02-06_00-17-20

ChrisNZL commented 7 years ago

Investigating further, error 778 is SQLITE_IOERR_WRITE.

Searching around, a few pages regarding this with Chrome suggest this error is caused if a harddrive is almost full. Is your harddrive almost out of space?

These aren't strictly related to Chrome extensions but sound similar:

I found that Fauxbar's SQLite file (a file named as a number without an extension) is located within:

C:\Users\YOUR_USERNAME\AppData\Local\Google\Chrome\User Data\Default\databases\chrome-extension_hibkhcnpkakjniplpfblaoikiggkopka_0

For me, the file was about 15 MB, but then I reinstalled Fauxbar and it was about 6 MB. In my code I've written Fauxbar's database quota as 100 MB, though I've just tried setting the quota to 1 MB and it didn't make a difference (I guess Chrome overrides this and gives it an unlimited quota). Uninstalling Fauxbar removes this folder, so if the folder gets removed and is recreated upon reinstallation for you, I assume it's not a file locking issue.

Comments linked above suggest issues were arising if their drives were almost full, so maybe try clearing some space? Other than that, I'm out of ideas.

fhoshino commented 7 years ago

My db is 3MB in size and my disk has 90G free space out of 240G, which is nowhere near full.

ChrisNZL commented 7 years ago

Does Fauxbar's background console have any info? To view:

  1. Go to chrome://extensions
  2. Click the developer mode checkbox
  3. Under Fauxbar, click the background page link
fhoshino commented 7 years ago

Unchecked runtime.lastError while running tabs.captureVisibleTab: Failed to capture tab: unknown error

chrome_2017-02-06_11-55-52

fhoshino commented 7 years ago

Errors on line: 646, 681, 754, 1641 of js/background-new.js

ChrisNZL commented 7 years ago

Unchecked runtime.lastError while running tabs.captureVisibleTab: Failed to capture tab: unknown error

Unknown errors - dunno. Probably an issue with Chrome that's out of my control.

Errors on line: 646, 681, 754, 1641 of js/background-new.js

What are the accompanying error messages? Can you screenshot the log again?

fhoshino commented 7 years ago

chrome_2017-02-09_15-03-45

ChrisNZL commented 7 years ago

Closing this. I/O errors are out of Fauxbar's control, likely due to issues with Chrome, user's harddrive, or operating system issues.