-
Notifications
You must be signed in to change notification settings - Fork 224
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Furnace crashed while playing a certain song #2330
Comments
Sadly, furnace_crash.txt is not useful. If you are using an artifact from the Actions tab, please make sure you have extracted furnace.pdb alongside furnace.exe. |
That is odd. I extracted both furnace.pdb and furnace.exe, considering that both of the "Date modified" is at the same time. |
It is causing Furnace 0.6.7 and newer to freeze (Maybe some older, but 0.6.3 works). And, because it's just freezing, it's not throwing an error. Update: It actually does load eventually on the Win64 build, but it crashes on both Win32 builds of 0.6.7. More weird stuff. |
32-bit specific crash... Oh no... |
I am unable to reproduce this bug. I have tried loading this song over and over for a while, yet none of these attempts have resulted in a crash. It does take very long to load - megasamples and rendering don't go well together. Valgrind does not detect any errors either... @Supreme-Man-1942 May you provide a backtrace? Download the latest 32-bit artifact in Actions tab, extract everything including furnace.pdb and try crashing Furnace. Then look at furnace_crash.txt in your user directory (e.g. |
Now I can only get it to crash in the WinXP build, and that might just be because I'm using Win10. I'm going to see if I can test it on XP. Update: This is so weird. It suddenly started crashing Standard 32 again, but it won't crash on the XP build in my VM... And the latest artifact won't crash. Update 2: It seem intermittent whether it'll crash or not, now WinXP build isn't crashing on Win10, but the Standard 32 is. So far, the latest artifact has never crashed. |
Do you at least have furnace_crash.txt? |
It isn't giving any useful info, that I know of, but here: Stack trace (most recent call last): |
Guess what. I tried opening a different song ("donttryreality.fur". You might recognize it.), and it crashed the same way... I'm wondering if 0.6.7 Win32 somehow failed to compile properly, or something, because they are the only ones I can get to crash like that. Here's the new furnace_crash.txt. It seems a little more useful, though... Stack trace (most recent call last): Edit: I just figured out that it's being caused by dragging and dropping the file into the program. But it still only happens in 0.6.7 Win32. It also doesn't matter what kind of file it is. It can be a .exe and it'll crash. |
Version of Windows? |
Windows 10 22H2. |
Go to Event Viewer and find the latest application crash event related to Furnace. If you see something with the word "ill" or "illegal", then what is your processor? |
It says "Unknown". |
Unknown? Are you running Windows on a virtual machine or ancient processor? |
I'm not sure what I'm supposed to be looking for specifically in the log,
but my junk laptop that I use has an AMD A10 in it.
I would post the entire log, but I think there's sensitive info in it.
|
So... I've tested the standard 32bit version on multiple Win10 computers, and it crashed. I tested in on Linux Mint 32bit (Don't remember what version) through wine, and it didn't crash, I couldn't get it to open on Windows Vista 32, and it didn't crash on Windows XP. I have no idea what the bug is, but I'm wondering if it fixed itself, because I can only replicate it with both Win32 builds of 0.6.7, and it doesn't always crash in the XP one. |
What do the crash logs say? |
Stack trace (most recent call last): Two things are puzzling me about this: I'm honestly thinking maybe someone should try recompiling 0.6.7 Win32, and see if it still crashes. |
I was playing this song, and it somehow crashed.
BotB 67560 damifortune - rosegarden.zip
furnace.log
furnace_crash.txt
The text was updated successfully, but these errors were encountered: