Skip to content
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

Blazor WebAssembly debugger doesn't load values properly #49912

Closed
vsfeedback opened this issue Mar 19, 2021 · 5 comments · Fixed by #56872
Closed

Blazor WebAssembly debugger doesn't load values properly #49912

vsfeedback opened this issue Mar 19, 2021 · 5 comments · Fixed by #56872
Assignees
Labels
arch-wasm WebAssembly architecture area-Debugger-mono
Milestone

Comments

@vsfeedback
Copy link

This issue has been moved from a ticket on Developer Community.


[severity:It's more difficult to complete my work]
While debugging Blazor Webassemply apps the debugger works really poorly stopping on breakpoints and also showing values. This makes debugging really painful and time consuming.

1 - In the image below, you can see how the breakpoint shows that it's disabled (like it can't be hit). After several attempts, it stopped, as you can see in the picture (even though it shows the breakpoint with white circle, meaning that it's not enabled).
Sometimes, it requires to restart the whole machine for the debugger to start working again.

2 - When adding a watch, it it's an enumeration, it's basically impossible to access the values, no matter what. Also you can't do a collection. ToList() to access the values. It says Unable to evaluate. The values are there as you can see that I got the values in 2 variables.

! [image.png] (https://aka.ms/dc/image?name=Bb979a73d5616424d988874b986df26fc637516426520135007_20210318-163730-image.png&tid=b979a73d5616424d988874b986df26fc637516426520135007)


Original Comments

Feedback Bot on 3/18/2021, 00:18 AM:

We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.


Original Solutions

(no solutions)

@mkArtakMSFT mkArtakMSFT transferred this issue from dotnet/aspnetcore Mar 19, 2021
@dotnet-issue-labeler dotnet-issue-labeler bot added area-Diagnostics-coreclr untriaged New issue has not been triaged by the area owner labels Mar 19, 2021
@ghost
Copy link

ghost commented Mar 19, 2021

Tagging subscribers to this area: @tommcdon
See info in area-owners.md if you want to be subscribed.

Issue Details

This issue has been moved from a ticket on Developer Community.


[severity:It's more difficult to complete my work]
While debugging Blazor Webassemply apps the debugger works really poorly stopping on breakpoints and also showing values. This makes debugging really painful and time consuming.

1 - In the image below, you can see how the breakpoint shows that it's disabled (like it can't be hit). After several attempts, it stopped, as you can see in the picture (even though it shows the breakpoint with white circle, meaning that it's not enabled).
Sometimes, it requires to restart the whole machine for the debugger to start working again.

2 - When adding a watch, it it's an enumeration, it's basically impossible to access the values, no matter what. Also you can't do a collection. ToList() to access the values. It says Unable to evaluate. The values are there as you can see that I got the values in 2 variables.

! [image.png] (https://aka.ms/dc/image?name=Bb979a73d5616424d988874b986df26fc637516426520135007_20210318-163730-image.png&tid=b979a73d5616424d988874b986df26fc637516426520135007)


Original Comments

Feedback Bot on 3/18/2021, 00:18 AM:

We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.


Original Solutions

(no solutions)

Author: vsfeedback
Assignees: -
Labels:

area-Diagnostics-coreclr, untriaged

Milestone: -

@mkArtakMSFT
Copy link
Member

@lewing FYI

@mkArtakMSFT mkArtakMSFT added the arch-wasm WebAssembly architecture label Mar 19, 2021
@ghost
Copy link

ghost commented Mar 19, 2021

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

This issue has been moved from a ticket on Developer Community.


[severity:It's more difficult to complete my work]
While debugging Blazor Webassemply apps the debugger works really poorly stopping on breakpoints and also showing values. This makes debugging really painful and time consuming.

1 - In the image below, you can see how the breakpoint shows that it's disabled (like it can't be hit). After several attempts, it stopped, as you can see in the picture (even though it shows the breakpoint with white circle, meaning that it's not enabled).
Sometimes, it requires to restart the whole machine for the debugger to start working again.

2 - When adding a watch, it it's an enumeration, it's basically impossible to access the values, no matter what. Also you can't do a collection. ToList() to access the values. It says Unable to evaluate. The values are there as you can see that I got the values in 2 variables.

! [image.png] (https://aka.ms/dc/image?name=Bb979a73d5616424d988874b986df26fc637516426520135007_20210318-163730-image.png&tid=b979a73d5616424d988874b986df26fc637516426520135007)


Original Comments

Feedback Bot on 3/18/2021, 00:18 AM:

We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.


Original Solutions

(no solutions)

Author: vsfeedback
Assignees: -
Labels:

arch-wasm, area-Diagnostics-coreclr, untriaged

Milestone: -

@ghost
Copy link

ghost commented Mar 19, 2021

Tagging subscribers to this area: @thaystg
See info in area-owners.md if you want to be subscribed.

Issue Details

This issue has been moved from a ticket on Developer Community.


[severity:It's more difficult to complete my work]
While debugging Blazor Webassemply apps the debugger works really poorly stopping on breakpoints and also showing values. This makes debugging really painful and time consuming.

1 - In the image below, you can see how the breakpoint shows that it's disabled (like it can't be hit). After several attempts, it stopped, as you can see in the picture (even though it shows the breakpoint with white circle, meaning that it's not enabled).
Sometimes, it requires to restart the whole machine for the debugger to start working again.

2 - When adding a watch, it it's an enumeration, it's basically impossible to access the values, no matter what. Also you can't do a collection. ToList() to access the values. It says Unable to evaluate. The values are there as you can see that I got the values in 2 variables.

! [image.png] (https://aka.ms/dc/image?name=Bb979a73d5616424d988874b986df26fc637516426520135007_20210318-163730-image.png&tid=b979a73d5616424d988874b986df26fc637516426520135007)


Original Comments

Feedback Bot on 3/18/2021, 00:18 AM:

We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.


Original Solutions

(no solutions)

Author: vsfeedback
Assignees: -
Labels:

arch-wasm, area-Debugger-mono, area-Diagnostics-coreclr, untriaged

Milestone: -

@lewing lewing removed the untriaged New issue has not been triaged by the area owner label May 5, 2021
@lewing lewing added this to the 6.0.0 milestone May 5, 2021
@radical
Copy link
Member

radical commented Jul 22, 2021

@thaystg does this work now, after your debugger changes?

@ghost ghost added the in-pr There is an active PR which will close this issue when it is merged label Aug 4, 2021
@ghost ghost removed the in-pr There is an active PR which will close this issue when it is merged label Aug 16, 2021
@ghost ghost locked as resolved and limited conversation to collaborators Sep 15, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
arch-wasm WebAssembly architecture area-Debugger-mono
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants