EpicGamesExt
Crash when running with bitmap view open
I can start and stop as much as I want with it closed, though.
After this crash, other graphics stuff on my computer starts getting weird until I close raddbg, as well. If I play a video in a browser, or do something in Spotify, then random windows will go black, pure white windows will pop up, my whole screen will go black, my cursor will randomly start moving at ~20% the normal speed and lagging, etc.
https://github.com/user-attachments/assets/75a88224-e1de-40a0-b696-bfe86a693b6a
Dump: https://drive.proton.me/urls/CQDBZ2A1JG#TztzaQV1h8pq
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:
1. [0x7ff78db2bb02] arena_alloc_ +194, base_arena.c line 53
2. [0x7ff78db324bf] ctrl_mem_stream_work +703, ctrl_core.c line 6045
3. [0x7ff78db2cbfd] async_work_thread__entry_point +461, async.c line 241
4. [0x7ff78db99688] os_w32_thread_entry_point +56, os_core_win32.c line 151
5. [0x7ffef63b7614] KERNEL32
6. [0x7ffef73826a1] ntdll
Version: 0.9.15 [33326a8]
What is the full bitmap view rule you are using, and can you evaluate the width/height parameters separately in the watch window? My first suspicion is that they are evaluating to something bogus and the debugger is not being robust-enough to that case.
Ah, sorry for the late reply here! The view rule is bitmap:{w:billband, h:crystal_length, fmt:r32}. Maybe they're evaluating to something bogus, but grid is float* grid = (float*)malloc(billband * crystal_length * sizeof(float)), so I would expect it to be fine? Is the bitmap view rule built to handle floats? Maybe the infinities in the array are messing with it? Everything displays as transparent for some reason:
Different call stack this time when it crashes as I inspect the bitmap in a popup window. Didn't need to run with it open to cause this one:
[Window Title]
Fatal Exception
[Content]
A fatal exception (code 0xc0000005) occurred. The process is terminating.
Call stack:
1. [0x7ff75cfbd309] r_end_frame +105, render_d3d11.c line 823
2. [0x7ff75cffa1db] rd_frame +96299, raddbg_core.c line 16948
3. [0x7ff75cf8f15d] entry_point +10077, raddbg_main.c line 794
4. [0x7ff75d08fe75] w32_entry_point_caller +2549, os_core_win32.c line 1724
5. [0x7ff75d08ff2d] wWinMain +29, os_core_win32.c line 1737
6. [0x7ff75d091052] __scrt_common_main_seh +262, exe_common.inl line 288
7. [0x7ffedb49e8d7] KERNEL32
8. [0x7ffedbaffbcc] ntdll
Version: 0.9.15 [33326a8]
When I export the content of grid to a PGM, this is the top of it:
The diagonal, the left and right edges, and the top right corner are infinities. Though I can't see them, I hover over and find the same thing in raddbg... sometimes? It's inconsistent whether or not the content shows up properly.