Thanks to all for your responses. A scene got presented and removed later on.
The app delegate had a currentScene property, and after I had activated all
debug features I saw that my scene class was being sent some message it didn't
respond to, but in fact was actually not even supposed to do so
On 01 Apr 2014, at 23:19, Alexander Reichstadt wrote:
> Is there a way to find the root cause of such a crash?
Vague idea: Set breakpoints on anything that can terminate an application (e.g.
exit() and abort()) and if one is triggered, see if the stack backtrace gives
any hints on what might be
template all works fine until one
> leaves the app and switches to another process, which results in random
> crashes without a backtrace. After having switched to another process and
> returning to the running or also paused game, it's only a question of time
> when it will c
On Apr 1, 2014, at 2:19 PM, Alexander Reichstadt wrote:
> It always seems to involve the main window. The trace is not very helpful as
> it crashes outside the app's own code. The last calls that I can see in the
> debugger are sometimes [NSApplication updateWindows], other times it's
> [NSWi
Hi,
in a project using the default Spritekit template all works fine until one
leaves the app and switches to another process, which results in random crashes
without a backtrace. After having switched to another process and returning to
the running or also paused game, it's only a que
On Mar 31, 2010, at 11:51, Ken Thomases wrote:
> On Mar 31, 2010, at 1:35 PM, Laurent Daudelin wrote:
>
>> In any case, what would cause an application built with the debug
>> configuration to not exhibit this bug at all while the same application
>> built with the release configuration will cr
On Mar 31, 2010, at 11:51, Ken Thomases wrote:
> On Mar 31, 2010, at 1:35 PM, Laurent Daudelin wrote:
>
>> In any case, what would cause an application built with the debug
>> configuration to not exhibit this bug at all while the same application
>> built with the release configuration will cr
On Mar 31, 2010, at 1:35 PM, Laurent Daudelin wrote:
> In any case, what would cause an application built with the debug
> configuration to not exhibit this bug at all while the same application built
> with the release configuration will crash randomly?
Changes in the layout of code or the sta
I'm turning toward the experts in the group here hopefully for some pointers.
I'm working on an application that runs for long period of time, collecting
information from the Internet using NSURLConnections. As such, I've been very
carefully with my memory management.
Now, I have problem where
Hello All,
I'm trying to hunt down a crash bug for two days now and I'm at a
complete loss, have finally run out of ideas what else I can try.
I've read the Corbin Dunn's EXC_BAD_ACCESS blog post as well as the
debugger magic tech note. I turned on debug frameworks,
NSZombieEnabled and
10 matches
Mail list logo
