Crash on exit from demo
by David Dougher · in Torque Game Engine Advanced · 09/08/2006 (7:28 am) · 6 replies
Compiled the latest M4 from CVS with Visual Stuiod Express and ran through the demo. Actually ran better than the incldued exe. (Was getting pink flashing from the earlier compile whenever an outdoor scene went by the building opening.) However, when I went to exit the demo I got a crash. The log identified this as the culprit.
Error, a DecalManager (1b59838) isn't properly out of the bins!
If you need more than that line let meknow I've saved the log.
Error, a DecalManager (1b59838) isn't properly out of the bins!
If you need more than that line let meknow I've saved the log.
About the author
Owner - Pariah Games, Adjunct Professor - Bristol Community College, Mentor - Game Design - Met School Newport, Mentor - Game Design - Met School Providence
#2
Sidebar: Being a little pedantic, but this isn't a crash, it's an assert (probably an ISV, although you didn't say if you compiled in debug or release).
Especially with the brand new release of MS4, it can be very useful to give as much info as possible in the initial report so Brian, Ben and all can get a snapshot of the issue in a single glance!
Not trying to pick on you David at all, just trying to make this smooth for everyone.
09/08/2006 (9:27 am)
That almost always comes from forgetting to call Parent::onRemove() in a re-implemented remove function, and therefore SceneObject::removeFromScene() winds up not getting called.Sidebar: Being a little pedantic, but this isn't a crash, it's an assert (probably an ISV, although you didn't say if you compiled in debug or release).
Especially with the brand new release of MS4, it can be very useful to give as much info as possible in the initial report so Brian, Ben and all can get a snapshot of the issue in a single glance!
Not trying to pick on you David at all, just trying to make this smooth for everyone.
#3
The message did indeed come from a Debug version. No message when you run Release version.
Here's the complete text.
-----------------------------------------------------------------------------------------------
Runtine Error!
Program: C:\tse_M4\example|TSE_DEBUG.exe
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
------------------------------------------------------------------------------------------------
Doesn't say that it is an ISV error so I didn't report it as such.
09/08/2006 (10:35 am)
No offense intended and none taken. The message did indeed come from a Debug version. No message when you run Release version.
Here's the complete text.
-----------------------------------------------------------------------------------------------
Runtine Error!
Program: C:\tse_M4\example|TSE_DEBUG.exe
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
------------------------------------------------------------------------------------------------
Doesn't say that it is an ISV error so I didn't report it as such.
#4
09/08/2006 (12:07 pm)
I got the same a couple of times - no clue on what it is. More or less exact same code worked in MS3 (doesnt help much, but wanted to add a +1 vote to seeing this more than once)
#5
09/10/2006 (10:57 pm)
Same to me. Tested a release build and it crashes with the runtime error when hitting F11. 
#6
09/11/2006 (2:15 pm)
We've got some extra checking in now to make sure that TSE's internal state matches up with what's on the video card. It's detecting a mismatch at the end and asserting. I'll have a fix ASAP, thanks for letting us know. 
Associate Scott Burns
GG Alumni