Thanks @araq, I'll work with @matkuki and see if we can narrow it down. Though
the demo app isn't too large, a few hundred lines.
The reason I thought it could be a compiler bug would be that it looks like the
some bugs from the early arc days, and that the stack trace becomes nebulous..
Though
The compiler could have miscompiled the program...
If the program is compiling into a binary - how would it be a compiler bug?
User error would be my guess - probably passing some memory to C that's already
been collected.
You need to create a small example program that still crashes. I'm (still)
willing to debug on Windows...
@matkuki reported running into an issue with the Fidgetty demo app when running
on Windows. It's a bit strange and also apparently only errors when run from
the Windows console:
> Funny observation: this only happens if I run the demo from the Windows
> console, if I run it with double-clicking
