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

Crashes in iOS Shipping build #37

Open
tustanivsky opened this issue Jan 30, 2024 · 1 comment
Open

Crashes in iOS Shipping build #37

tustanivsky opened this issue Jan 30, 2024 · 1 comment

Comments

@tustanivsky
Copy link

Shipping build of the game crashes on iOS with the following message:

*** error for object %p: pointer being freed was not allocated
 > MyGame-IOS-Shipping > MyGame-IOS-Shipping(45544,0x16be63000) malloc: *** error for object 0x4000000: pointer being freed was not allocated

According to captured crash call stacks the above error can come from a variety of places in plugin source code depending on the user's game flow (see the attachments). In some cases it can be "fixed" by not freeing up memory which was allocated for certain structs that the plugin's API exposes however that introduces memory leaks and doesn't feel like a proper solution by any means.

Callstack1.txt
Callstack2.txt
Callstack3.txt

Shipping build of the game is distributed via TestFlight and that's the only scenario when crash can be reproduced. The development build has been tested on several iOS devices and this configuration works as expected.

Also, here's an article that describes somewhat a similar problem but the suggested workaround doesn't seem to be applicable for engine downloaded via Epic Games launcher.

Additional info:

TurboLink plugin version: 1.3
Unreal Engine version: UE 5.3 (binary distribution)
macOS: 14.2.1
iOS: 17.2.1, 16.5
Xcode: 15.2

@rootux
Copy link
Contributor

rootux commented Jan 31, 2024

Yes. Same here. 🤚🏼
The interesting part is that when developing we didn't encounter those - probably because when developing - the ide holds a lot of pointers to those memory areas. and when shipping we immediately encounter them.

In our experience - this happened when our .proto had a bytes type. But I saw that happens in a few other places - memory got allocated and immediately deallocated on ios when shipping.

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