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
Application crashes with a bad access error when runnables or void blocks (Swift closures or Obj-c function pointers) are called from a background Java thread (e.g. a libgdx OpenGL thread). This issue was first reported as #1109 in the original RoboVM project and fixed in version 1.11.
I have been able to trace back this issue in RunnableAsObjCBlockMarshaler.java and I'll submit a PR soon.
Thanks
The text was updated successfully, but these errors were encountered:
fwolff
pushed a commit
to fwolff/robovm
that referenced
this issue
May 22, 2017
* origin/master:
Removed unused old simulator binaries.
Exclude some Entitlement keys (MobiVM#144)
Update README.md
Update README.md
Fix issue MobiVM#140 (MobiVM#142)
Add the "framework" compiler target (issue MobiVM#132) (MobiVM#141)
Added the ability to select one of several USB-connected physical devices with the robovm.device.udid parameter in the Gradle plugin. (MobiVM#139)
Update poms to next development version
Application crashes with a bad access error when runnables or void blocks (Swift closures or Obj-c function pointers) are called from a background Java thread (e.g. a libgdx OpenGL thread). This issue was first reported as #1109 in the original RoboVM project and fixed in version 1.11.
I have been able to trace back this issue in RunnableAsObjCBlockMarshaler.java and I'll submit a PR soon.
Thanks
The text was updated successfully, but these errors were encountered: