Skip to content
This repository has been archived by the owner on Dec 22, 2023. It is now read-only.

App crash #4

Open
artkhromov opened this issue Apr 1, 2014 · 4 comments
Open

App crash #4

artkhromov opened this issue Apr 1, 2014 · 4 comments

Comments

@artkhromov
Copy link

I use your ane to open .jpg or .ig (for Instagram) pictures and everything works great when the file is opened for the first time.

Later on, if the filepath changes, subsequent call of context.call("openWith",filePath,basePath) makes app crash without any notification, event or error message. If filepath stays the same, everything works as expected.

I've tried to wrap it into try-catch block, but haven't got any other result.

UPDATE:
I'm using AIR 3.9 and iOS 7.1 (with IOKit framework fix from issue #2 )

@katopz
Copy link
Owner

katopz commented Apr 1, 2014

Thanks for report, Can you access to your device log and paste crash related here please?

@artkhromov
Copy link
Author

I'm not sure, that it is what you have asked for, but:

Date/Time: 2014-04-02 13:45:28.393 +0700
OS Version: iOS 7.1 (11D167)
Report Version: 104

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Triggered by Thread: 0

Last Exception Backtrace:
(0x30dafefe 0x3b544ce2 0x30dafe40 0x31723d14 0x31723c9a 0xfd51e8 0xdd01f0 0x447914 0xb195e0 0x4a64d0 0x6e448 0x4d1bf4 0x4d5de0 0x4d5fcc 0xae4704 0xae1dfc 0xae1aec 0x6e448 0x5e3dec 0x5e42bc 0x5e3b64 0x54a008 0x549a94 0x5c898c 0xc81774 0xc81138 0xc80410 0x3a852c 0xb07940 0xb1fb28 0x6e448 0x5e3dec 0x5e42bc 0x5e3b64 0x55dafc 0x549a94 0x5c898c 0xc81774 0xc81138 0xc80e10 0xc84268 0xd27834 0xd287a4 0xf9c33c 0xf9c190 0xb863bc 0x31798c1e 0x30d7afe2 0x30d7a4aa 0x30d78c9a 0x30ce37a4 0x30ce3586 0x35c506ce 0x3364288c 0xba3320 0xfd3ff8)

Thread 0 Crashed:
0 libsystem_kernel.dylib 0x3baf91f0 0x3bae6000 + 78320
1 libsystem_pthread.dylib 0x3bb617b2 0x3bb5e000 + 14258
2 libsystem_c.dylib 0x3baa9ff4 0x3ba60000 + 303092
3 libc++abi.dylib 0x3aef898a 0x3aef8000 + 2442
4 libc++abi.dylib 0x3af116e2 0x3aef8000 + 104162
5 libobjc.A.dylib 0x3b544f7a 0x3b541000 + 16250
6 libc++abi.dylib 0x3af0f1b0 0x3aef8000 + 94640
7 libc++abi.dylib 0x3af0ed12 0x3aef8000 + 93458
8 libobjc.A.dylib 0x3b544e2a 0x3b541000 + 15914
9 CoreFoundation 0x30ce381a 0x30cdb000 + 34842
10 CoreFoundation 0x30ce3586 0x30cdb000 + 34182
11 GraphicsServices 0x35c506ce 0x35c47000 + 38606
12 UIKit 0x3364288c 0x335d4000 + 452748
13 GreatPeoplePhrases 0x00ba3320 0x6c000 + 11760416
14 GreatPeoplePhrases 0x00fd3ff8 0x6c000 + 16154616

@katopz
Copy link
Owner

katopz commented Apr 2, 2014

yes it is, if you clear log -> try crash -> grab log, it should be right.

far as i know it could be memory management, it would be safer to rewrite as ARC and recompile with present SDK

i will take a look when i've some free time or when i need this again

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants
@katopz @artkhromov and others