About Store Forum Documentation Contact



Post Reply 
[Solved] Crash after returning to world
Author Message
miro@3dea Offline
Member

Post: #1
[Solved] Crash after returning to world
Hello, we have a small world surrounded by sea (as you can see it under showcase section 3DEA project..). After moving away from it until out of the view range (1350), and than returning back again there are problems while world is starting to draw. Drawing is painfully slow, and finally the app is crashing with an error "Element out of range File:_Memc.h Line 14"
and debugging output in vs 2012 is:
Code:
DXGI WARNING: Process is terminating. Using simple reporting. Please call ReportLiveObjects() at runtime for standard reporting. [ STATE_CREATION WARNING #0: ]
DXGI WARNING: Live Producer at 0x000000000237DDC8, Refcount: 5. [ STATE_CREATION WARNING #0: ]
DXGI WARNING:     Live Object at 0x00000000023884B0, Refcount: 3. [ STATE_CREATION WARNING #0: ]
DXGI WARNING:     Live Object at 0x00000000023B8D80, Refcount: 1. [ STATE_CREATION WARNING #0: ]
DXGI WARNING: Live                         Object :      2 [ STATE_CREATION WARNING #0: ]
(This post was last modified: 02-28-2013 11:33 AM by miro@3dea.)
02-27-2013 05:26 PM
Find all posts by this user Quote this message in a reply
Esenthel Offline
Administrator

Post: #2
RE: Crash after returning to world
Can you attach a callstack?
Can you reproduce the error in the Editor or does it happen only in your codes?
02-27-2013 06:03 PM
Find all posts by this user Quote this message in a reply
miro@3dea Offline
Member

Post: #3
RE: Crash after returning to world
I'm still investigating this and now it seams that it is related to sound. We have objects that are sound containers only, with sound objects as children. When that object is about to reload, crash happens..

Unfortunately exception is not caught by debugger, so no stack..
No, no same behavior in editor..
02-27-2013 06:21 PM
Find all posts by this user Quote this message in a reply
miro@3dea Offline
Member

Post: #4
RE: Crash after returning to world
So, my bad after all.. first of all crash was there because of optimistic approach - without checking indexes while random accessing sub-objects. Actually that is not a problem because I want to avoid index checking in each update..
Real problem was that this container object was not set as Const and has no save/load methods overloads.. Setting it to Const solved the issue..
02-28-2013 11:32 AM
Find all posts by this user Quote this message in a reply
Post Reply