search

ankit / stylebot

Change the appearance of the web instantly
https://stylebot.dev/
MIT License
1.4k stars 208 forks source link

[Bug] Unable to open Stylebot after Chrome crash #610

Closed KDCCreative closed 3 years ago

KDCCreative commented 3 years ago

The title sums it up fairly well. I haven't tried to reproduce this issue, nor do I want to try to as it involves crashing the program. I was viewing a large Google Doc with a few other tabs open, one of which was pinned and another was playing audio. The Docs tab seemed to take up too much of some resource and caused my entire Chrome app to crash. Upon reopening Chrome, Stylebot no longer worked. It had been working perfectly before the crash, and I've had a similar issue on a previous version of Stylebot, with the same symptoms but no Chrome crash to start out with. Stylebot is unable to be opened on any page, cannot be selected upon right-clicking an element on a page (see image attached), and I don't have the CSS knowledge to code something purely in the editor on the Stylebot options website, so I can't test whether it is completely unable to access pages' CSS. All of my previous CSS settings have been wiped. I never backed them up, which is seeming like a good idea now that this has happened twice. Another Chrome extension, Tampermonkey, also came up with a report noting irretrievable user settings and data. I no longer use this extension, but it may be of note in finding and addressing the issue here if there is one. image Removing and re-installing Stylebot from the Chrome extension webstore has not fixed this issue.

ankit commented 3 years ago

@KDCCreative It will be very helpful if you can check if the extension's popup, background page or the page you try to open stylebot on has any Javascript errors in the developer console. Without that information, it is hard for me to know what the issue is. Thanks!

KDCCreative commented 3 years ago

I've found two errors (after googling how to open the dev console, lol) that might be of note here. image The first error is seen on every page in Chrome. I don't know if it's Stylebot-related, another extension possibly breaking, or another Chrome issue. The second error appears on some pages, but not others. Notably, it does not appear on a freshly opened tab with Google still open, but all other tabs I've tried had it show up. It seems like it could be the issue? Thanks for responding! Oh, and as an edit here: Toggling readability will show the switch turning on and off, but the webpage doesn't change. It seems like there's some issue in finding and editing the page.

ankit commented 3 years ago

Thanks for the quick response (and googling how to open the dev console)! this is very helpful. Yes, it is likely the second error is the issue. A couple more things would be very helpful:

Screen Shot 2021-01-05 at 12 31 02 AM
KDCCreative commented 3 years ago

Sorry for the late reply, it was 2am when I last responded, but I've dug into those for ya. I'm running Chrome version 87.0.4280.88 (latest, apparently) on Windows 10. Here's what came up on the background page: image

ankit commented 3 years ago

@KDCCreative no worries, thanks! Sorry another quick help: can you run:

chrome.storage.local.get(items => console.log(items))

in the dev console on background page (just copy/paste and hit enter) and copy the output here? Thank you!

KDCCreative commented 3 years ago

image Or, if you need it as text: Unchecked runtime.lastError: IO error: .../LOCK: File currently in use. (ChromeMethodBFE: 15::LockFile::2)