getappmap / getappmap/appmap-js
Process killed with `0x40010004` on Windows
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 53
- Forks
- 18
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 8
Description
Typically some time after startup, the RPC server is killed with a 0x40010004 exit code on Windows.
It will be restarted by the process watcher and subsequently be killed with a 0xC0000142 error code until the process is aborted entirely.
Both error codes are listed here, but it's not clear whether or not they're related:
https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-erref/596a1078-e883-4972-9bbc-49e60bebca55
For example, 0xC0000142 is mapped to STATUS_DLL_INIT_FAILED:
{DLL Initialization Failed} Initialization of the dynamic link library %hs failed. The process is terminating abnormally.
However, dumpbin reports only standard Windows imports.
dbghelp.dll
WS2_32.dll
IPHLPAPI.DLL
PSAPI.DLL
USERENV.dll
ADVAPI32.dll
USER32.dll
CRYPT32.dll
bcrypt.dll
KERNEL32.dll
WINMM.dll
Contributor guide
No contributing guide indexed for this repository
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 examining the RPC server and process-watcher entry points, which are not named in the issue, and reproduce the Windows restart sequence if possible. Compare the 0x40010004 and 0xC0000142 failures, then use dumpbin to verify the listed imports; done means identifying the cause and preventing the repeated termination.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100