Mosaic crash after few seconds

Are you up to date on iOS 14.4 by the way? If not, try upgrading to that as a first step to tracking down the issue.

Also, iOS might be capturing your crashes in it’s Analytics dump. When Mosaic next crashes on your iPhone/iPad, from iOS’ Settings, go to [Privacy] → [Analytics & Improvements] → [Analytics Data], and from the search bar up top, type in the date of your crash in YYYY-MM-DD format (e.g. “2021-02-08”) and see what turns up. That file might be handy for dCS to track down any potential issue Mosaic might have.

By the way, what language is your iPhone/iPad set to if you don’t mind my asking? :slightly_smiling_face:

Ok I’ll try to do what you have suggested.
I am italian.

The reason I ask is because there have been sporadic reports of iOS App crashes in some language settings but not others.

Coincidentally, a year ago iOS had a bug which caused it to crash when displaying an Italian flag and Sindhi text! (I know, sounds totally crazy! :grin:)

Hi Anup!
No problem with your question about language!
I have the file you requested but the platform here tells me that the file is not authorized
because of the extension. How I can manage this thing?

Hey Stefano, those Analytics dumps are usually plain text files that you should be able to view from the iPhone itself. Note: As it usually contains private information, be careful not to send it out to anyone randomly :grin:, best to scan through it yourself for clues as to whats causing Mosaic to crash.

Here’s an example of a crash log that iOS generates on its own (a simulated crash log). The top area will usually show whats causing the App to crash, I’ve highlighted in red, see if you can find some clues in your crash logs.

Hi Anupc.
No Problem! I don’t have nothing to hide :slight_smile:
But I have some problem to send the content to you

xception Type: EXC_CRASH (SIGKILL)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Termination Reason: Namespace RUNNINGBOARD, Code 0xdead10cc
Triggered by Thread: 0

Thread 0 name: Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0 libsystem_kernel.dylib 0x00000001d66f9644 0x1d66f5000 + 17988
1 libsystem_kernel.dylib 0x00000001d66f8a48 0x1d66f5000 + 14920
2 CoreFoundation 0x00000001aa7c50fc 0x1aa72b000 + 631036
3 CoreFoundation 0x00000001aa7bf570 0x1aa72b000 + 607600
4 CoreFoundation 0x00000001aa7beba0 0x1aa72b000 + 605088
5 Foundation 0x00000001ab9de7f8 0x1ab9d7000 + 30712
6 Foundation 0x00000001aba0f964 0x1ab9d7000 + 231780
7 libxpc.dylib 0x00000001f2fa41c4 0x1f2f8f000 + 86468
8 libxpc.dylib 0x00000001f2fa63bc 0x1f2f8f000 + 95164
9 WebKit 0x00000001b662db80 0x1b64a8000 + 1596288
10 libdyld.dylib 0x00000001aa49d568 0x1aa49c000 + 5480

Thread 1:
0 libsystem_pthread.dylib 0x00000001f2f7e86c 0x1f2f70000 + 59500

Thread 2:
0 libsystem_pthread.dylib 0x00000001f2f7e86c 0x1f2f70000 + 59500

Thread 3 name: JavaScriptCore bmalloc scavenger
Thread 3:
0 libsystem_kernel.dylib 0x00000001d671c61c 0x1d66f5000 + 161308
1 libsystem_pthread.dylib 0x00000001f2f76c54 0x1f2f70000 + 27732
2 libc++.1.dylib 0x00000001bec4ae0c 0x1bec3e000 + 52748
3 JavaScriptCore 0x00000001b43b4b54 0x1b3586000 + 14871380
4 JavaScriptCore 0x00000001b43b9584 0x1b3586000 + 14890372
5 JavaScriptCore 0x00000001b43b8f98 0x1b3586000 + 14888856
6 JavaScriptCore 0x00000001b43ba6c0 0x1b3586000 + 14894784
7 libsystem_pthread.dylib 0x00000001f2f79b3c 0x1f2f70000 + 39740
8 libsystem_pthread.dylib 0x00000001f2f7e880 0x1f2f70000 + 59520

