You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When calling playdate.system.error("somestring") the simulator prints the message in red to the console as expected.
When someone attempts to restart the simulator using cmd-/ctrl-R, the handler processes the event kEventTerminate. When you use certain functions ?that attempt to allocate?, the simulator freezes. Attaching a debugger shows a BAD_ACCESS_EXCEPTION after going trough a memtrace codepath
Interesting -- I've got a branch that completely cuts out the memtracing code when it's not turned on. I'll clean that up and submit a CR. We can see if it helps.
When calling playdate.system.error("somestring") the simulator prints the message in red to the console as expected.
When someone attempts to restart the simulator using cmd-/ctrl-R, the handler processes the event
kEventTerminate
. When you use certain functions ?that attempt to allocate?, the simulator freezes. Attaching a debugger shows a BAD_ACCESS_EXCEPTION after going trough a memtrace codepathFor a reproducible example, see ninovanhooff@79c8529
In this example it is the
things.join
call inproc print
where the crash happens.Reproduce:
Observed on Mac OS; simulator 2.6.2
The freeze does not happen when removing the
print "testtest"
lineThe text was updated successfully, but these errors were encountered: