OpenMW 0.18 RC crash after "coc" command on OS X

Support for running, installing or compiling OpenMW

Before you submit a bug report for the first time, please read: Bug reporting guidelines
corristo
Posts: 493
Joined: 12 Aug 2011, 08:29

OpenMW 0.18 RC crash after "coc" command on OS X

Post by corristo » 20 Sep 2012, 18:28

Let's discuss it here.

https://gist.github.com/3752643 — backtrace.

Found that there's no crash on "coc" on commit "6c03d7aec40e618a7b0a1e9fb0c00c5b2b6406ed" (before loading screen implementation).

corristo
Posts: 493
Joined: 12 Aug 2011, 08:29

Re: OpenMW 0.18 RC crash after "coc" command on OS X

Post by corristo » 20 Sep 2012, 21:20

this one started crashing: 2b339f6c0fd9242cd5bf800e68963acfa3abf479 (1st commit in scralw's loadingscreen branch).

But backtrace here is a bit more interesting than previous:
https://gist.github.com/3758112
(yes, it's really that long)

User avatar
Zini
Posts: 5537
Joined: 06 Aug 2011, 15:16

Re: OpenMW 0.18 RC crash after "coc" command on OS X

Post by Zini » 21 Sep 2012, 08:01

Huh? That looks like the same coc was executed several times in a row. Infinitely in fact. Did we really somehow produce a OS X only infinite recursion? Funny.

The last thing at the end of each cycle is a call to MWGui::loadingScreen::setLoadingProgress. For a simple test, I suggest to comment this function call out (it is located in MWGui::WindowManager) and see if the crash goes away.

User avatar
sirherrbatka
Posts: 2157
Joined: 07 Aug 2011, 17:21

Re: OpenMW 0.18 RC crash after "coc" command on OS X

Post by sirherrbatka » 21 Sep 2012, 08:14

That's what you get when you have only one semi-active developer for a platform... :/

User avatar
Zini
Posts: 5537
Joined: 06 Aug 2011, 15:16

Re: OpenMW 0.18 RC crash after "coc" command on OS X

Post by Zini » 21 Sep 2012, 08:14

Also, could you merge in my branch osxtest and see if that changes the nature of the crash? Please test this separately from what I proposed above.

corristo
Posts: 493
Joined: 12 Aug 2011, 08:29

Re: OpenMW 0.18 RC crash after "coc" command on OS X

Post by corristo » 21 Sep 2012, 10:25

Zini, tried your branch, same bt.

corristo
Posts: 493
Joined: 12 Aug 2011, 08:29

Re: OpenMW 0.18 RC crash after "coc" command on OS X

Post by corristo » 21 Sep 2012, 10:33

Commented all cals to "setLoadingProgress" in scene.cpp. No crash so far. (did that in current master, not in mentioned above commit)

User avatar
Zini
Posts: 5537
Joined: 06 Aug 2011, 15:16

Re: OpenMW 0.18 RC crash after "coc" command on OS X

Post by Zini » 21 Sep 2012, 11:00

Zini, tried your branch, same bt.
Exactly? Are you sure? It should be similar, but I would expect a few variations.

corristo
Posts: 493
Joined: 12 Aug 2011, 08:29

Re: OpenMW 0.18 RC crash after "coc" command on OS X

Post by corristo » 21 Sep 2012, 11:47

here is your branch:

Code: Select all

* thread #1: tid = 0x1c03, 0x003e5ae3 openmw`OIS::MacKeyboard::capture() + 147, stop reason = EXC_BAD_ACCESS (code=1, address=0x83e5895d)
    frame #0: 0x003e5ae3 openmw`OIS::MacKeyboard::capture() + 147
    frame #1: 0x000c1f60 openmw`MWInput::InputManager::update(float, bool) + 64 at inputmanagerimp.cpp:242
    frame #2: 0x003bfdc6 openmw`OMW::Engine::frameRenderingQueued(Ogre::FrameEvent const&) + 134 at engine.cpp:70
    frame #3: 0x020c84a0 Ogre`Ogre::Root::_fireFrameRenderingQueued(Ogre::FrameEvent&) + 336 at OgreRoot.cpp:841
    frame #4: 0x020c8e1f Ogre`Ogre::Root::_updateAllRenderTargets() [inlined] Ogre::Root::_fireFrameRenderingQueued() + 77 at OgreRoot.cpp:896
    frame #5: 0x020c8dd2 Ogre`Ogre::Root::_updateAllRenderTargets() + 34 at OgreRoot.cpp:1395
    frame #6: 0x020c8d48 Ogre`Ogre::Root::renderOneFrame() + 104 at OgreRoot.cpp:978
    frame #7: 0x0000620c openmw`OEngine::Render::OgreRenderer::start() + 172 at renderer.cpp:73
    frame #8: 0x003c469c openmw`OMW::Engine::go() + 11964 at engine.cpp:407
    frame #9: 0x003b0119 openmw`main + 281 at main.cpp:273
    frame #10: 0x99457725 libdyld.dylib`start + 1
here is master:

Code: Select all

* thread #1: tid = 0x1c03, 0x003e5ae3 openmw`OIS::MacKeyboard::capture() + 147, stop reason = EXC_BAD_ACCESS (code=2, address=0xf)
    frame #0: 0x003e5ae3 openmw`OIS::MacKeyboard::capture() + 147
    frame #1: 0x000c1f60 openmw`MWInput::InputManager::update(float, bool) + 64 at inputmanagerimp.cpp:242
    frame #2: 0x003bfdc6 openmw`OMW::Engine::frameRenderingQueued(Ogre::FrameEvent const&) + 134 at engine.cpp:70
    frame #3: 0x020c84a0 Ogre`Ogre::Root::_fireFrameRenderingQueued(Ogre::FrameEvent&) + 336 at OgreRoot.cpp:841
    frame #4: 0x020c8e1f Ogre`Ogre::Root::_updateAllRenderTargets() [inlined] Ogre::Root::_fireFrameRenderingQueued() + 77 at OgreRoot.cpp:896
    frame #5: 0x020c8dd2 Ogre`Ogre::Root::_updateAllRenderTargets() + 34 at OgreRoot.cpp:1395
    frame #6: 0x020c8d48 Ogre`Ogre::Root::renderOneFrame() + 104 at OgreRoot.cpp:978
    frame #7: 0x0000620c openmw`OEngine::Render::OgreRenderer::start() + 172 at renderer.cpp:73
    frame #8: 0x003c469c openmw`OMW::Engine::go() + 11964 at engine.cpp:407
    frame #9: 0x003b0119 openmw`main + 281 at main.cpp:273
    frame #10: 0x99457725 libdyld.dylib`start + 1

User avatar
scrawl
Posts: 2152
Joined: 18 Feb 2012, 11:51

Re: OpenMW 0.18 RC crash after "coc" command on OS X

Post by scrawl » 21 Sep 2012, 12:46

The infinite recursion was a mistake on my side, but as you can see in commit messages its fixed a few commits later.

Have you tried to disable custom osx main loop yet? I have a feeling that could cause it.

Locked