ReSkate

0 Fork 0

mirror of https://github.com/Dingo-Shenanigans/ReSkate.git synced 2026-10-17 22:07:05 +02:00

Files

T

AyeZeeBB 3249f747dc Crash reports: the game's own fatal crashes come with the memory their stacks point at

Most crashes are caught by the game's own fatal handlers, which write a
dump of thread stacks only; the launcher could only copy it after the
game had exited. A crash on a freed or overwritten object then showed
the faulting registers but not the object or the list it came from.

- game_fatal_dump: the game's MiniDumpWriteDump import points at
  ReSkate. Before the game writes its dump, the crash reporter takes its
  own of the still-running game for the faulting thread; the game's dump
  follows as before. Reports say capture.source "game-fatal-handler".
- The reporter's dumps include the memory the stacks point at
  (MiniDumpWithIndirectlyReferencedMemory), a few MB more a report.
- The shared report says who asked for the dump (protocol version 4).
- Tests: a game-handler crash is captured with a heap block only its
  stack points at; ReSkate's own capture keeps it too.

2026-10-15 20:01:55 -05:00

Test

Discord Rich Presence, with joining from Discord

2026-10-09 22:51:22 -05:00

descriptor_heap_size.cpp

Descriptor heaps: dense custom maps no longer overflow the GPU's descriptor heap and crash it

2026-10-15 13:57:11 -05:00

descriptor_heap_size.h

Descriptor heaps: dense custom maps no longer overflow the GPU's descriptor heap and crash it

2026-10-15 13:57:11 -05:00

discord_presence.cpp

Launcher changelogs, download total, Discord joins skip the launcher window; Mod Options