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

failure starting debug in Aspire - port in use by aspire host process #1603

Open
burtonrodman opened this issue Nov 12, 2024 · 2 comments
Open
Labels
area-dotnet-debugging Issues around .NET Debugging with console, ASP.NET, or Aspire bug Something isn't working

Comments

@burtonrodman
Copy link

Type: Bug

  1. in an Aspire project -- 5 repos, each with .Net Core apps (api, Blazor, MVC, etc...).
  2. start debugging (launch.json, F5)
  3. encounter an exception
  4. stop debugging, make a code change
  5. try to start debugging again.
  6. some random set of resources fails to start
  7. click Play button in Dashboard on failed projects
  8. debugger stop with IOException - Failed to bind to address https://127.0.0.1:7140: already in use.
  9. netstat shows this port in use by aspire host process.

Extension version: 1.13.6
VS Code version: Code 1.95.2 (e8653663e8840adaf45af01eab5c627a5af81807, 2024-11-07T11:07:22.054Z)
OS version: Windows_NT x64 10.0.22631
Modes:

System Info
Item Value
CPUs 13th Gen Intel(R) Core(TM) i9-13900H (20 x 2995)
GPU Status 2d_canvas: enabled
canvas_oop_rasterization: enabled_on
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: disabled_off
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: enabled
webnn: disabled_off
Load (avg) undefined
Memory (System) 31.59GB (6.52GB free)
Process Argv --file-uri file:///d%3A/source/2010solutions/VisitingAngels/VisitingAngels.Aspire/VisitingAngels.Aspire.code-workspace --crash-reporter-id c8e3650d-a133-42e9-901c-3aa8e8465629
Screen Reader no
VM 0%
A/B Experiments
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492cf:30256860
pythonvspyt551cf:31179979
vscod805:30301674
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
962ge761:30959799
pythonnoceb:30805159
asynctok:30898717
pythonmypyd1:30879173
h48ei257:31000450
pythontbext0:30879054
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
jg8ic977:31013176
dvdeprecation:31068756
dwnewjupyter:31046869
impr_priority:31102340
nativerepl1:31139838
pythonrstrctxt:31112756
cf971741:31144450
iacca1:31171482
notype1cf:31157160
5fd0e150:31155592
dwcopilot:31170013
j44ff735:31179530

@burtonrodman
Copy link
Author

Image

@burtonrodman
Copy link
Author

netstat -aon | findstr ":7140"
  TCP    127.0.0.1:7140         0.0.0.0:0              LISTENING       25904
  TCP    [::1]:7140             [::]:0                 LISTENING       25904

Image

@WardenGnaw WardenGnaw added area-dotnet-debugging Issues around .NET Debugging with console, ASP.NET, or Aspire bug Something isn't working labels Nov 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-dotnet-debugging Issues around .NET Debugging with console, ASP.NET, or Aspire bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants