Notes |
|
(0005444)
|
Blzut3
|
2012-11-29 16:00
|
|
You would probably need to see the frequency in which Zandronum processes start and how long it takes for the forkbombing to happen. I can't think of a reason it should be forking off hand. The only code I'm aware of that does forking is the timidity code and the crash handler.
If the forkbombing starts as soon as it locks up then it's the crash handler. Otherwise if it happens over time it might be something in the sound code. |
|
|
(0005548)
|
MazterQyoun-ae
|
2012-12-22 20:18
(edited on: 2012-12-22 20:19) |
|
I've accidentally encountered the same problem and it happened only after the game crashed, so it probably might be the crash handler?
edit: Mac OS X 10.8.2
|
|
|
(0005558)
|
Blzut3
|
2012-12-24 06:34
|
|
It's definitely the crash handler. Looks like it can be fixed by just using the crash handler from the latest ZDoom. |
|
|
|
Your proposed patch reverts the changes I made to these files (like logging the GCC version, not bothering the server with a window, using GAMENAMELOWERCASE instead of zdoom). Can you make a patch that keeps these changes? |
|
|
(0005606)
|
Blzut3
|
2012-12-29 02:43
|
|
Regarding the GCC version, did you mean GDB version? ZDoom appears to have removed the GCC version dumping, so do you want me to keep the GDB version dumping or also restore the GCC line? |
|
|
|
Yeah, I was referring to the GDB version. I didn't know though that ZDoom removed the GCC version. Was there a technical reason for this? If not, it would be great to have both back. If this causes technical problems, I'd say we can live without this. |
|
|
|
Thanks for your updated patch! I just pulled it. Should be tested in the next beta build. |
|
|
(0006278)
|
Oddbrother
|
2013-04-09 23:30
(edited on: 2013-04-09 23:37) |
|
Testing the alpha, I've re-created the crash from issue 0001073.
Success! No forkbombing in this one, lead straight to an error message (see attachment).
MacBook Pro: 13-inch, Mid-2009; Mac OS X Lion 10.7.5
|
|