You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since we updated our app from Xamarin android to .NET MAUI android, we started to have a crash Bridge SCC at index must NOT be alive coming from:
xamarin-android/src/monodroid/jni/osbridge.cc:963 (gc_cleanup_after_java_collection)
when our app opens a third party scanning camera, Scandit.
Looks like this happens when the camera opens and our app goes in background and garbage collection runs.
Always this GC log can be seen before the crash. zygote64: Explicit concurrent copying GC freed 44801(2MB) AllocSpace objects, 53(9MB) LOS objects, 58% free, 8MB/20MB, paused 96us total 41.578ms
We have reported this to Scandit, but I wonder whether we can get some input from you.
Hi I'm an AI powered bot that finds similar issues based off the issue title.
Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!
Description
Since we updated our app from Xamarin android to .NET MAUI android, we started to have a crash Bridge SCC at index must NOT be alive coming from:
xamarin-android/src/monodroid/jni/osbridge.cc:963 (gc_cleanup_after_java_collection)
when our app opens a third party scanning camera, Scandit.
Looks like this happens when the camera opens and our app goes in background and garbage collection runs.
Always this GC log can be seen before the crash.
zygote64: Explicit concurrent copying GC freed 44801(2MB) AllocSpace objects, 53(9MB) LOS objects, 58% free, 8MB/20MB, paused 96us total 41.578ms
We have reported this to Scandit, but I wonder whether we can get some input from you.
Steps to Reproduce
this
Link to public reproduction project repository
No response
Version with bug
8.0.40 SR5
Is this a regression from previous behavior?
No, this is something new
Last version that worked well
Unknown/Other
Affected platforms
Android
Affected platform versions
Android 14, 13, 12,11,10 and 9.
Did you find any workaround?
Not a workaround but this does not happen with our Xamarin app.
Relevant log output
No response
The text was updated successfully, but these errors were encountered: