Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

App crashes when Runnable / VoidBlocks are called from a background thread (aka RoboVM issue #1109) #140

Closed
fwolff opened this issue May 22, 2017 · 1 comment

Comments

@fwolff
Copy link
Contributor

fwolff commented May 22, 2017

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

fwolff pushed a commit to fwolff/robovm that referenced this issue May 22, 2017
@fwolff fwolff mentioned this issue May 22, 2017
florianf pushed a commit that referenced this issue May 22, 2017
@florianf
Copy link
Collaborator

Fixed by merging the PR.

dkimitsa added a commit to dkimitsa/robovm that referenced this issue May 25, 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants