-
Notifications
You must be signed in to change notification settings - Fork 297
Crash while messing around with bitmap sizes #563
Copy link
Copy link
Closed
Labels
BugA report of unintended or broken behavior.A report of unintended or broken behavior.DebuggerPertains to the debugger.Pertains to the debugger.
Description
[Window Title]
Fatal Exception
[Content]
A fatal exception (code 0xc0000005) occurred. The process is terminating.
Press Ctrl+C to copy this text to clipboard, then create a new issue at
https://github.com/EpicGamesExt/raddebugger/issues
Call stack:
- [0x7ff74eb624f7] r_end_frame +119, render_d3d11.c line 826
- [0x7ff74ebb6dac] rd_frame +157004, raddbg_core.c line 17036
- [0x7ff74eb32491] entry_point +11121, raddbg_main.c line 686
- [0x7ff74ec78be1] w32_entry_point_caller +2961, os_core_win32.c line 1797
- [0x7ff74ec78c7d] wWinMain +29, os_core_win32.c line 1810
- [0x7ff74ec7a4c2] __scrt_common_main_seh +262, exe_common.inl line 288
- [0x7ff99e04259d] KERNEL32
- [0x7ff99e9caf78] ntdll
Version: 0.9.20 [6543dad]
[Generate Crash Dump File] [Close]
I was playing with the Bitmap window and must have made the bitmap size too large. I assume I caused raddbg to segfault.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
BugA report of unintended or broken behavior.A report of unintended or broken behavior.DebuggerPertains to the debugger.Pertains to the debugger.