dotnet / runtime

.NET is a cross-platform runtime for cloud, mobile, desktop, and IoT apps.
https://docs.microsoft.com/dotnet/core/
MIT License
14.91k stars 4.63k forks source link

Blazor WebAssembly debugger jumps into JS code mono CLR while debugging C# only code #55214

Closed vsfeedback closed 2 years ago

vsfeedback commented 3 years ago

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


Debugging Blazor apps, when it stops in a breakpoint, pressing F10 or even F5 sometimes, it jumps from C# into the JS code of the mono/CLR, which makes no sense. I would expect to only stop in my C# code and not in minimise JS from the framework, which is useless.

! [image.png] (https://aka.ms/dc/image?name=Bdae72a2c859b416abae54aeb5aa71c7f637601756372352277_20210625-095358-image.png&tid=dae72a2c859b416abae54aeb5aa71c7f637601756372352277)

! [image.png] (https://aka.ms/dc/image?name=B08eea34afe7f462691618cc5df896729637601755533096995_20210625-095234-image.png&tid=08eea34afe7f462691618cc5df896729637601755533096995)


Original Comments

Feedback Bot on 6/24/2021, 11:22 PM:

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)

pranavkm commented 3 years ago

@lewing / @thaystg do you have any thoughts on what the expected behavior here is? Should we transfer the issue to runtime for further follow up?

lewing commented 3 years ago

sure, transfer it

ghost commented 3 years ago

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](https://developercommunity.visualstudio.com/t/Blazor-WebAssembly-debugger-jumps-into-J/1460253)._ --- Debugging Blazor apps, when it stops in a breakpoint, pressing F10 or even F5 sometimes, it jumps from C# into the JS code of the mono/CLR, which makes no sense. I would expect to only stop in my C# code and not in minimise JS from the framework, which is useless. ! [image.png] (https://aka.ms/dc/image?name=Bdae72a2c859b416abae54aeb5aa71c7f637601756372352277_20210625-095358-image.png&tid=dae72a2c859b416abae54aeb5aa71c7f637601756372352277) ! [image.png] (https://aka.ms/dc/image?name=B08eea34afe7f462691618cc5df896729637601755533096995_20210625-095234-image.png&tid=08eea34afe7f462691618cc5df896729637601755533096995) --- ### Original Comments #### Feedback Bot on 6/24/2021, 11:22 PM:

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: -
ghost commented 3 years ago

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](https://developercommunity.visualstudio.com/t/Blazor-WebAssembly-debugger-jumps-into-J/1460253)._ --- Debugging Blazor apps, when it stops in a breakpoint, pressing F10 or even F5 sometimes, it jumps from C# into the JS code of the mono/CLR, which makes no sense. I would expect to only stop in my C# code and not in minimise JS from the framework, which is useless. ! [image.png] (https://aka.ms/dc/image?name=Bdae72a2c859b416abae54aeb5aa71c7f637601756372352277_20210625-095358-image.png&tid=dae72a2c859b416abae54aeb5aa71c7f637601756372352277) ! [image.png] (https://aka.ms/dc/image?name=B08eea34afe7f462691618cc5df896729637601755533096995_20210625-095234-image.png&tid=08eea34afe7f462691618cc5df896729637601755533096995) --- ### Original Comments #### Feedback Bot on 6/24/2021, 11:22 PM:

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-Debugger-mono`, `area-Diagnostics-coreclr`, `untriaged`
Milestone: -
lewing commented 3 years ago

Without digging into the details I suspect this is the expected behavior of the current code, we should consider if it makes sense to be more aggressive about filtering out the implementation details here.

rmencia-isv commented 3 years ago

I created this item because me and my team we have experienced this a number of times. The first thing that comes to our heads is, something went wrong, the debugger/VS has failed again, restart the application or even VS. Even when we realised that it was happening consistently but nothing was broken, we just wasted some time trying to figure out what was happening. More junior guys kept asking the more senior devs to get help because they thought their VS install was wrong and even wasted a full day reinstalling VS.

I don't think that any developers using Blazor need to see the minimised code of the CLR in JS. Maybe it's something that you would need for the Blazor framework development, but you could accomplish that by adding a setting/flag in VS to enable it.

Just my point of view.

lewing commented 3 years ago

@rmencia-isv the tricky part here is passing the flags down to the wasm debugger, we are working on it.

ilonatommy commented 2 years ago

@thaystg what is the status on this? Do we have access to original screenshots? Can we reproduce it?

thaystg commented 2 years ago

@rmencia-isv are you still getting this behavior?

ghost commented 2 years ago

This issue has been marked needs-author-action and may be missing some important information.

rmencia-isv commented 2 years ago

Sorry, I'm not doing any debugging on blazor at the moment, I'm working on the API. I was getting very frustrated with blazor dev work, so I decided to complete the API and wait for a few more versions to fix the large number of issues I was finding every day.

Get Outlook for Androidhttps://aka.ms/AAb9ysg

Roberto Mencia Franco Principal Solutions Architect

40 Rosslyn Street West Melbourne VIC 3003 T: 03 9825 7200 | D: 03 9825 7221<tel:03%209825%207221> @.**@.>

[cid:isv_logo_emailsignature_c7e588ed-f2af-475e-9fd5-ac616247555f.png]

[cid:isv_blueblogicon_32x32px_ce38392c-df77-4e11-ba92-5f2222689245.png]https://is.vic.edu.au/media-centre/blog/ [cid:isv_bluelinkedinicon_32x32px_0838ad28-6fa9-46e7-a61b-c84b567e3f35.png] https://www.linkedin.com/company/independent-schools-victoria/mycompany/ [cid:isv_bluefbicon_32x32px_faca1ac8-e138-40a7-8af4-04d9d1edad5c.png] https://www.facebook.com/IndSchoolsVictoria [cid:isv_bluetwittericon_32x32px_48f38438-42a0-427e-b326-b9f367a20f00.png] https://twitter.com/IndSchoolsVic [cid:isv_blueyticon_32x32px_3ba24e02-7c77-4f92-9663-dee38134d93e.png] https://www.youtube.com/channel/UCDGrFIPCQF4WLtItF4DlHMg

@.***

https://is.vic.edu.au/programs/principals-leadership-academy/https://is.vic.edu.au/programs/teacher-fellowship-program/https://bit.ly/3Hi2x2ghttps://bit.ly/3Hi2x2ghttps://bit.ly/isv-ohshttps://bit.ly/3Hi2x2ghttps://bit.ly/isv-ohshttps://bit.ly/3xFPG5Mhttps://bit.ly/3lPGS8Ohttps://bit.ly/3GiX61vhttps://bit.ly/3rEY9omhttps://bit.ly/3rEY9omhttps://is.vic.edu.au/programs/principals-leadership-academy/https://is.vic.edu.au/programs/principals-leadership-academy/https://bit.ly/3hkNVUchttps://bit.ly/3tC96XFhttps://bit.ly/3HWqZFGhttps://bit.ly/36m4gWGhttps://bit.ly/3K5So9Xhttps://bit.ly/3LOi9Mrhttps://is.vic.edu.au/learning-and-development/reignite-series/https://is.vic.edu.au/learning-and-development/reignite-series/#unpacking-resiliencehttps://bit.ly/3KENjoFhttps://bit.ly/3Pv1qQVhttps://bit.ly/394JNHjhttps://bit.ly/39o14LL[cid:lead_survey2022_emailsignaturebanner_abd2a967-2ee5-414b-8500-f90774970571.png]https://bit.ly/3Pv1qQV https://bit.ly/3kmmwn6 We work flexibly at Independent Schools Victoria. I'm sending this message now because this time suits me, and I encourage you to read, respond or action this email at a time that best works for you. Read our email disclaimerhttps://is.vic.edu.au/terms-of-use/.


From: Thays Grazia @.> Sent: Monday, June 20, 2022 9:58:24 PM To: dotnet/runtime @.> Cc: Roberto Mencia Franco @.>; Mention @.> Subject: Re: [dotnet/runtime] Blazor WebAssembly debugger jumps into JS code mono CLR while debugging C# only code (#55214)

@rmencia-isvhttps://github.com/rmencia-isv are you still getting this behavior?

— Reply to this email directly, view it on GitHubhttps://github.com/dotnet/runtime/issues/55214#issuecomment-1160356336, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ATSGAELIURXYG2HOQFXGP33VQBMGBANCNFSM4747RIEA. You are receiving this because you were mentioned.Message ID: @.***>

ghost commented 2 years ago

This issue has been automatically marked no-recent-activity because it has not had any activity for 14 days. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will remove no-recent-activity.

ghost commented 2 years ago

This issue will now be closed since it had been marked no-recent-activity but received no further activity in the past 14 days. It is still possible to reopen or comment on the issue, but please note that the issue will be locked if it remains inactive for another 30 days.