dotnet gcdump collect timeout parameter is ignored

未关闭

#5,646 创建于 2025年11月26日 0 条评论 0 个 reaction 已指派 0 人在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度: 3/5
预计耗时: 1-2 天
新手友好度: 42/100

Issue 类型: 缺陷
描述清晰度: 基本清楚
活跃度: 停滞
领域: tooling

调研方向

从 DotNetHeapDump/EventPipeDotNetHeapDumper.cs 开始，重点查看 stack trace 中显示的第 134 行 DumpFromEventPipe 调用和第 363 行 EventPipeSessionController 构造函数。重新执行两个 gcdump 命令，并验证控制 IPC 操作的是所请求的超时，而不是固定的 30 秒限制。

由索引模型根据 Issue 内容生成。

描述

bug

Description

I have my IIS 7 process running and trying to make a dump of it. My issue is similar to #1786.
Changing the order of arguments doesn't help.

IIS 7

dotnet-gcdump collect --process-id 110492 -v -t 120

C:\Users\alex>dotnet-gcdump collect --process-id 110492 -v -t 120
Writing gcdump to 'C:\Users\alex\20251126_163114_110492.gcdump'...
  0.0s: Creating type table flushing task
 30.0s: [Error] Exception during gcdump: System.TimeoutException: The operation has timed out.
   at System.IO.Pipes.NamedPipeClientStream.ConnectInternal(Int32 timeout, CancellationToken cancellationToken, Int32 startTime)
   at Microsoft.Diagnostics.NETCore.Client.IpcEndpointHelper.Connect(IpcEndpointConfig config, TimeSpan timeout) in /_/src/Microsoft.Diagnostics.NETCore.Client/DiagnosticsIpc/IpcTransport.cs:line 67
   at Microsoft.Diagnostics.NETCore.Client.PidIpcEndpoint.Connect(TimeSpan timeout) in /_/src/Microsoft.Diagnostics.NETCore.Client/DiagnosticsIpc/IpcTransport.cs:line 264
   at Microsoft.Diagnostics.NETCore.Client.IpcClient.SendMessageGetContinuation(IpcEndpoint endpoint, IpcMessage message) in /_/src/Microsoft.Diagnostics.NETCore.Client/DiagnosticsIpc/IpcClient.cs:line 40
   at Microsoft.Diagnostics.NETCore.Client.EventPipeSession.Start(IpcEndpoint endpoint, EventPipeSessionConfiguration config) in /_/src/Microsoft.Diagnostics.NETCore.Client/DiagnosticsClient/EventPipeSession.cs:line 45
   at Microsoft.Diagnostics.NETCore.Client.DiagnosticsClient.StartEventPipeSession(IEnumerable`1 providers, Boolean requestRundown, Int32 circularBufferMB) in /_/src/Microsoft.Diagnostics.NETCore.Client/DiagnosticsClient/DiagnosticsClient.cs:line 75
   at Microsoft.Diagnostics.Tools.GCDump.EventPipeSessionController..ctor(Int32 pid, String diagnosticPort, List`1 providers, Boolean requestRundown) in /_/src/Tools/dotnet-gcdump/DotNetHeapDump/EventPipeDotNetHeapDumper.cs:line 363
   at Microsoft.Diagnostics.Tools.GCDump.EventPipeDotNetHeapDumper.DumpFromEventPipe(CancellationToken ct, Int32 processId, String diagnosticPort, MemoryGraph memoryGraph, TextWriter log, Int32 timeout, DotNetHeapInfo dotNetInfo) in /_/src/Tools/dotnet-gcdump/DotNetHeapDump/EventPipeDotNetHeapDumper.cs:line 134
[ 30.0s: Done Dumping .NET heap success=False]
        Failed to collect gcdump. Try running with '-v' for more information.

dotnet-gcdump collect --process-id 110492 --timeout 120 -v

