Game Development Community

Perpetual Busy Loop/Crash in RunApplicationEventLoop

by Gary "ChunkyKs" Briggs · in Torque Game Engine · 04/30/2007 (4:51 pm) · 7 replies

RunApplicationEventLoop(); crash

I have *no* idea why this is happening or what to do about it. It happens, sometimes, when I add one of my ODE objects to the world. I just have no idea what's happening. Could anyone make any suggestions as to what I might look for?

The #ifdef wrapping that is TORQUE_MULTITHREAD. If I disable TORQUE_MULTITHREAD [experience here], then the same thing happens. This happens on both release and debug builds.

I have no idea what's going on. Uh, anyone?

Thanks,
Gary (-;

#1
05/01/2007 (10:18 am)
My first totally obvious thought is, you're crashing somewhere in ODE and there's no debugging symbols. Maybe link to a debug build of ODE and see if you get a better idea of where the crash is happening?

On an unrelated note, I am impressed at how you've managed to keep from cluttering your menu bar with crap.
#2
05/01/2007 (10:53 am)
@Rob - lol, good catch! My Dockbar (even reduced) stretches 75% across the bottom of my screen.
#3
05/01/2007 (11:29 am)
Wow, y'all are crazy.

icculus.org/~chunky/stuff/smallishdock.png
That's what it looks like when apps aren't running. Spotlight is my friend. Now you come to mention it, time for the WoW icon to go, too. If I'm not opening and closing it more than a couple times a day, then I don't bother putting it in the dock.

Back to the original topic, this is a debug build of ODE :-/

I mean, I'm pretty sure my ODE code is what's wrong here, since seems to always happen when I add an ODE object to the world, but I've no idea how to go about debugging this problem [I'm really pretty nooby at coding :-(]

Gary (-;
#4
05/01/2007 (3:30 pm)
That dock is sick. Just turn the damn thing off, why don'tcha.

Ok, so you're a noob. (Uh, NOW he says it, after that I've basically called him a coding demi-god on another thread.) (I call BS anyway. Noobs don't integrate ODE.) Set yourself some breakpoints, sprinkle a liberal dose of NSLog()s through the code, and start to narrow down the chunk of code that dies.

If it dies within ODE, don't link to the library; add the ODE code to your project. Then you can see what all's going on when the crash happens.

And Spotlight for launching apps? You're just a baby step away from becoming one of those Quicksilver zombies.
#5
05/01/2007 (5:16 pm)
Hm.

So, I've messed about with it a lot, and it seems like the problem is stuff being put in crazy places by ODE. I dunno what's up there. Thanks for the pointer to NSLog (It may not be fair to say I'm a complete programming noob, but I'm sure as hell new to programming macs :-))

And you guys are all freaks. Apple-space, start typing, apple-enter. I miss my old crazyhardcoded vtwm desktop with it's vi navigation shortcuts and hitting "enter" to bring up a terminal.

/me does the UNIX-user-stuck-in-the-dark-ages dance

Gary (-;
#6
05/03/2007 (9:24 am)
It sounds like you're one download away from becoming one of those Quicksilver crazy people. You might also like homepage.mac.com/tconkling/windowdragon/

Any update? Anything I can do to help? My game uses rigidshapes out the yin-yang and their bugs are starting to bug me.
#7
05/03/2007 (10:47 am)
Heh. I tried quicksilver long ago, but it did nothing for me.

I'm not really big on big desktop UI modifications on things like mac or windows. I can never get the nagging doubt out of my head that adding stuff from random third parties is probably making my UI less stable or slower.

Anyways. Try ODEScript. It may already solve all your problems. :-)

Gary (-;