Asset Bundle Crashes on iOS (AssetBundleLoadFromFileAsync)

Unity Engine
,
1

Hey,

We’re seeing many of these crashes on iOS. We are on Unity 5.3.4p1.

Is anyone familiar with these?

2

Could you please submit a bug report and attach a small reproduction project? Could you post the id of the new bug here? Thanks.

3

Unfortunately, i don’t have a repro project.
We have an automated crash reporting service, and already there are over 200 of these crashes. They occur in the product (store) version of our game. I don’t have any more information to provide at the moment.

Would you still like this bug to be reported? what information should i add to the bug report ?

4

Unfortunately not having a repro project is almost a guaranteed dead end for all but the most simple bugs. If the bug can be easily reproduced, then you could try to strip unrelated assets by trial and error and then submit the project when it’s sufficiently small. Otherwise, just post the updates here, maybe someone who has more reproducible project will chime in.

5

Isn’t is possible to see the exact line that caused the crash for a particular version?

e.g: this happens on 5.3.4p1, what happens in this particular line:
0 coinmaster FileSystemEntry::Set(char const*) (in coinmaster) (VirtualFileSystem.cpp:389)

6

Same issue we are getting, any info on this?

7

excellent site

8

Hi,

We have 2 similar (VirtualFileSystem.cpp) crashes in all of our iOS games as well; Bee Brilliant, Disco Ducks and Cookie Cats:

1) FileSystem::ToAbsolute(char const*) const (VirtualFileSystem.cpp:264):

Thread 24 Crashed:
0 BeeBrilliant 0x00000001009f58c0 FileSystem::ToAbsolute(char const*) const (VirtualFileSystem.cpp:264)
1 BeeBrilliant 0x0000000100a08194 IsDirectoryCreated(std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator > const&) (FileVFS.cpp:18)
2 BeeBrilliant 0x000000010095b950 Cache::ReadCacheIndexThreaded(void*) (CachingManager.cpp:486)
3 BeeBrilliant 0x00000001009f406c Thread::RunThreadWrapper(void*) (Thread.cpp:40)
4 libsystem_pthread.dylib 0x0000000193317860 _pthread_body + 236
5 libsystem_pthread.dylib 0x0000000193317770 _pthread_start + 280
6 libsystem_pthread.dylib 0x0000000193314dbc thread_start + 0

2) FileSystemEntry::Set(char const*) (VirtualFileSystem.cpp:101)

Thread 25 Crashed:
0 BeeBrilliant 0x0000000100a41c54 FileSystemEntry::Set(char const*) (VirtualFileSystem.cpp:101)
1 BeeBrilliant 0x0000000100a41b9c FileSystemEntry::FileSystemEntry(char const*) (VirtualFileSystem.cpp:371)
2 BeeBrilliant 0x0000000100a544e0 ReadStringFromFile(std::__1::basic_string<char, std::__1::char_traits, stl_allocator<char, (MemLabelIdentifier)1, 16> >, std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator > const&) (FileVFS.cpp:92)
3 BeeBrilliant 0x00000001009a7354 CachingManager::ReadInfoFile(std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator > const&, long, std::__1::vector<std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator >, std::__1::allocator<std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator > > >) (CachingManager.cpp:759)
4 BeeBrilliant 0x00000001009a7120 Cache::AddToCache(std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator > const&, int) (CachingManager.cpp:346)
5 BeeBrilliant 0x00000001009a796c Cache::ReadCacheIndexThreaded(void) (CachingManager.cpp:487)
6 BeeBrilliant 0x0000000100a4006c Thread::RunThreadWrapper(void*) (Thread.cpp:40)
7 libsystem_pthread.dylib 0x000000018f1d7860 _pthread_body + 236
8 libsystem_pthread.dylib 0x000000018f1d7770 _pthread_start + 280
9 libsystem_pthread.dylib 0x000000018f1d4dbc thread_start + 0

We started seeing the crash after we upgraded from Unity 4 to Unity 5. The crashes above are from a 5.3.5f1 build of Bee Brilliant.

We are also unable to reproduce the crash, but the crashlogs give you the file and line number of the crash, so it should be worthwhile to have an engineer spend an hour looking at that code to see if there are any obvious problems in that section of the code; sometimes you spot things that are otherwise overlooked when you know for a fact that a line of code has a problem.

Best regards,
Morten Nielsen

1 Like
9

p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; line-height: 17.0px; font: 14.7px Helvetica; color: #333333; -webkit-text-stroke: #333333; min-height: 17.0px} p.p2 {margin: 0.0px 0.0px 0.0px 0.0px; line-height: 17.0px; font: 14.7px Helvetica; color: #333333; -webkit-text-stroke: #333333; background-color: #ffffff; min-height: 17.0px} p.p3 {margin: 0.0px 0.0px 0.0px 0.0px; line-height: 17.0px; font: 14.7px Helvetica; color: #333333; -webkit-text-stroke: #333333; background-color: #ffffff} span.s1 {font-kerning: none}

#0 Thread

SIGSEGV

SEGV_ACCERR

0??? 000000000000000000+0

1xjws Set (VirtualFileSystem.cpp:101)

2xjws FileSystemEntry (VirtualFileSystem.cpp:372)

3xjws Delete (VirtualFileSystem.cpp:693)

4xjws ~AssetBundleLoadFromAsyncOperation (AssetBundleLoadFromAsyncOperation.cpp:53)

5xjws ~AssetBundleLoadFromStreamAsyncOperation (AssetBundleLoadFromStreamAsyncOperation.cpp:29)

6xjws ~UnityWebStream (UnityWebStream.cpp:158)

7xjws Release (UnityWebStream.cpp:152)

8xjws CleanupUnityWebStreams (LinkedList.h:26)

9xjws ExecuteCleanup (RegisterRuntimeInitializeAndCleanup.cpp:69)

10xjws RuntimeCleanup (Player.cpp:1073)

11xjws -[UnityAppController applicationWillTerminate:] (UnityAppController.mm:351)

12UIKit -[UIApplication _terminateWithStatus:]+280

13UIKit ___102-[UIApplication _handleApplicationDeactivationWithScene:shouldForceExit:transitionContext:completion:]_block_invoke2017+796

14UIKit __runAfterCACommitDeferredBlocks+292

15UIKit __cleanUpAfterCAFlushAndRunDeferredBlocks+92

16UIKit __afterCACommitHandler+96

17CoreFoundation _CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION+32

18CoreFoundation ___CFRunLoopDoObservers+372

19CoreFoundation ___CFRunLoopRun+928

20CoreFoundation CFRunLoopRunSpecific+384

21GraphicsServices GSEventRunModal+180

22UIKit UIApplicationMain+204

23xjws main (main.mm:32)

24libdyld.dylib _start+4

10

Even we are facing similar issue on ios after updating to unity5.3.6p8

11

Any Update on this issue ??

12

any update? exactly the same crash occurred on ios

13

5.3.7p4 we’ve seen a lot of crash report like this, and all that happen in background