C:\Users\alex>dotnet-gcdump collect --process-id 110492 --timeout 120 -v
Writing gcdump to 'C:\Users\alex\20251126_163436_110492.gcdump'...
  0.0s: Creating type table flushing task
 30.0s: [Error] Exception during gcdump: System.TimeoutException: The operation has timed out.
   at System.IO.Pipes.NamedPipeClientStream.ConnectInternal(Int32 timeout, CancellationToken cancellationToken, Int32 startTime)
   at Microsoft.Diagnostics.NETCore.Client.IpcEndpointHelper.Connect(IpcEndpointConfig config, TimeSpan timeout) in /_/src/Microsoft.Diagnostics.NETCore.Client/DiagnosticsIpc/IpcTransport.cs:line 67
   at Microsoft.Diagnostics.NETCore.Client.PidIpcEndpoint.Connect(TimeSpan timeout) in /_/src/Microsoft.Diagnostics.NETCore.Client/DiagnosticsIpc/IpcTransport.cs:line 264
   at Microsoft.Diagnostics.NETCore.Client.IpcClient.SendMessageGetContinuation(IpcEndpoint endpoint, IpcMessage message) in /_/src/Microsoft.Diagnostics.NETCore.Client/DiagnosticsIpc/IpcClient.cs:line 40
   at Microsoft.Diagnostics.NETCore.Client.EventPipeSession.Start(IpcEndpoint endpoint, EventPipeSessionConfiguration config) in /_/src/Microsoft.Diagnostics.NETCore.Client/DiagnosticsClient/EventPipeSession.cs:line 45
   at Microsoft.Diagnostics.NETCore.Client.DiagnosticsClient.StartEventPipeSession(IEnumerable`1 providers, Boolean requestRundown, Int32 circularBufferMB) in /_/src/Microsoft.Diagnostics.NETCore.Client/DiagnosticsClient/DiagnosticsClient.cs:line 75
   at Microsoft.Diagnostics.Tools.GCDump.EventPipeSessionController..ctor(Int32 pid, String diagnosticPort, List`1 providers, Boolean requestRundown) in /_/src/Tools/dotnet-gcdump/DotNetHeapDump/EventPipeDotNetHeapDumper.cs:line 363
   at Microsoft.Diagnostics.Tools.GCDump.EventPipeDotNetHeapDumper.DumpFromEventPipe(CancellationToken ct, Int32 processId, String diagnosticPort, MemoryGraph memoryGraph, TextWriter log, Int32 timeout, DotNetHeapInfo dotNetInfo) in /_/src/Tools/dotnet-gcdump/DotNetHeapDump/EventPipeDotNetHeapDumper.cs:line 134
[ 30.0s: Done Dumping .NET heap success=False]
        Failed to collect gcdump. Try running with '-v' for more information.

Configuration

dotnet gcdump --version
9.0.652701+240cb1ce5bc30594c515206764241d7982e384af

dotnet --info

C:\Users\alex>dotnet --info .NET SDK: Version: 9.0.304 Commit: f12f5f689e Workload version: 9.0.300-manifests.610a1858 MSBuild version: 17.14.16+5d8159c5f

Runtime Environment:
OS Name: Windows
OS Version: 10.0.26100
OS Platform: Windows
RID: win-x64
Base Path: C:\Program Files\dotnet\sdk\9.0.304\

.NET workloads installed:
There are no installed workloads to display.
Configured to use loose manifests when installing new manifests.

Host:
Version: 9.0.8
Architecture: x64
Commit: aae90fa090

.NET SDKs installed:
3.1.100 [C:\Program Files\dotnet\sdk]
6.0.428 [C:\Program Files\dotnet\sdk]
9.0.304 [C:\Program Files\dotnet\sdk]

.NET runtimes installed:
Microsoft.AspNetCore.App 3.1.0 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 6.0.36 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 7.0.7 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 8.0.19 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 9.0.8 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 3.1.0 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 5.0.17 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 6.0.36 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 7.0.7 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 8.0.6 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 8.0.19 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 9.0.4 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 9.0.8 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 3.1.0 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 5.0.17 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 6.0.36 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 7.0.7 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 8.0.6 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 8.0.19 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 9.0.4 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 9.0.8 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

Other architectures found:
x86 [C:\Program Files (x86)\dotnet]
registered at [HKLM\SOFTWARE\dotnet\Setup\InstalledVersions\x86\InstallLocation]

Environment variables:
Not set

global.json file:
Not found

Regression?

Other information

主要语言: C++
星标: 1.3k
派生: 407
平均合并: 21 小时 5 分钟
30 天内合并 PR: 78

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

没有 Dockerfile 或 Docker Compose 文件
没有 Pull Request 模板
没有贡献指南

从这里开始

先读完整个 Issue，再读项目的贡献指南。
在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
Fork 仓库，在一个分支上完成修改。
提交 Pull Request，并在描述里引用这个 Issue 编号。

dotnet/diagnostics 的其他 Issue

Fix StackAndOtherTests.script line number verification for .NET 11 and Windows x64
可能重新可做关联的 PR 已关闭且未合并。未关闭
- 哪里不对？
难度 2/5 1-3 小时新手友好度 65/100

dotnet/diagnostics#5884 · 2 条评论 · 2026年6月17日创建

维护者通常 1 天内回复
[dnceng-bot] Branch `diagnostics/release/stable` can't be merged to Azdo internal branch
未关闭
- 哪里不对？
难度 4/5 3-5 天新手友好度 25/100

dotnet/diagnostics#6225 · 2026年11月11日创建

维护者通常 1 天内回复
Linux arm64 single-file CI failures caused by inconsistent .NET 11 host package restore
未关闭
- 哪里不对？
难度 4/5 3-5 天新手友好度 48/100

dotnet/diagnostics#6213 · 2026年11月11日创建

维护者通常 1 天内回复
Isolate SOS hosting from other debugger extensions that use managed code
可能已有人在做关联的 PR 仍在进行中或已合并。未关闭
- 哪里不对？
bug

难度 5/5 一周以上新手友好度 25/100

dotnet/diagnostics#6207 · 2026年11月10日创建

维护者通常 1 天内回复
[Known Build Error] PrintException_TaskExceptionChain missing source-line annotations on Windows ARM64
未关闭
- 哪里不对？
Known Build Error

难度 4/5 3-5 天新手友好度 49/100

dotnet/diagnostics#6190 · 2026年11月4日创建

维护者通常 1 天内回复

查看 dotnet/diagnostics 的全部 Issue

相似的 Issue

Any.Prototype as a struct-pointer DllCall argument or field value crashes: IsCArrayOf dereferences a null base (since 8fcbf453)
未关闭
- 哪里不对？
难度 2/5 1-3 小时新手友好度 76/100

AutoHotkey/AutoHotkey#380 · 2026年11月13日创建
S3 store: document that environment credentials override ?profile= (since 2.33.2)
未关闭
- 哪里不对？
documentation

难度 1/5 1-3 小时新手友好度 84/100

NixOS/nix#16811 · 2026年11月12日创建

维护者通常 1 天内回复
Lua File: add readWhole()
未关闭
- 哪里不对？
难度 2/5 1-3 小时新手友好度 69/100

grumpycoders/pcsx-redux#2667 · 2026年11月12日创建
GCC 15.2: -Wcast-qual warning - cast discards const qualifier from pointer target type (H5trace.c)
未关闭
- 哪里不对？
难度 2/5 1-3 小时新手友好度 73/100

HDFGroup/hdf5#6878 · 2026年11月12日创建

维护者通常 1 天内回复
file kvstore: after a crashed write, the next shorter write returns the new value plus stale bytes (regression in 0.1.65)
未关闭
- 哪里不对？
难度 2/5 1-3 小时新手友好度 88/100

google/tensorstore#305 · 2026年11月12日创建

更多 C++ Issue

dotnet gcdump collect timeout parameter is ignored

哪里不对？

评估

调研方向

描述

Description

Configuration

Regression?

Other information

环境准备

从这里开始

dotnet/diagnostics 的其他 Issue

哪里不对？

哪里不对？

哪里不对？

哪里不对？

哪里不对？

相似的 Issue

哪里不对？

哪里不对？

哪里不对？

哪里不对？

哪里不对？

把新 issue 发到你的邮箱