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.

Sign up for GitHub

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

Jump to bottom

[Blazor] debugging startup takes 24 seconds while without it loads instantly #49244

Open
1 task done
xperiandri opened this issue Jul 6, 2023 · 2 comments
Open
1 task done

[Blazor] debugging startup takes 24 seconds while without it loads instantly #49244

xperiandri opened this issue Jul 6, 2023 · 2 comments
Labels
area-networking Includes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractions

Comments

@xperiandri
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Describe the bug

After I set up my enterprise-grade solution, debug startup time increased from 5 seconds which is pretty nice to 24-28 seconds which is not acceptable

Expected Behavior

Debugging startup time takes no more than 10 seconds

Steps To Reproduce

  1. dotnet new -i Bolero.Templates

  2. dotnet new bolero-app -o MyBoleroApp

  3. Add "inspectUri": "{wsProtocol}://{url.hostname}:{url.port}/_framework/debug/ws-proxy?browser={browserInspectUri}", to launchSettings.json as per [Debugging] Breakpoint is only hit on the first load fsbolero/Bolero#307 (comment)

  4. Run in debug mode and see that app loads in 5 seconds

  5. unpack App.zip and run in debug mode Marketplace.Server

  6. See that it loads very slow!

Exceptions (if any)

No response

.NET Version

7.0.102

Anything else?

Visual Studio 2022 17.7.0 Preview 2.0
@rogihee
Copy link
Contributor

rogihee commented Jul 7, 2023

Yes, with me on 17.6.4 it takes up to 12 seconds to download the browserLink:
image

Not sure if it's the same issue but it's quite a wait to start every time with the debugger!

@amcasey amcasey added area-networking Includes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractions and removed area-runtime labels Aug 25, 2023
@dotnet-policy-service dotnet-policy-service bot added the pending-ci-rerun When assigned to a PR indicates that the CI checks should be rerun label Feb 6, 2024
@wtgodbe wtgodbe removed the pending-ci-rerun When assigned to a PR indicates that the CI checks should be rerun label Feb 6, 2024
@dotnet-policy-service dotnet-policy-service bot added the pending-ci-rerun When assigned to a PR indicates that the CI checks should be rerun label Feb 6, 2024
@xperiandri
Copy link
Author

Looks like it was fixed in 8.0

@wtgodbe wtgodbe removed the pending-ci-rerun When assigned to a PR indicates that the CI checks should be rerun label Feb 13, 2024
@dotnet dotnet deleted a comment from dotnet-policy-service bot Feb 13, 2024
@dotnet dotnet deleted a comment from dotnet-policy-service bot Feb 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area-networking Includes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractions
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@xperiandri @rogihee @amcasey @wtgodbe