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

Application crashes with LWJGL3 backend: pointer being freed was not allocated #5205

Closed
tyrondis opened this Issue May 1, 2018 · 2 comments

Comments

Projects
None yet
3 participants
@tyrondis

tyrondis commented May 1, 2018

Issue details

When running my application with the LWJGL3 backend, it crashed right upon starting with the error message:
java(84925,0x7fffb15f6380) malloc: *** error for object 0x11f762180: pointer being freed was not allocated

This does not occur with the LWJGL backend.

Reproduction steps/code

Use LWJGL3, start application.

Version of LibGDX and/or relevant dependencies

LibGDX: 1.9.8
Java: 1.8.0_171-b11
OSX: 10.13.4 (17E199)

Stacktrace

java(84925,0x7fffb15f6380) malloc: *** error for object 0x11f762180: pointer being freed was not allocated

Please select the affected platforms

  • Android
  • iOS (robovm)
  • iOS (MOE)
  • HTML/GWT
  • Windows
  • Linux
  • MacOS

@tyrondis tyrondis changed the title from Application crashed with LWJGL3: pointer being freed was not allocated to Application crashes with LWJGL3: pointer being freed was not allocated May 1, 2018

@tyrondis tyrondis changed the title from Application crashes with LWJGL3: pointer being freed was not allocated to Application crashes with LWJGL3 backend: pointer being freed was not allocated May 1, 2018

@Tom-Ski

This comment has been minimized.

Member

Tom-Ski commented May 1, 2018

Seen this before with mac. Not sure the what the absolute cause is here as i don't have a device i can reproduce this on, but the gpu is being switched from discrete to integrated. At which point this error happens. This usually happens when transitioning from using an external monitor, or exiting a game, mac seems to put you back on integrated, (probably to save power). You can confirm this by manually switching back to discrete gpu with any application that can manage this on macosx and running again

This is also most likely a lwjgl3 issue, if you can confirm that this is not a problem with a standard lwjgl3 (no libgdx) application, we can try to look into it, but afaik this is not something with libgdx itself.

@Tom-Ski Tom-Ski closed this May 1, 2018

@mudlee

This comment has been minimized.

mudlee commented Aug 30, 2018

Regarding this thread, it can be solved with a VM parameter:

-Dorg.lwjgl.system.allocator=system
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment