- name
SKILL.md
Die Skill-Datei bleibt im Repository des Herausgebers.
Fügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add microsoft/win-dev-skills --skill windbg-user-virtual-memory-exhaustion -a cursor -yFügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add microsoft/win-dev-skills --skill windbg-user-virtual-memory-exhaustion -a claude-code -yFügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add microsoft/win-dev-skills --skill windbg-user-virtual-memory-exhaustion -a codex -yFügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add microsoft/win-dev-skills --skill windbg-user-virtual-memory-exhaustion -a grok -ySenden Sie die kopierte Nachricht in einem Grok Bot-Chat. Der Bot ruft diese SKILL.md von GitHub ab und fügt sie den Skills hinzu, die alle Ihre Bots gemeinsam nutzen.
Install this skill: https://github.com/microsoft/win-dev-skills/tree/HEAD/plugins/windbg/skills/windbg-user-virtual-memory-exhaustionVom Herausgeber
Load windbg-diagnostic-method first if it is not already loaded in this
conversation, and apply it throughout for evidence ranking, hypothesis testing,
confidence calibration, independent review, and report validation. This skill
adds the bug-family-specific commands and evidence requirements.
Investigate E_OUTOFMEMORY (0x8007000E), STATUS_NO_MEMORY (0xC0000017),
bad_alloc, or failed heap/virtual allocations in an application, service, or
user-mode driver host (including UMDF). Record the actual API, requested
size/alignment, architecture, flags, and error. Free physical RAM does not rule
out insufficient virtual address space, commit pressure, or applicable limits.
!address -summary
!address
!heap -s
Compare available regions with the attempted allocation's contiguous range and alignment requirements. Distinguish reserved, committed, free, image, mapped, stack, and heap ranges. A large reservation consumes VA without committing its entire range. Heap internals may require more than the user's requested bytes.
Report unavailable pages/map data rather than inferring completeness from a limited dump.
Use contemporaneous system memory counters or an appropriate live/kernel
session for system commit data. A process PEB is not a documented
MaximumCommit source. A process's committed bytes alone do not establish a
system-wide or job limit.
For 32-bit targets inspect /LARGEADDRESSAWARE and the host architecture;
2 GB versus up to 4 GB depends on those settings. Verify current documented
limits for the target Windows version and architecture instead of applying
one 64-bit limit to every system.
!address -f:Heap
!address -f:Stack
!heap -stat -h <heap-address>
Use !address -? and !heap -? for allocator/version-specific support.
Classify dominant heaps, stacks, mappings, images, and reserved arenas.
Large or numerous allocations are not automatically leaks: map them to cache
policy, owners, workload, and expected lifetimes.
Collect authorized time-series counters, repeated comparable snapshots, or allocation/free tracing across the workload. Compare warm-up with steady-state behavior and verify whether memory is reclaimed when work finishes.
One snapshot plus process uptime cannot prove a leak rate. For a suitable
user-mode recording use windbg-user-ttd-reverse-debugging-triage; for damaged allocations
use windbg-user-heap-corruption-investigation instead.
VirtualAlloc reservations with the correct VirtualFree release
contract; distinguish decommit from release.Name the failing allocation and pressure mechanism, identify the consumer with evidence, and exercise the remedy through warm-up, sustained load, and cleanup. Verify memory remains bounded or the intended allocation succeeds under the required constraints. Document configured system/job limits separately.
Follow FEEDBACK.md and submit reviewed, sanitized feedback to
WinDbg-Feedback.
Include windbg-user-virtual-memory-exhaustion and the package version from plugin.json;
no automatic dump or memory-content upload.
Use when a native app, service, or user-mode driver host allocation fails; distinguish VA exhaustion, fragmentation, and commit pressure. Not for managed .NET heap growth, proving a leak from one snap
---name: windbg-user-virtual-memory-exhaustiondescription: Use when a native app, service, or user-mode driver host allocation fails; distinguish VA exhaustion…---# plugins/windbg/skills/windbg-user-virtual-memory-exhaustion/SKILL.mdÜbersicht
Use when a native app, service, or user-mode driver host allocation fails; distinguish VA exhaustion, fragmentation, and commit pressure. Not for managed .NET heap growth, proving a leak from one snapshot, or corruption.
FAQ
Laden Sie plugins/windbg/skills/windbg-user-virtual-memory-exhaustion/SKILL.md vom Herausgeber herunter oder kopieren Sie den Pfad und öffnen Sie das Repository. PlugMCP listet den Skill und hostet die Datei nicht.
Der Herausgeber pflegt es unter https://github.com/microsoft/win-dev-skills.
Claude, Cursor, Codex und Grok Build können eine SKILL.md lesen, die Sie aus dem Repository des Herausgebers hinzufügen. Grok Bot installiert sie, wenn Sie den Link zum GitHub-Ordner des Skills in einem Chat senden.