Skip to main content
E
ernie_95126
Participating Frequently
March 28, 2015
Question

IOS SIGSEGV crash in 17.0.0.124

  • March 28, 2015
  • 3 replies
  • 1692 views

I'm getting this crash with 124 (and I don't think it ever happened with 123, but I may just have been passing in different parameters).  Anybody know whats going on?

Incident Identifier: 18A41DC7-6FA7-4E34-B1C8-21B893F302C9

CrashReporter Key:   cb0bd8f3a81ba9c63cd6bf651670c06577034811

Hardware Model:      iPad3,1

Process:             Writing [2649]

Path:                /private/var/mobile/Containers/Bundle/Application/17F541DB-06B1-40FF-A0A8-1A57F1B4DE37/Writing.app/Writing

Identifier:          com.toolwire.WritingILUs

Version:             1.0.0 (1.0)

Code Type:           ARM (Native)

Parent Process:      launchd [1]

Date/Time:           2015-03-26 09:58:42.769 -0700

Launch Time:         2015-03-26 09:51:13.567 -0700

OS Version:          iOS 8.1.3 (12B466)

Report Version:      105

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)

Exception Subtype: KERN_INVALID_ADDRESS at 0x0000003c

Triggered by Thread:  0

Thread 0 name:  Dispatch queue: com.apple.main-thread

Thread 0 Crashed:

0   Writing                           0x02016916 0x4e000 + 33327382

1   Writing                           0x0146580c 0x4e000 + 21067788

2   Writing                           0x0146580c 0x4e000 + 21067788

3   Writing                           0x0146a63c 0x4e000 + 21087804

4   Writing                           0x01feec4c 0x4e000 + 33164364

5   Writing                           0x02003aaa 0x4e000 + 33249962

6   Writing                           0x01fc4654 0x4e000 + 32990804

7   Writing                           0x01499794 0x4e000 + 21280660

8   Writing                           0x014982b0 0x4e000 + 21275312

9   Writing                           0x01feec4c 0x4e000 + 33164364

10  Writing                           0x02003d06 0x4e000 + 33250566

11  Writing                           0x02003aaa 0x4e000 + 33249962

12  Writing                           0x01d0ff30 0x4e000 + 30154544

13  Writing                           0x01d0f58c 0x4e000 + 30152076

14  Writing                           0x01d1263c 0x4e000 + 30164540

15  Writing                           0x01b1bd48 0x4e000 + 28106056

16  Writing                           0x01feec4c 0x4e000 + 33164364

17  Writing                           0x02003d06 0x4e000 + 33250566

18  Writing                           0x02003aaa 0x4e000 + 33249962

19  Writing                           0x01dd9114 0x4e000 + 30978324

20  Writing                           0x01c6e944 0x4e000 + 29493572

21  Writing                           0x01c6a9f4 0x4e000 + 29477364

22  Writing                           0x01c6f004 0x4e000 + 29495300

23  Writing                           0x01bffcc8 0x4e000 + 29039816

24  Writing                           0x01c007f0 0x4e000 + 29042672

25  Writing                           0x01b35220 0x4e000 + 28209696

26  QuartzCore                        0x26a79ae6 0x26a1f000 + 371430

27  QuartzCore                        0x26a7994e 0x26a1f000 + 371022

28  IOMobileFramebuffer               0x2b33182c 0x2b32c000 + 22572

29  IOKit                             0x24a881ea 0x24a84000 + 16874

30  CoreFoundation                    0x23b143a2 0x23a56000 + 779170

31  CoreFoundation                    0x23b247f0 0x23a56000 + 845808

32  CoreFoundation                    0x23b2478a 0x23a56000 + 845706

33  CoreFoundation                    0x23b22dac 0x23a56000 + 839084

34  CoreFoundation                    0x23a6fb2c 0x23a56000 + 105260

35  CoreFoundation                    0x23a6f93e 0x23a56000 + 104766

36  GraphicsServices                  0x2ae2404c 0x2ae1b000 + 36940

37  UIKit                             0x27061f1c 0x26ff4000 + 450332

38  Writing                           0x01c2b244 0x4e000 + 29217348

39  Writing                           0x02095610 0x4e000 + 33846800

.... lots of other stuff

This topic has been closed for replies.

3 replies

jindal_nipun
jindal_nipun
Participating Frequently
May 12, 2015

Boolean issue should be fixed with the current Beta. Can you please check.

Regards,

Nipun

E
ernie_95126Author
Participating Frequently
April 8, 2015

I actually seem to have a different problem from the coercion problem.  I have traced the code to this statement:

var questions:Vector.<MCQuestion> = new Vector.<MCQuestion>;

The execution does get to the global$init code in MCQuestion class, presumably to get the size of the instance.   The interesting thing is that the MCQuestion class has this declaration:

private var _choices:Vector.<MCChoice>

It crashes before getting to the global$init code in the MCChoice  class.  So I think my problem is setting up a Vector containing a class that itself contains a Vector.

I
InDev
Participant
May 4, 2015

Could it be related to this?

Bug#3979394 - iOS 64-bit Segmentation fault

J
joulupuqqi
Participant
April 2, 2015

My device logs are full of this too. I was able to pinpoint the bug to getting and setting booleans through interfaces.

Here's a sample app which fails on every run:

https://www.dropbox.com/s/1onrm3kdwaxczwq/src.zip?dl=0

Notes:

- App fails only in debug mode

- App works fine with fast packaging

- Variable test has to be of type ITest. Using type Test works fine.

- First getBool() returns correct value (true)

- false is passed to setBool(), but if you put a break point into setBool() you'll see that it gets a true as parameter.

- Second getBool() either crashes the app, or gets traced as "(null)"

Setup:

AIR SDK 17.0.0.124

iOS 8.2

iPhone 5

G
Greg Dove
Inspiring
April 5, 2015

I have also encountered this issue with booleans in a project. I am currently trying to find which AIR revision it occurred in.

I didn't try that minimal repro test, but the circumstances are identical to what I have encountered in my code. I was able to get something that corrected the issues in the places I was using it in, with something similar to :

var value:Boolean = !Boolean(test.getBool());

It seems that the coercion is not working correctly when accessing a boolean value via an interface and it requires an explicit cast. This is using the flex compiler, just in case that is different here to the ASC 2.0 compiler.

This is quite a nasty bug.

joulupuqqi‌ could you please log a bug in the bugbase, with your minimal repro code : Adobe Bugbase

if you do I will vote it up immediately!

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices