TeamREPENTOGON / TeamREPENTOGON/REPENTOGON
Inconsistent crash when hitting the "exit game" button in the pause menu when testing a room in Basement Renovator
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 345
- Forks
- 51
- Avg merge
- 11h 2m
- Merged PRs (30d)
- 4
Description
I am on Repentogon+ nightly (43c774b).
For a while now (about 4 months, I'd say), the program used to test and create Isaac rooms, Basement Renovator, has been crashing randomly when pressing the "Exit Game" button on the pause menu. Normally this brings you to the main menu.
This is an inconsistent crash, only happening sometimes when pressing the exit game button.
The crashes do not occur when disabling Repentogon with the -repentogone command.
Disabling mods by pressing tab and continuing to playtest rooms while having Repentogon on will make the game crash when pressing the exit game button.
Reproducing the crash is difficult, as it can take many room tests to get a crash.
Sometimes retesting the same room when a crash happens does not lead to a crash as well, making reproduction VERY weird.
The log of the crash.
Video of the crash happening.
https://github.com/user-attachments/assets/3431ca80-5bbd-493c-ad44-a4dcaa2769b3
If it makes any difference, I am running the source version of Basement Renovator.
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 reviewing the attached log.txt and crash video, then compare behavior in Basement Renovator with Repentogon enabled and with the -repentogone command. Focus on the pause-menu "Exit Game" path during room testing, including after disabling mods with Tab. Done means identifying a reliable cause or reproduction for the intermittent crash.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- game-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100