-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GraalVM js debug devtools is not accessible in the lasted chrome 118.0.5993.89 #7636
Comments
Hi can you please provide:
|
GraalVm version: 23.0 |
To make the reproduction more concrete:
Result: The DevTools open but no source code is shown, and no debugging is possible. According to the protocol monitor, GraalVM sends the browser 3 events, but no further communication takes place. The Java code blocks until the DevTools page is manually closed again. |
I'm experiencing a similar issue since a few days. Before this it was rock solid for months. I changed nothing in my implementation, same JDK, only regular updates to OS. For me everything looks normal, I can create breakpoints etc, but my program won't pause on the breakpoints anymore. GraalVm version: 22.0.0 EDIT: |
Thanks @martinhiller issue was found on windows, and we are looking into it |
@zebhlindqvist , I found the original issue with Chromium 118.0.5993.70 ubuntu arm64, can you please provide me with Chromium 116.x that you have used ? |
I didn't find a way to download an older version of Chrome/Chromium. I just happed to find that version installed on a computer that wasn't updated. One easy way I found was to use Electron. Electron 26.4.1 has Chromium 116.0.5845.228 built in. |
Another way are the Chrome for Testing downloads: Chrome 117 (still works): Chrome 117.0.5938.149 for Win64 Chrome 118 (not anymore): Chrome 118.0.5993.70 for Win64 |
Issue was identified on the latest builds of chrome/chromium, and we are looking into it |
I found a possible reason that GraalVM did not send the source code to chrome devtools. |
Issue is actual for google-chrome-stable-119.0.6045.105-1.x86_64 as well (and perhaps for 120), but works correctly for google-chrome-stable-117.0.5938.132-1.x86_64 (Linux) and releases before. No info that Chrome devTools changed something in API for source code, looks like there were only cosmetic changes: Streamlined workspace in the Sources panel Did anyone localize the issue or found a workaround? The last post from @chenjie100 looks encouraging... |
This was fixed by db40984 |
@entlicher That's great, where can I download the update patch or completed graalvm please? Thank you. |
Adds chrome-inspector tool and Debug Adapter protocol tool for debugging Enso. # Important Notes The chrome devtools seems to be broken (tracked in oracle/graal#7636). Even `graalpy --inspect ...` fails (Chrome devtools freezes after connecting to the server). This PR adds Debug adapter protocol tool for debugging as a workaround for chrome inspector. There is docs in [dap.md](https://github.com/enso-org/enso/pull/8344/files#diff-421574b50574cfe546e86d4b3d32d79b8b2087f2fe204f68e5cf2693af43bbe1)
After struggling to install a previous version of Google Chrome ... Edit your host file with:
This will block Brave browser update domains (The simplest way I found to disable auto update of Brave...) Then you can download in the assets of: https://github.com/brave/brave-browser/releases/tag/v1.58.137 A version of Brave browser that match your arch. |
When debug js in Chrome open: devtools://devtools/bundled/js_app.html?ws=127.0.0.1:61775/1E828627BBFA81AF25EDE97FD2F
No source code appears and cannot be debugged。
The text was updated successfully, but these errors were encountered: