Frame not in module when hitting a breakpoint in Blazor WASM #86754
Labels
Milestone
Comments
dotnet-issue-labeler
bot
added
the
needs-area-label
|
@joseangelmt I need more help to reproduce/understand what may be happening. Thanks |
lewing
added
untriaged
|
Tagging subscribers to this area: @thaystg Issue DetailsIs there an existing issue for this?
Describe the bugAfter upgrading to Visual Studio 17.6.0 and 17.6.1 the debugger shows me a Source Not Available page with the body: The curious thing is that in the .razor file the breakpoints selected before executing the application are kept without warnings, but if I add one while the application is running, it appears with the warning: "The breakpoint will not currently be hit. Unbound breakpoint". When I open the debug window "Modules" I can check that the module "Application.server.dll" has the status "Symbols loaded" and that the "symbol file" is correct. I have tried deleting the .obj and .bin directories, I have tried with .net 6 and .net 7 (with their corresponding updated NuGet packages), I have tried with different browsers, and in all of them, the error is the same. When debugging no error appears in the Output window. The curious thing is that if I create a new application with the wizard, there is no problem and Visual Studio stops at the line in the .razor file. I have analyzed both projects and I do not see what could be the cause of my main project causing this problem. Expected Behavior
Steps To ReproduceNo response Exceptions (if any)No response .NET Version7.0.302 Anything else?
|
|
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsIs there an existing issue for this?
Describe the bugAfter upgrading to Visual Studio 17.6.0 and 17.6.1 the debugger shows me a Source Not Available page with the body: The curious thing is that in the .razor file the breakpoints selected before executing the application are kept without warnings, but if I add one while the application is running, it appears with the warning: "The breakpoint will not currently be hit. Unbound breakpoint". When I open the debug window "Modules" I can check that the module "Application.server.dll" has the status "Symbols loaded" and that the "symbol file" is correct. I have tried deleting the .obj and .bin directories, I have tried with .net 6 and .net 7 (with their corresponding updated NuGet packages), I have tried with different browsers, and in all of them, the error is the same. When debugging no error appears in the Output window. The curious thing is that if I create a new application with the wizard, there is no problem and Visual Studio stops at the line in the .razor file. I have analyzed both projects and I do not see what could be the cause of my main project causing this problem. Expected Behavior
Steps To ReproduceNo response Exceptions (if any)No response .NET Version7.0.302 Anything else?
|
|
|
Maybe a screenshot of the Call Stack can help. I think in the side of javascript the application is hitting the breakpoint correctly as you can see in the next screenshot. If I double click the "Subestaciones.Client.Pages.EditarPosicion.OnitializedAsync" is when I get the "file not in module" page.
|
|
I should try to open this PATH: C:/Users/josea/source/repos/digi21/Subestaciones/Subestaciones/Client/Pages/EditarPosicion.razor Is this the correct source path? |
|
Yes, it is the correct path. |
|
@joj can you help here? |
|
The behavior happens when the top of the stack is on a file that doesn't exist. From what I'm seeing in the stack, it looks like the top is being detected as a dotnet generated file (the second line in the screenshot). It's weird that the source file is not being detected (the one in EditarPosicion), but I'm not seeing a file name or position on that stack frame, which would explain it. |
|
Looking at visualstudio-js-debugger.txt And we are also sending the correct Debugger.paused:
|
|
Oh, I can see we sending three times the Debugger.scriptParsed, for the same file: |
|
@joj Maybe this is causing something weird on the extension side? |
|
Not sure. Maybe @connor4312 will know? |
|
Hello, I have the same problem, rollback visualStudio pro to the 17.5.1 make my breakpoints work again |
|
Does Blazor send the |
|
@connor4312 yes. If you look at the visualstudio-js-debugger.txt that is attached here you will see this: |
|
Ah, thanks. Something I notice in that log is that it seems like an execution context was destroyed at the wrong time:
|
connor4312
added a commit
to microsoft/vscode-js-debug
that referenced
this issue
Jun 8, 2023
Ref dotnet/runtime#86754 A true fix is being applied in .net, but this will take time to trickle down.
|
With Visual Studio 17.6.3 it's working again. |
I still get a the same error error. |
|
I have 17.6.3 installed, and still receiving this message. This is stopping me working, so will have to roll back my Vs to a previous working version. |
How do I downgrade? I tried using Visual studio Installer nut it only allows me to downgrade to 17.6.0. |
|
You can only roll back to the last version from what I can see. I had to uninstall and reinstall. |
|
Same issue here / work halted, very frustrating |
Ok, thank you. Do you know where I can get an older working version? |
|
same issue on our side also, we are totally blocked with development due to malfunction of debugger. |
So you need to uninstall the old version and the download the boostrapper version you want here. |
|
We have a fix for this also coming on the debugger side which should be in the next release, but in the mean time, if you want to get things working right away, you can replace the files in C:\Program Files{Your VS install dir}\Common7\IDE\CommonExtensions\Microsoft\JSDiagnostics\Debugger\DebugAdapter with the files in dist.zip. That should get you the fix right away (use at your own risk, since this is not the official way to upgrade the debugger, though it should work). |
|
@EricCornelson Just wanted to confirm this fixed my immediate issue, thanks. |
|
@EricCornelson Thank you, will try it, could you please tell us ETA of next release? |
1 task
ghost
removed
the
in-pr
|
I currently have the same issue. |
|
@EricCornelson I had the same problem with VS2022 17.6.4 and can confirm that your dist.zip fixed it. |
|
@candritzky Just updated to 17.6.4 and used dist.zip as described by EricCornelson and it appears to fix the issue. |
|
I also used dist.zip and while it did fix the debugging breakpoints within C# code files, it caused VS to stop responding for my breakpoint on C# code within a razor file. VS had a popup indicating it was looking for the razor breakpoint, or something to that affect (I already killed that instance of VS to stop it). |
Should be around mid-July |
|
dist.zip seems to work for me too on VS 17.6.4 |
|
Issue still on VS 17.6.5, fixed with dist.zip |
|
Also had same issue in VS 17.6.5 and was solved with the dist.zip |
|
Still an issue VS 17.6.5, dist.zip solved it |
|
I still have the issue in VS 17.6.5, and "dist.zip" did not solve it |
Thanks a lot. this solution helped. VS 17.6.5 |
|
same here on VS 17.6.5 ... dist.zip fixed the issue |
|
The strangest thing is that the problem is only in one old Blazor project. It used to be ok everywhere, but at some point one project fell into such a problem. The project file is the most common and even trivial. The solution file is also unremarkable. Rolling back to a previous version of VS doesn't help. All Blazor projects except one are fine. It's been a problem for quite some time now. Eric is a real doctor! My pain is gone - thank you Eric! |
ghost
locked as resolved and limited conversation to collaborators
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
and others
Is there an existing issue for this?
Describe the bug
After upgrading to Visual Studio 17.6.0 and 17.6.1 the debugger shows me a Source Not Available page with the body:
The curious thing is that in the .razor file the breakpoints selected before executing the application are kept without warnings, but if I add one while the application is running, it appears with the warning: "The breakpoint will not currently be hit. Unbound breakpoint".
When I open the debug window "Modules" I can check that the module "Application.server.dll" has the status "Symbols loaded" and that the "symbol file" is correct.
I have tried deleting the .obj and .bin directories, I have tried with .net 6 and .net 7 (with their corresponding updated NuGet packages), I have tried with different browsers, and in all of them, the error is the same.
When debugging no error appears in the Output window.
The curious thing is that if I create a new application with the wizard, there is no problem and Visual Studio stops at the line in the .razor file. I have analyzed both projects and I do not see what could be the cause of my main project causing this problem.
Expected Behavior
Steps To Reproduce
No response
Exceptions (if any)
No response
.NET Version
7.0.302
Anything else?
The text was updated successfully, but these errors were encountered: