Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
nwjs-sdk-v0.16.1-win-ia32 crash dump generated in the wrong location
See original GitHub issuefor nwjs-sdk-v0.16.1-win-ia32 the crash dump is generated inside %LOCALAPPDATA%\Chromium\User Data\Crashpad\reports where in the documentation it should be generated inside %LOCALAPPDATA%\CrashPad
Issue Analytics
- State:
- Created 7 years ago
- Comments:11 (8 by maintainers)
Top Results From Across the Web
Generate a kernel or complete crash dump - Windows Client
Learn how to generate a kernel or complete crash dump, and then use the output to troubleshoot several issues.
Read more >How to generate crash dumps on a Windows machine
Navigate to the location HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting. Select the Windows Error Reporting key and ...
Read more >How to enable core file dumps when an application crashes or ...
By default, core files are created in the working directory of the faulting application. · If you change to non-root user test via...
Read more >How to obtain application core dumps | Support - SUSE
Disable the limit for the maximum size of a core dump file; Configure a fixed location for storing core dumps; Disable AppArmor; Enable...
Read more >Understand and configure core dumps on Linux
But sometimes things go wrong and a process may crash. Depending on the configuration of the system a core dump is created.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Thank you, great work! 🙇 The bug, that no dump file at all is generated when
--user-data-dir=<some folder>is specified as launch argument for nw.exe is now resolved as well! I just tested withnw 0.21.5:and the crash dump is properly generated in
C:\Users\Admin\AppData\Roaming\App_B\Crashpad\reports\Otherwise
the dump is found here:
C:\Users\Admin\AppData\Local\App_A\User Data\Crashpad\reportsGood work!
FYI upstream had a related change: https://codereview.chromium.org/2487783002