I am using Chrome Version 86.0.4240.198 (Official Build) (64-bit) on Windows 10.
During debug I have unchecked Pause on caught exceptions
But most probably this exception is uncaught, therefore the debugger keep stopping there. It is very annoying.
Is there a way to disable debugger stop on all kinds of exceptions?
Oh I found my mistake:
I have mistakenly activated this button:
Related
I have a problem with chromium when I run my tests through the puppeteer.
What happens is that my tests require the microphone to be enabled the moment I log in to the application, even after adding:
'--use-fake-ui-for-media-stream', '--no-sandbox', '--disable-setuid-sandbox'] : ['--use-fake-ui-for-media-stream'
Before working normally, after changing the machine it stopped working and I don't know if it is related to the version of the chromium that is started:
This is the version of chromium when testing starts:
Version 77.0.3844.0
And my version of the puppeteer is:
```"puppeteer": "^1.19.0"````
Has anyone ever experienced this? If so, how do I update the chromium?
Thanks,
Have not been able to use Chrome (Version 42.0.2311.90 (64-bit)) as a neo4j browser client after upgrading to the latest XCode / Command Tools in MacOS Yosemite 10.10.3 . Safari is working fine though. Is there an easy way to pinpoint to the actual problem? I'm using Neo4j 2.2.1
The following is a screenshot from the JavaScript console showing the errors:
mostly load resource errors and an uncaught error failing to instatiate module neo4jApp .
It works fine under Safari. It also works in a Chrome Incognito Window. Partially resetting settings is a trial and error exercise. While resetting all chrome settings finally solved the initial problem, I wonder if there is a better way and not having to lose all other user settings in Chrome.
I encountered the same exact issue today with Chromium 43.0.2357.81 (64-bit) and Neo4j 2.2.1. Clearing the cache and refreshing http://localhost:7474/browser/ wasn't working for me (javascript errors). What did work for me, was going to http://localhost:7474/webadmin/ which asked me to re-authenticate. After logging in, the Neo4j browser site loaded.
Using info from chrome://gpu and chrome://version
Both on Chrome version: 35.0.1916.153 (Official Build 274914) m
Both using an Nvidia 670 GTX
My driver: 9.18.13.3523
His driver: 9.18.13.4043
My webGL works perfectly, and my driver is slightly behind his. His webGL doesn't work even though in the settings it says all hardware accelerated, webGL enabled etc.
When he goes on page with webGL things they don't work - he can't see them just like you wouldn't see them with old browsers.
Why is this happening? How to diagnose/fix?
Most likely Google has blacklisted the graphics driver because of the bugs.
You need to find out how start Chrome so that it ignores GPU blacklist. On some system it is this command line:
google-chrome --enable-webgl --ignore-gpu-blacklist
... and if it still doesn't work, the relevant console output etc. is needed.
More about blacklist:
http://www.khronos.org/webgl/wiki/BlacklistsAndWhitelists
As I stated in the title, how does one close (temporarily disables) debugging session connection Netbeans 7.4 with Chrome browser. The browser has flag #silent-debugger-extension-api turned on and Netbeans connector extension installed. Sometimes I have to turn off debugging because Netbeans CSS window does not show browser native styles, which is confusing. Thank you from the mountain! ;)
Simply open Chrome Developer Tools in given page. It terminates session between NetBeans and Chrome because only 1 degbugger can debug page - either Chrome Dev Tools or NetBeans. Once you close Chrome Developer Tools, re-run your project/file from NetBeans to get debugging with NetBeans back.
I've just upgraded to publish my SWF files as Flash 11. I want to attach FlashDevelop to Firefox (or IE). I'm able to first attach it, however player crashes after my first call to PHP file(not sure if it is related) and the debugger is stopped. If I just run the program without debugging it doesn't crash.
How can I figure out what is causing the problem?
Here is my set up:
FlashDevelop 4.0.1 RTM on Windows 7 (32bit)
Installed - Windows Flash Player 11.2 Plugin content
debugger (for Netscape-compatible browsers) (EXE, 3.89MB) from http://www.adobe.com/support/flashplayer/downloads.html
In FlashDevelop, I point Program->Settings->FlashViewer to flashplayer_11_plugin_debug_32bit.exe (I'm not exactly sure if this correct).
The way I attach is by going to Debug->Start Remote Session. Then launch an HTML page that loads my SWF.
update: Instead of upgrading to 11.2 version I upgraded to 11.1 . Now I'm getting some feedback in the output window. [Fault] exception, information=TypeError: Error #1009: Cannot access a property or method of a null object reference. However FlashDevelop doesn't break on that exception and I don't see a file name or line number which would help me to figure out wher exectly the error is happening.
update: I finally rolled back to my original version of 10.1.102.64 and now FlashDeveloper isn't crashing while debugging.
When you debug a flash application, you freeze the thread and your browser will think the application has locked up or died. It will then try to save your browsing session by force closing the plugin causing the problem (in this case, Flash).
To stop Firefox from doing this, type in "about:config" (minus quotes) in the address bar and hit enter, then click "I'll be careful" if a warning comes up.
Look for "dom.ipc.plugins.timeoutSecs" by typing it in the config search bar and set its value to -1. This will stop the browser from shutting down laggy plugins.
Disable the flash debugger plugin in your browser. Are you accessing the same SWF from the browser that you are debugging?