I am debugging background script in chrome extension mv3
I usually use Chrome devtools and it always worked correctly
but as of recently, breakpoints are fired without showing debugger
You can see in the images below that the breakpoint is fired, while displaying variables data but without any debugger commands
Has anyone encountered this issue before?
For anyone who encounters the same issue, I just reset Chrome and it worked
https://support.google.com/chrome/answer/3296214?hl=en
Related
My breakpoints set in WebStorm do not work until I hit the 'Rerun' button to restart the debugger. It's a fresh install of the latest WebStorm and Chrome. I have the exact same setup running on my old machine and breakpoints change immediately takes effect without the need to rerun the debugger.
The issue may be related to the communications between WebStorm debugger and the browser. I tried few tricks but could not resolve the problem. Debugging directly in the browser works perfectly fine. I searched the web well and could not find any working solution.
What might cause the problem?
EDIT:
I found some setting that somewhat helps: open the dev-tools in the browser window of the debugger > Network tab > check 'Disable cache'. Now breakpoints can be removed immediately, and only a page refresh is needed in order to make new breakpoints take effect. However, still quite annoying. Any ideas?
For a long time, I have not been able to use tooltips in the Sources tab of the chrome debugger anymore. Today I thought that I found a fix (which I posted below) but now tooltips have stopped working again. So, maybe someone knows how to fix this?
In Settings/General of the debugger I disabled "Show detailed inspect tooltip". Then I reloaded Chrome and enabled "Show detailed inspect tooltip". Somehow, this caused tooltips to work again.
Unfortunately, not long after, tooltips stopped working again.
I once came across an SO answer that gave a Chrome URL to navigate to, that had a button to "enable" JS console logging. After enabling the logging, that tab would show the console logs of other Chrome tabs.
I know this answer seems like a duplicate, but I'm having a lot of trouble finding how to do that again. It was super convenient since it gave the console logs on any Chrome browser without needing a USB connected.
Any ideas? I know I came across it in an SO question about iOS debugging.
Found it! So, it's actually a Chrome on iOS only feature.
URL: chrome://inspect
That URL won't show anything on Chrome for Android, which tripped me up. But, on iOS it shows a "Start Logging" button.
Answer from: https://stackoverflow.com/a/55433616/2096769
I am running Node.js on localhost:3001 and unintentionally wrote some code with an infinite while loop. This locked up Chrome to the point where the only resolution was to kill the browser. Since then, I found the problem in my code using Firefox, and fixed the code, but even after restarting Chrome, it will not load my page. I even changed the port that the server runs on, and the cache is disabled with developer tools open - Chrome simply refuses to load the page. I see a single request to the server for the page, but in Chrome it just registers as Pending.
Has Chrome maybe flagged this page as suspect, somehow? How do I get it to play again? I would at least expect Chrome to offer some opportunity to kill a tight loop - like Firefox does - but I've yet to see it. Is there some setting I can tweak? I'm on version 74.0.3729.169 (Official Build) (64-bit), although now that I opened the About page, I see that it is updating Chrome, so maybe that will fix it.
UPDATE: It didn't fix it, but it works in Incognito mode. ???!!!
UPDATE: Disabling all of my extensions also didn't fix it!
I found a setting in Chrome: "Continue to run background apps when Chrome is closed"
I turned that off, and now it works again.
When Chrome stops WebGL and gives you the following error (in a yellow banner on top of the screen): "Rats! WebGL hit a snag...", and reloading does not work (WebGL is still not re-enabled), is it possible to re-enable WebGL without restarting Chrome?
Context:
Chrome disables WebGL probably because it requires too many resources: I ask it to display 400,000 billboards on Cesium, for those who know what this is.
I know how I could reduce the resources my app asks for, but actually I am exploring its limits for testing purposes. So I am going to make Chrome disable WebGL a lot of times, and I do not want to restart it everytime it disables WebGL.
My configuration:
Chrome 35.0.1916.114 m
Windows 7 Pro 64 bit.
Solutions explored:
I already tried to open a new Chrome window, it does not work. For the moment all I can do is close all Chrome windows and restart it.
I already tried to put --ignore-gpu-blacklist in the Chrome shortcut (even if I understood this is for Windows XP, right?).
Hope I was clear enough.
Thank you for your help.
I was having the same problem and I just found a solution. It sounds like this didn't work back when this question was posted but, it works now!
Refreshing the page doesn't work. If you clicked a link from a different tab to open the tab the crashed, clicking that link again doesn't work. You have to open a new tab and paste in the URL of the page that you want to reload.
I'm guessing this is due to chrome threading... by opening a brand new tab, you create a new thread instead of using the existing one.
In your application you should properly handle webglcontextlost and webglcontextrestored events. In particular, you should prevent default event action in webglcontextlost handler thus telling the browser that you can restore proper functioning of your app when webglcontextrestored will be fired.