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
$ go tool trace /tmp/trace.out
2020/03/21 12:34:08 Parsing trace...
2020/03/21 12:34:09 Splitting trace...
2020/03/21 12:34:10 Opening browser. Trace viewer is listening on http://127.0.0.1:53686
Visit http://127.0.0.1:53686 in Chrome Version 80.0.3987.149 (Official Build) (64-bit)
Click on View trace, which takes me to http://127.0.0.1:53686/trace. The page is empty.
Open Chrome javascript console (cmd-opt-j on Mac).
Reload http://127.0.0.1:53686/trace and see the broken javascript:
Uncaught ReferenceError: tr is not defined
at onResult (trace:59)
at trace:43
Click through to see the JS that caused the error:
58 function onResult(result) {
59 model = new tr.Model(); ## tr is not defined here
60 var opts = new tr.importer.ImportOptions();
61 opts.shiftWorldToZero = false;
62 var i = new tr.importer.Import(model, opts);
63 var p = i.importTracesWithProgressDialog([result]);
64 p.then(onModelLoaded, onImportFail);
65 }
Give up and file a bug, because I'm lousy at JS.
What did you expect to see?
I expect to see a non-empty trace in my browser. This is my first time using go tool trace so I don't know what it's supposed to show me. Note that the /trace endpoint is also used when you click on a specific goroutine number in the /goroutines page, and is similarly broken.
What did you see instead?
An empty trace in my browser, and the above broken javascript in the console.
AFAICT the other links on the local http server seem to work fine; only /trace seems to be broken.
The text was updated successfully, but these errors were encountered:
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
go.1.14
is the latest release. It also reproduces ongo1.13.8
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
trace.out
file.go tool trace
http://127.0.0.1:53686
in ChromeVersion 80.0.3987.149 (Official Build) (64-bit)
View trace
, which takes me tohttp://127.0.0.1:53686/trace
. The page is empty.http://127.0.0.1:53686/trace
and see the broken javascript:What did you expect to see?
I expect to see a non-empty trace in my browser. This is my first time using
go tool trace
so I don't know what it's supposed to show me. Note that the/trace
endpoint is also used when you click on a specific goroutine number in the/goroutines
page, and is similarly broken.What did you see instead?
An empty trace in my browser, and the above broken javascript in the console.
AFAICT the other links on the local http server seem to work fine; only
/trace
seems to be broken.The text was updated successfully, but these errors were encountered: