-
Notifications
You must be signed in to change notification settings - Fork 339
Loading CPU profile in JIT doesn't work #8866
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
Comments
@jakemac53 and another one! |
@derekxu16 This looks related to the fact that you are running through SSH - note that web socket URL that it is trying to connect to Using VsCode and the proxy server its creates I was able to load a profile (even when running devtools on a remote machine through ssh). I had to do some manual munging of the connection URL to use the vscode proxy URL, prior to that I saw the same errors you see. I did however still see several errors in the JavaScript console, but was ultimately able to load the profile. |
It looks like when running via the AOT command you provided, it always uses port 8181. So that is why it works. |
I believe you could work around this by passing explicitly |
The remaining errors I do see are related to the dart tooling daemon connection which fails (but gracefully). It is the same core issue, it tries to connect to dtd using a local host/port which isn't being forwarded. I think it probably gets the connection URI from a file or something. I am not sure there is much we can do there. |
This issue was reported by @jensjoha, I just transferred it from the SDK repo to here. |
cc @jensjoha can you confirm things work if you provide an explicit port that you have forwarded? I do expect you will see the error connecting to the dart tooling daemon still though. |
Specifying a port doesn't change things.
You'd have to specify It's weird that it's trying to connect to a different port, the output is
so it's seemingly asking webtools to connect to port 8181. That being said, it does stop complaining about not being able to connect if chromoting in, but it still doesn't load and I still get null errors:
|
I did send out a fix for the null check exception fwiw, #8940. But, I doubt its really going to help your situation, as this indicates a not useful response anyways. But, it might get you a different or better error. |
Fixes one of the errors shown in #8866.
I still get null-errors in the console and the actual page is just standing there saying "Fetching CPU samples". |
@jensjoha can you provide a CPU profile which fails to load? |
I don't understand. The reproduction is in the first message? |
The following is a copy of the bug report that @jensjoha had initially filed in the SDK repo:
Say I run
and launch devtools. I go to the "CPU Profiler" tab, click "Load all CPU samples". Then it just sits there, "Fetching CPU samples" forever.
In the javascript console I can see this stuff:
I am running through a ssh tunnel with port 8181 open btw.
Worth noting though is that if I instead do
it works. It loads the profile and there are no errors in the console.
The text was updated successfully, but these errors were encountered: