Successfully packaged application doesn't work on MagicLeap

Development Platform & Builds XR Development
, , ,
1

Hi, I have developed an application for my MagicLeap. When I packaged it, everything went fine. When I uploaded it to the MagicLeap, everything went fine. But when I tried to start the application, the following error occured after a long time of loading…

error: mldb exited with code -117 stderr: Application ended with signal 'Segmentation fault'
mldb exited with code -117 stderr: Application ended with signal 'Segmentation fault'

and the Crash Report outputs the following error message:

09-29 13:53:03.873  5108     1 F libc    : Fatal signal 11 (SIGSEGV), code 1, fault addr 0x0 in tid 1 (MA)

Are there any suggestions or hints for this issue?

2

Segmentation faults are access violations related to memory access.

It could be its trying to write to non-writable space or trying to access a virtual address not mapped to a physical one.

3

Yeah I know this, but I don’t know what causes this error :confused:

4

Perhaps you need to run the app in debug mode

https://ml1-developer.magicleap.com/en-us/learn/guides/sdk-mldb-debugging-apps
It seems more of a magic leap problem than a direct unreal problem

Try getting logs from the device & you might get more detail what is causing the problem.

Are you a 100% sure the packaged app uploaded correctly onto the device?

Some people on forums have had problems for instance:
"My problem was i didn’t have the hub dongle attached (the hub allowed AC power to the Magic Leap and allowed a USB Type A connection to my computer instead of the USB C) "

Sometimes the device also needed an update.

Seeing as most memory management on the side of unreal is handled by unreal (it handles it’s entities life cycle) then maybe the problem lies elsewhere?
Unless you are using memcpy in pure c++ somewhere?