GraalVM js debug devtools is not accessible in the lasted chrome 118.0.5993.89

[chenjie100]

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。

[hamzaGhaissi]

Hi can you please provide:

• GraalVm version
• JDK version
• OS & architecture
• A minimal reproducer and steps

[chenjie100]

GraalVm version： 23.0
JDK version: 17.0.8+9-LTS-jvmci-23.0-b14
OS & architecture：Windows 10 amd64
A minimal reproducer and steps：
1, Write any js and start to debug in chrome devtools.
2, In Chrome open: devtools://devtools/bundled/js_app.html?ws=127.0.0.1:50144/someUrl
3, No source code to display and cannot be debugged。

[martinhiller]

To make the reproduction more concrete:

1. Launch the following main class:

import org.graalvm.polyglot.Context;

public class DebugTest {

	public static void main(String[] args) throws Exception {
		try (Context context = Context.newBuilder("js")
				.option("inspect", "4242")
				.option("inspect.Suspend", "false")
				.option("inspect.WaitAttached", "true")
				.option("inspect.Path", "debug")
				.build()) {
			context.eval("js", """
					(function () {
						debugger;
						return 41 + 1;
					})()
					""");
		}
	}
}

2. Open the DevTools URL (printed by GraalVM to the stderr) in any recent Chromium browser: devtools://devtools/bundled/js_app.html?ws=127.0.0.1:4242/debug

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.

[zebhlindqvist]

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
JDK version: 11.0.20-tem
OS & architecture：Ubuntu 23.04 amd64
Web browser: Chromium 118.0.5993.88

EDIT:
Tested with Chromium 116.0.5845.96 and everything works as expected.

[hamzaGhaissi]

Thanks @martinhiller issue was found on windows, and we are looking into it

[hamzaGhaissi]

@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 ?

[zebhlindqvist]

@hamzaGhaissi

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.
See https://github.com/zebhlindqvist/electron-devtools

Electron 26.4.1 has Chromium 116.0.5845.228 built in.

[martinhiller]

Another way are the Chrome for Testing downloads:

Chrome 117 (still works):

Chrome 117.0.5938.149 for Win64
Chrome 117.0.5938.149 for Linux64

Chrome 118 (not anymore):

Chrome 118.0.5993.70 for Win64
Chrome 118.0.5993.70 for Linux64

[hamzaGhaissi]

Issue was identified on the latest builds of chrome/chromium, and we are looking into it

[chenjie100]

I found a possible reason that GraalVM did not send the source code to chrome devtools.

[oghmjos]

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...

[entlicher]

This was fixed by db40984
We will backport the fix to the releases of GraalVM.

[chenjie100]

@entlicher That's great, where can I download the update patch or completed graalvm please? Thank you.

[jkevan]

After struggling to install a previous version of Google Chrome ...
To workaround the issue and be able to use the debugger here is what I did:

Edit your host file with:

0.0.0.0 brave-update.brave.com
0.0.0.0 updates.bravesoftware.com

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.
This version of Brave is based on Chromium 117 and the debugger is working again.