You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello all,
I've recently updated the ClearScript version from 5.5.0 to 5.5.1.1 and now I'm not able to debug my javascript code by using Chrome Developer Tools anymore.
Every time I try to connect to an engine using the CDT, a WebSocket connection is established and then closed by chrome as soon as the first message is received.
From a brief analysis seems to be an issue connected to the new WebSocket implementation.
I can reproduce the issue with the following steps:
I create a minimal test console application:
using Microsoft.ClearScript.V8;using System;namespaceMinimal{classProgram{staticvoidMain(string[]args){using(varengine=new V8ScriptEngine(V8ScriptEngineFlags.EnableDebugging | V8ScriptEngineFlags.EnableRemoteDebugging,9876)){
Console.WriteLine(engine.Evaluate("'Press enter to send debug command';"));
Console.ReadKey();
engine.Evaluate("debugger;");}}}}
We've confirmed that manually entering the CDT front end URL into the Chrome address bar currently doesn't work. We're investigating.
In the meantime, you can configure chrome://inspect to monitor your host and port, and launch CDT from there. That works and is the recommended procedure for launching CDT with ClearScript 5.5.1 and later.
Hello all,
I've recently updated the ClearScript version from 5.5.0 to 5.5.1.1 and now I'm not able to debug my javascript code by using Chrome Developer Tools anymore.
Every time I try to connect to an engine using the CDT, a WebSocket connection is established and then closed by chrome as soon as the first message is received.
From a brief analysis seems to be an issue connected to the new WebSocket implementation.
I can reproduce the issue with the following steps:
http://127.0.0.1:9876/json/list
My solution, for now, is to downgrade ClearScript version.
Thanks
The text was updated successfully, but these errors were encountered: