-
Notifications
You must be signed in to change notification settings - Fork 380
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
Unable to profile in WSL1 #8822
Comments
Hi @LoganDark, |
That's why I opened this issue |
IIRC WSL1 doesn't support kernel performance counters, so profiling on it is impossible |
Are kernel performance counters required to profile code? I thought you just took a bunch of samples of the stack/whatever and then built a flame graph out of that. Isn't that what |
@LoganDark |
Doesn't seem like a definitive answer to me, just corporate garbage. |
Environment
Problem description
IntelliJ-Rust seems to only support using Perf on WSL2 for profiling, which runs in a virtual machine (i.e. lazy, bad performance, bad integration). WSL 1 runs much closer to the bare metal and is tied much more closely to the OS, but IntelliJ-Rust doesn't seem to support it yet.
It seems like this is a known limitation because IntelliJ-Rust contains this error message:
It would help me get more accurate profiles if I were able to profile in WSL 1 without the overhead of Hyper-V. Windows builds above 18342 support dtrace, maybe that supports WSL processes?
Steps to reproduce
Try to profile in WSL1.
The text was updated successfully, but these errors were encountered: