• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
Locked
0

Bug signal 11 (SIGSEGV), code 1 (SEGV_MAPERR) and Conflict trampoline

Explorer ,
Jun 05, 2017 Jun 05, 2017

Copy link to clipboard

Copied

Hello

I have a bug every time I upload a new app with Adobe air 25.0.0.126 that I need to fix. This is:

signal 11 (SIGSEGV), code 1 (SEGV_MAPERR)

art_quick_imt_conflict_trampoline

backtrace:

  native: pc 00000000000eae18 /system/lib/libart.so (art_quick_imt_conflict_trampoline+7)

  native: pc 0000000001fe8861 /system/framework/arm/boot.oat

I use animate and I need to find what cause this bug asap. Can anybody tell me how to solve that bug?

TOPICS
Performance issues

Views

3.6K

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Jun 05, 2017 Jun 05, 2017

Copy link to clipboard

Copied

Hi,

Could you please share a sample application probably a swf and xml file which reproduces this issue.

Thanks,

Ankit | Adobe AIR Engineering

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Jun 05, 2017 Jun 05, 2017

Copy link to clipboard

Copied

I sent you a private message with 2 screenshot, one .swf and one xml.

Get back to me asap please

Thank you

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Jun 06, 2017 Jun 06, 2017

Copy link to clipboard

Copied

Hi,

Could you please send us a dropbox link for the same. The link you shared is not opening in our network.

Thanks,

Ankit

Adobe AIR Engineering

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Jun 06, 2017 Jun 06, 2017

Copy link to clipboard

Copied

Sent via private message

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Jun 06, 2017 Jun 06, 2017

Copy link to clipboard

Copied

Hi,

We have tried reproducing the issue at our end but its not reproducible. Please try with our latest BETA.

App is showing black screen but no crash is observed.

Regards,

Adobe AIR Engineering

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Jun 06, 2017 Jun 06, 2017

Copy link to clipboard

Copied

Hello

I already did with AIR 26.0.0.112 and I saw the same crash over and over

I can show you several screenshot of apps where the crash increase when I use both version AIR 25 and AIR 26 if you want.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Jun 06, 2017 Jun 06, 2017

Copy link to clipboard

Copied

Hi,

Please share more information with us like the device you are using and the OS version and any other useful information to repro the issue at our end.

Regards,

Adobe AIR Engineering

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Jun 07, 2017 Jun 07, 2017

Copy link to clipboard

Copied

I don't see the error in my devices. I see those error in google play. Here are more details:


Example App #1
OS

Android 6.0    431Times    100.0%
Device
There is a huge list of devices

A76plus (A76Plus)

429.7%
MS40s (MS40S) 337.7%
Xolo era 2 (era_2) 317.2%
JS2 235.3%
AX820 (Bmobile_AX820) 214.9%
SUNNY (v2508) 173.9%
A71 (A71) 163.7%
Fly Stratus (Stratus_6) 153.5%
sp7731c_fs280_32v4 133.0%
c177_gal_241 133.0%
Aqua_Lions_4G (INTEX_AQUA_LIONS_4G) 122.8%
JERRY (v2806) 112.6%
tg65_k28 112.6%
L-EMENT505 102.3%
Q705EA 81.9%
i6 Metal One (i6_Metal_ONE_new) 71.6%
c177_ymt_216 71.6%
AX920 (Bmobile_AX920) 71.6%
Admire_Thrill 71.6%
AM508 71.6%
Others 12027.8%

Example App #2
OS
Android 6.0     139 Times   100.0%

Devices

Canvas Juice (A77)

3424.5%
Aqua_Lions_4G (INTEX_AQUA_LIONS_4G) 1611.5%
Xolo era 2 (era_2) 1510.8%
A76plus (A76Plus) 117.9%
i5.5 (i5_5) 75.0%
X32 (X32) 75.0%
INTEX AQUA AMAZE+ (INTEX_AQUA_AMAZE_PLUS) 53.6%
sp9832a_3h10_volte 42.9%
Galaxy J7(2016) (j7xelte) 42.9%
itel it1513 (itel_it1513) 42.9%
JERRY (v2806) 32.2%
X32 (X32_new) 32.2%
X11 (X11) 32.2%
Admire_Thrill 32.2%
eraX 21.4%
SYMPHONY V75 (V75) 21.4%
Stellar Mi-438 (Spice) 21.4%
Q705EA 21.4%
Q351 21.4%
Me_1 21.4%
Others 85.8%

Example App 3​

OS
Android 6.0     787    100.0%

Devices

A76plus (A76Plus)

7910.0%
tg61_S4015A_Swipe 546.9%
Xolo era 2 (era_2) 536.7%
X32 (X32) 516.5%
Aqua_Lions_4G (INTEX_AQUA_LIONS_4G) 455.7%
Fly Stratus (Stratus_6) 283.6%
L-EMENT_403 283.6%
Era 4G (era_4G) 273.4%
JERRY (v2806) 263.3%
sp7731c_1h10 243.0%
c177_gal_241 192.4%
c178_hwf_261 182.3%
SUNNY (v2508) 162.0%
iris870 (iris870) 162.0%
L-EMENT505 162.0%
JS2 162.0%
sp9832a_3h10_volte 151.9%
SUNNY (V2508AN01D) 141.8%
i5.5 (i5_5) 131.7%
MS40s (MS40S) 131.7%
Others 21627.4%

It look like it affect Android 6.0 with many many devices.

I can't reproduce the error in my devices but I see a lot of reports about them via google play.

If you want more details with screenshots, I can send you via private message.

Waiting for your answer

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Jun 08, 2017 Jun 08, 2017

Copy link to clipboard

Copied

Hi,

We have tried to reproduce the issue at our end on all the devices of Android 6.0 but unfortunately no success. To successfully investigate the issue we need a sample project which reproduces this issue.

Thanks,

Ankit | Adobe AIR Engineering

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Jun 08, 2017 Jun 08, 2017

Copy link to clipboard

Copied

I sent you a private message with a complete game to test on your side.

Keep me updated.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Jun 09, 2017 Jun 09, 2017

Copy link to clipboard

Copied

Thanks. We will investigate and let you know.

-Ankit

Adobe AIR Engineering

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Jun 13, 2017 Jun 13, 2017

Copy link to clipboard

Copied

Hi,

We have investigated the project shared by you on popular Android 6 devices available with us that includes Nexus devices, Samsung devices and HTC. Issue is still not reproducible.

Thanks,

Ankit  | Adobe AIR Engineering

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Jun 15, 2017 Jun 15, 2017

Copy link to clipboard

Copied

Hello Ankit

Well if you don't use the devices in the list you will not not see the problem I guess.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jun 19, 2017 Jun 19, 2017

Copy link to clipboard

Copied

Had this problem as well. You should try downgrading to AIR 23.

We had this issue mainly with LG devices like "LG G Pad F 8.0"

Hope it helps

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Jun 19, 2017 Jun 19, 2017

Copy link to clipboard

Copied

AlexXev this is not a solution as we will need to update for recent adobe air in the futur. We can't stay at 23 forever. What are we going to do when google play will ask us to upgrade for a new openssl version? We need to solve this issue.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Jun 16, 2017 Jun 16, 2017

Copy link to clipboard

Copied

I have a strong suspicion this is related to the recently added multidex support.  Would it be possible to add a flag for AIR to optionally disable multidex?

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Jun 20, 2017 Jun 20, 2017

Copy link to clipboard

Copied

Hi,

This cant be related to Multidex as this feature introduced in AIR 25 and users are reporting this issue in AIR 24 as well.

Thanks,

Ankit

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Advocate ,
Aug 10, 2017 Aug 10, 2017

Copy link to clipboard

Copied

Hello,

we just set our app live with Air 25 and we are seeing the error stacking up. Unfortunately there is no way to roll back now because we upgraded to the latest Android SDK 23 and can't undo that. Have you been able to identify and fix the problem?

We are not using Milkman Ads ANE but some other ANEs, some of them produced by Milkman.

Thanks in advance

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Advocate ,
Aug 14, 2017 Aug 14, 2017

Copy link to clipboard

Copied

Hello,

the problem persists in Air 27 Beta. Is there anything we can do to help identifying the issue? Building a sample project will not be possible because we are unable to reproduce the problem locally. However I would be happy to send stats or give device information.

Kind regards,

Ruben

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Participant ,
Jun 20, 2017 Jun 20, 2017

Copy link to clipboard

Copied

We noticed the same issue here as soon as we moved to  Air 24 and above Google Play reported many crashes on Android 6 only. Unfortunately we had to roll back to Air 22. We tested each of the native extension we use and found that milkman admob native extension is responsible. We must find out a way to fix that bug otherwise Google Play penalizes apps with too many crashes.

trampoline-crash(1).png

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Oct 27, 2017 Oct 27, 2017

Copy link to clipboard

Copied

I got the same problem and i need to find a solution. Anybody found a way to fix this ? It hurt my rating on android.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Apr 30, 2018 Apr 30, 2018

Copy link to clipboard

Copied

LATEST

Hi.
I also have the same problem but I am using Cocos2dx.
All the crashes are on Android 6.x (as mentioned above).

The most affected device is Bmobile AX680 (about 45% of the crashes are on this device).

Here is what I found:
https://forums.coronalabs.com/topic/71862-signal-11-sigsegv-code-1-segv-maperr-art-quick-imt-conflic...

Seems something is related with Vungle sdk initialization.

On my side Fabric logs show that Vungle initialization is started but not finished before the crash.

Also in the above link they said some fix is already done in the latest Vungle.

I hadn't update the Vungle yet so I am not sure it helps.

I hope it will help.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines