Getting SIGABRT 6 in Android when running http calls in parallel

[jassmith]

From @tsequeira-vhs on July 27, 2018 14:32

Description

We have a Xamarin.Forms app which is crashing with 'signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr -------- java_vm_ext.cc:534] JNI DETECTED ERROR IN APPLICATION: use of deleted global reference 0x3ce2'

We are running multiple calls to web services with HttpClient in parallel using Task.WhenAll()

The crash is random and due to this we are unable to identify the root cause.

Steps to Reproduce

1. Login (first time)
2. Set pin code (first time)
3. Enter pin code (from second time)
4. Launches a page with blue header
5. If no crash, kill the app and repeat steps from 3.

Note: To make the crash more frequent enable gref logging using the following ADB command: 'adb shell setprop debug.mono.log gref'

Expected Behavior

The app should not crash

Actual Behavior

App crashes with 'java_vm_ext.cc:534] JNI DETECTED ERROR IN APPLICATION: use of deleted global reference 0x3ce2'

Basic Information

• Version with issue:
• Last known good version:
• IDE: Visual Studio 2017 Enterprise
• Platform Target Frameworks:
  • Android: 8.1
• Android Support Library Version: API 27
• Affected Devices: Tested on Pixel 2 and Samsung S8

Logs

ReportLog-1.txt
ReportLog-2.txt

Copied from original issue: xamarin/Xamarin.Forms#3421

[jassmith]

From @tsequeira-vhs on July 27, 2018 14:43

We have attached stripped down version of the code.
EngageDummy.zip

[tsequeira-vhs]

Any update on the issue?

[elacca]

I had the same issue. At my case the problem was coming from the SecureStorage, which I was accessing async to get a Token from it, before each HTTP request. After eliminating this part, the parallel HTTP calls are working flawlessly.

[ghost]

We suspect this issue is stale and no longer relevant. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will undo this process.

[ghost]

This issue will now be closed since it had been marked possibly-stale but received no further activity in the past 14 days. It is still possible to reopen or comment on the issue, but please note that the issue will be locked if it remains inactive for another 30 days.