Android version crashes with Fatal signal 11 (SIGSEGV) when app started from notification (2)

SimplesApps

I have the same crash noted next with the last version of my Action Basket game for Android:

http://giderosmobile.com/forum/discussion/3884/android-version-crashes-with-fatal-signal-11-sigsegv-when-app-started-from-notification

In fact I was googling the error and I've found that post of our lovely Gideros forum.

@ar2rsawseen I guess you can find the solution.

But as I can read for @Jeff_Kanazi the problem was solved with an updated of the Notification plugin you did.

I'm using last version (1.4) of Notification plugin but the problem it's the same that explained here.

Please, could you check the last changes of the plugin in order to know if maybe there is some bug?

For my app the crash goes with the following error:
"libc(20400): Fatal signal 11 (SIGSEGV) at 0x00000007 (code=1), thread 20426 (Thread-7592)"

If you need more details or the complete log, please let me know.

Btw, I wrote another discussion related the Notification plugin here:
http://giderosmobile.com/forum/discussion/5549/list-of-local-notifications-empty-other-notification-plugin-issues#Item_1

Could somebody find what could be the solution to this problem?

Thanks for your help!

SimplesApps

@ar2rsawseen Could you check it?

Many thanks.

ar2rsawseen

Hello @SimplesApps
sorry been doing lots of work on the core lately.

yeah the Notifications plugin was one of the most complex ones

so you experience same crash (with libgideros.so (gevent::EventManager::tick())?)
and under same circumstances (when app was closed by application:exit())?

SimplesApps

Thanks @ar2rsawseen

You can check by yourself If after you play my app "Action Basket" you click on the notification (it will appear one or three days after you play last time).

The crash is generated when the user clicks on the notification.
The notification tries to open the app and then it crashes...

It gives a bad feeling to the user when he wants to play motivated by a notification and finally receives a crash.

This is the backtrace of the stack:

#00 pc 00005248 /data/app-lib/com.simplesapps.actionbasket-1/liblua.so
#01 pc 00006a30 /data/app-lib/com.simplesapps.actionbasket-1/liblua.so
#02 pc 00006ad4 /data/app-lib/com.simplesapps.actionbasket-1/liblua.so (lua_rawget+24)
#03 pc 00007be8 /data/app-lib/com.simplesapps.actionbasket-1/libnotification.so (NotificationManager::dispatchEvent(int, void*)+72)
#04 pc 00066341 /data/app-lib/com.simplesapps.actionbasket-1/libgideros.so (gevent_CallbackList::dispatchEvent(int, void*)+136)
#05 pc 000663ff /data/app-lib/com.simplesapps.actionbasket-1/libgideros.so (gevent::EventManager::tick()+90)

Thanks again.

SimplesApps

Hi,

I checked the Notification plugin and the above issue remains the same.
I think this is an important bug to fix.

Does anyone have checked it ?

Thanks!

ChrisF

Do you have a github bug raised? , I was planning on using notifications as well as I have found they are vital to driving revenue

SimplesApps

@ChrisF , no I don't.

ar2rsawseen

Interesting,
just recently I seemed to fix a bug in Android notification (some other bug)
and no one seemed to experience this bug.

Does it happen on app cold start? Or when app is already in background?