JME3.1 - Large number of exceptions signal 11 (SIGSEGV), code 1 (SEGV_MAPERR) for lib libopenalsoftjme.so

Hi guys,

I am getting many error reports of type “signal 11 (SIGSEGV), code 1 (SEGV_MAPERR)” for the lib libopenalsoftjme.so

More often for the “alcDeviceResumeSOFT” function.

Here is an example log:

106/5000
Jul 14 07:38 in version 39 of the app
Samsung Galaxy Core 2 (kanas), 768MB RAM, Android 4.4
Report 1 of 1

backtrace:
native: pc 000000000000b512 /data/app-lib/com.ectragames.capsracing-1/libopenalsoftjme.so
native: pc 000000000000c42d /data/app-lib/com.ectragames.capsracing-1/libopenalsoftjme.so
native: pc 000000000000ec93 /data/app-lib/com.ectragames.capsracing-1/libopenalsoftjme.so (alcDeviceResumeSOFT+70)
native: pc 000000000001dd4c /system/lib/libdvm.so (dvmPlatformInvoke+112)
native: pc 000000000004e213 /system/lib/libdvm.so (dvmCallJNIMethod(unsigned int const*, JValue*, Method const*, Thread*)+398)
native: pc 0000000000027160 /system/lib/libdvm.so
native: pc 000000000002e110 /system/lib/libdvm.so (dvmMterpStd(Thread*)+76)
native: pc 000000000002b7bc /system/lib/libdvm.so (dvmInterpret(Thread*, Method const*, JValue*)+184)
native: pc 0000000000060919 /system/lib/libdvm.so (dvmInvokeMethod(Object*, Method const*, ArrayObject*, ArrayObject*, ClassObject*, bool)+392)
native: pc 00000000000688ab /system/lib/libdvm.so
native: pc 0000000000027160 /system/lib/libdvm.so
native: pc 000000000002e110 /system/lib/libdvm.so (dvmMterpStd(Thread*)+76)
native: pc 000000000002b7bc /system/lib/libdvm.so (dvmInterpret(Thread*, Method const*, JValue*)+184)
native: pc 0000000000060637 /system/lib/libdvm.so (dvmCallMethodV(Thread*, Method const*, Object*, bool, JValue*, std::__va_list)+338)
native: pc 0000000000049dfb /system/lib/libdvm.so
native: pc 0000000000055417 /system/lib/libandroid_runtime.so
native: pc 00000000000569af /system/lib/libandroid_runtime.so (android::AndroidRuntime::start(char const*, char const*, bool)+358)
native: pc 0000000000001063 /system/bin/app_process
native: pc 000000000000e433 /system/lib/libc.so (__libc_init+50)
native: pc 0000000000000d80 /system/bin/app_process

The function suggests that it occurs after the application exits the background.

So I did the following test:

1 - When the application is playing a sequence of sound instances I press the screen lock button on the device. This forces it to be placed in the background;

2 - I repeat this process several times;

3 - Then at some point the application hangs and ends up logging this error.

Has anyone gone through this and have any idea what can be done?

You are describing a sound (resume?) failure as far as i can see from the vague information. Cant really say more than that. Does using a different emulator make any difference. I.e. is it device specific?

Hi Jayfella,

Sorry for the generic text.

These are reports that arrive via the Google Play Developer Console. These are reports that come directly from customers’ devices.

The data show that occurs for any type of device and version of android.

It caught my eye because reports are coming in too often.

So far usually occurred for calls:

alcDevicePauseSOFT
alcDeviceResumeSOFT
alcDestroyContext

Based on this data I formulated the test I described.

The test confirmed that the problem occurs intermittently after the game goes to the background in android.

1 Like

Isnt there some kind of boolean isResumeSupported method somewhere in the sound setup. I forget where. The console disays the result on game startup, too.