Thread 4 name: Dispatch queue: WebResourceLoadStatisticsStore Process Data Queue
Thread 4:
0 libsystem_kernel.dylib 0x00000001d671b6a0 0x1d66f5000 + 157344
1 libsystem_kernel.dylib 0x00000001d66fd974 0x1d66f5000 + 35188
2 libsqlite3.dylib 0x00000001c38a5b30 0x1c383a000 + 441136
3 libsqlite3.dylib 0x00000001c38bb3dc 0x1c383a000 + 529372
4 libsqlite3.dylib 0x00000001c38d8d54 0x1c383a000 + 650580
5 libsqlite3.dylib 0x00000001c387ca28 0x1c383a000 + 272936
6 libsqlite3.dylib 0x00000001c387a4f0 0x1c383a000 + 263408
7 WebCore 0x00000001b8894a60 0x1b6e5a000 + 27503200
8 WebKit 0x00000001b66126a4 0x1b64a8000 + 1484452
9 WebKit 0x00000001b6611074 0x1b64a8000 + 1478772
10 WebKit 0x00000001b6647074 0x1b64a8000 + 1699956
11 libdispatch.dylib 0x00000001aa47d298 0x1aa41d000 + 393880
12 libdispatch.dylib 0x00000001aa47e280 0x1aa41d000 + 397952
13 libdispatch.dylib 0x00000001aa45a4f0 0x1aa41d000 + 251120
14 libdispatch.dylib 0x00000001aa45afdc 0x1aa41d000 + 253916
15 libdispatch.dylib 0x00000001aa464800 0x1aa41d000 + 292864
16 libsystem_pthread.dylib 0x00000001f2f7b5a4 0x1f2f70000 + 46500
17 libsystem_pthread.dylib 0x00000001f2f7e874 0x1f2f70000 + 59508

Thread 5:
0 libsystem_pthread.dylib 0x00000001f2f7e86c 0x1f2f70000 + 59500

Thread 6:
0 libsystem_pthread.dylib 0x00000001f2f7e86c 0x1f2f70000 + 59500

Thread 7 name: com.apple.WebKit.IndexedDBServer
Thread 7:
0 libsystem_kernel.dylib 0x00000001d671c61c 0x1d66f5000 + 161308
1 libsystem_pthread.dylib 0x00000001f2f76c54 0x1f2f70000 + 27732
2 JavaScriptCore 0x00000001b434349c 0x1b3586000 + 14406812
3 JavaScriptCore 0x00000001b3c3b078 0x1b3586000 + 7032952
4 JavaScriptCore 0x00000001b431a408 0x1b3586000 + 14238728
5 JavaScriptCore 0x00000001b43669f0 0x1b3586000 + 14551536
6 JavaScriptCore 0x00000001b43696c8 0x1b3586000 + 14563016
7 libsystem_pthread.dylib 0x00000001f2f79b3c 0x1f2f70000 + 39740
8 libsystem_pthread.dylib 0x00000001f2f7e880 0x1f2f70000 + 59520

Thread 0 crashed with ARM Thread State (64-bit):
x0: 0x0000000010004005 x1: 0x0000000007000806 x2: 0x0000000000000000 x3: 0x0000000000000c00
x4: 0x0000000000000c03 x5: 0x00000000ffffffff x6: 0x0000000000000000 x7: 0x0000000100608570
x8: 0x00000000fffffbbf x9: 0x0000000007000906 x10: 0xd1be7db58b3e00b4 x11: 0x000000b2efe05c2e
x12: 0x00000000016e3600 x13: 0x0000000000140050 x14: 0x0000000000000100 x15: 0x0000010000000000
x16: 0xffffffffffffffe1 x17: 0x0000000000000001 x18: 0x0000000000000000 x19: 0x0000000000000000
x20: 0x00000000ffffffff x21: 0x0000000000000c03 x22: 0x0000000000000c00 x23: 0x000000016fb2abc0
x24: 0x0000000007000806 x25: 0x0000000000000000 x26: 0x0000000007000806 x27: 0x0000000000000c03
x28: 0x000000016fb2ab48 fp: 0x000000016fb2aa50 lr: 0x00000001d66f8a48
sp: 0x000000016fb2aa00 pc: 0x00000001d66f9644 cpsr: 0x60000000
esr: 0x56000080 Address size fault

The exception notification suggests the App was killed by the iOS watchdog process due to the App being “unresponsive”. One of the primary reasons for an App being unresponsive is synchronous networking related, so, if this is the log from Mosaic crashing, looks like it might actually be networking related after all (as Pete and Carsten suggested!! :wink:)

Stefano, I’ll take a closer look at your FRITZ!Box 7330 to see if theres any clues. I wonder whats changed (besides iOS?) from when Mosaic was working just fine for you :thinking:. Do you have any other WiFi access points you can try with by any chance?

Thanks Anupc.
I am sure.
Nothing is changed in os and even in my network. I remember that I was using the app on my sofà listening music. I remember that for several minutes all was ok. Sometime I switched from Roon to Mosaic and vice versa.
It was when I switched to Mosaic from Roon that I have seen Mosaic freeze and than suddenly shutting off. Since that Moment The problem has remains. No I don’t have any other access point.

Stefano:

As at this point we seem to be suspecting some kind of network issue I am wondering if the Roon/Mosaic switch just happened to occur coincidentally with some other change taking place which was perhaps invisible to you.

For example, AVM installs updates to Fritz!box from time to time and the change is not necessarily visible to the user unless you interrogate the firmware. Could this have happened and have changed a network setting causing your issue?

Anup:

Would it help if Stefano posted ( or PM’d to you) some screenshots of the Fritz!box network settings?

I‘m not sure as not being an expert, but could it be related to 7330’s port management? As far as i‘m informed in some routers you have to enable the port for UPNP. Must be somewhere in the routers menue, possibly home network —> network —> enable port for UPnP or something similar (i excuse for not speaking much italian, although i fell in love with Your country many years ago).

Hi Carsten.
I have found what you have told and I have enabled the port for UpNp.
But nothing has happen.

Where do you have been here in Italy?

Whoops!! I somehow missed this :man_facepalming:t2:… thats a deadlock condition associated with the App holding a file/database lock during suspension, and iOS killed the App as a consequence.

Stefano, this looks like maybe an iOS related issue [rather] than networking. Here’s a suggestion;

  • be sure your iPhone/iPad are updated to iOS 14.4
  • Uninstall Mosaic
  • Reset iOS’ networking; [Settings] → [General] → [Reset] → [Reset Network Settings]
  • Re-instal Mosaic App

Can’t think of anything else to try at this point. :thinking:

(Although, if you use a Mac, you could try connecting your iPhone to it and launching the console to see what happens live as the App crashes, but thats really getting into the weeds :grin: )

I took a look at the FRITZ!Box 7330 configuration manual, couldn’t find anything that might cause what Stefano’s experiencing.

HI Anup.
I’ll try as soon as i can.
In the meanwhile I have installed Mosaic on an Android device.
Same problem.
It took just 4 or 5 seconds more to crash.

:astonished: :thinking:

Hi Stefano,

This is very strange behaviour. I haven’t come across this before - we haven’t been able to replicate this issue and haven’t had any other reports of the same problem, so currently working with our R&D department to get this resolved.

I’ll update here if there as soon as I have anything further.

Thanks
I have also done the network reset that Anup suggested.
The problem remain.

Can I update the Bartok directly from the machine?

It is highly unlikely that the issue is related to the Bartók’s software version - from what you have said above the unit has been updated to version 1.1.1, so this should not be causing a problem.

For reference, you can update a Bartók without using Mosaic by navigating to the Bartók’s IP address in a web browser, clicking on Device Settings, then within the Internet Update section clicking on Check for update. The IP address can be found by opening the Unit Status menu page on the front panel of the unit (press the Menu button three times).

In this case I would expect checking for a new update to report back “No update available” however.

Hi James
I didn’t want to mean that the problem is on Bartok.
I was simply worried how to update the machine in future. Your software update is a high value feature and I don’t want to miss.

I really hope that you can solve this issue.