microsoft / microsoft/SizeBench
Infinite "Initializing debugging engine"
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 175
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
When using features that require the debugging engine, SizeBench loops forever in "Initializing debugging engine" state.
What you are doing
- Download and install latest release from Windows Store.
- Run an analysis on a single binary. In my case this is C++ built with MSVC 2022 17.6.3, 50 MB exe and ~900 MB pdb.
- Select template foldability analysis
- In results, try to fall inside any record
It also reproduces with other features that require debugging engine.
Expected behavior
Either to have all necessary things installed with SizeBench or to provide meaningful error message with instructions for fixing an issue on user side.
Screenshots
Environment Details
- OS: Windows 11 21H2 (22000.2057)
- SizeBench version number 2.2302.2300.0 (git commit 91c1cfe6)
- Examined binary is built with MSVC 2022 17.6.3 and linked with Microsoft linker
Additional context
Application loops but doesn't hang, i.e. it responds to the input. I can use File and Help menus and open About SizeBench. Modal popup with "Initializing debugging engine" has a clickable X button but nothing happens on click. The longest trial is around 30 min with no progress. SizeBench.GUI.exe uses 0-1% of CPU. Memory consumption doesn't change.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue with the listed SizeBench release, Windows 11 environment, and MSVC-built binary, then trace the debugging-engine initialization path used by foldability analysis. Verify the behavior with a large PDB and confirm what happens when initialization cannot complete. Done means the required components are available or the application reports a useful error instead of looping indefinitely.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- desktop, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100