Announcements

[Desktop] The Support tells me to share Crash Reports via posts here as a new IDEA! WOW!

Reply

[Desktop] The Support tells me to share Crash Reports via posts here as a new IDEA! WOW!

mnin
Casual Listener

Hey,

 

Spotify released a new version for the macOS app, which crashes all the time now. It isn't useable anymore.

 

Asked the support how to approach here and they tells me, I should share the crash report here. As a new idea, i'am now really impressed.

 

Here is the important part from the crash log:

 

Process: Spotify [55089]
Path: /Applications/Spotify.app/Contents/MacOS/Spotify
Identifier: com.spotify.client
Version: 1.1.58.820.g2ae50076 (1.1.58.820.g2ae50076-37)
Code Type: X86-64 (Translated)
Parent Process: ??? [1]
Responsible: Spotify [55089]
User ID: 501

Date/Time: 2021-05-04 11:35:16.899 +0200
OS Version: macOS 11.3.1 (20E241)
Report Version: 12
Anonymous UUID: 4AA05E17-6063-8721-D0F2-6A5D2C93E023

Sleep/Wake UUID: DE398404-6414-4A5D-B500-747A5C06A47A

Time Awake Since Boot: 24000 seconds
Time Since Wake: 4400 seconds

System Integrity Protection: enabled

Crashed Thread: 0 CrBrowserMain Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x000052aeb838d520
Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [55089]

VM Regions Near 0x52aeb838d520:
GPU Carveout (reserved) 1000000000-7000000000 [384.0G] ---/--- SM=NUL reserved VM address space (unallocated)
-->
MALLOC_NANO 600000000000-600008000000 [128.0M] rw-/rwx SM=PRV

Thread 0 Crashed:: CrBrowserMain Dispatch queue: com.apple.main-thread
0 libobjc.A.dylib 0x00007fff202a641f objc_release + 31
1 com.apple.CoreFoundation 0x00007fff205ca027 _CFRelease + 244
2 com.apple.CFNetwork 0x00007fff2476d651 0x7fff24679000 + 1001041
3 com.apple.CoreFoundation 0x00007fff204ff7dc __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
4 com.apple.CoreFoundation 0x00007fff204ff744 __CFRunLoopDoSource0 + 180
5 com.apple.CoreFoundation 0x00007fff204ff4ba __CFRunLoopDoSources0 + 242
6 com.apple.CoreFoundation 0x00007fff204fdec8 __CFRunLoopRun + 897
7 com.apple.CoreFoundation 0x00007fff204fd480 CFRunLoopRunSpecific + 567
8 com.apple.HIToolbox 0x00007fff28981203 RunCurrentEventLoopInMode + 292
9 com.apple.HIToolbox 0x00007fff28980f65 ReceiveNextEventCommon + 587
10 com.apple.HIToolbox 0x00007fff28980d03 _BlockUntilNextEventMatchingListInModeWithFilter + 70
11 com.apple.AppKit 0x00007fff22c23b32 _DPSNextEvent + 864
12 com.apple.AppKit 0x00007fff22c22305 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1364
13 com.apple.AppKit 0x00007fff22c14679 -[NSApplication run] + 586
14 org.chromium.ContentShell.framework 0x000000011233987c cef_time_delta + 3029180
15 org.chromium.ContentShell.framework 0x000000011233864c cef_time_delta + 3024524
16 org.chromium.ContentShell.framework 0x00000001122f4ac7 cef_time_delta + 2747143
17 org.chromium.ContentShell.framework 0x00000001122c057d cef_time_delta + 2532797
18 org.chromium.ContentShell.framework 0x0000000111fcf733 ChromeAppModeStart_v6 + 6819059
19 com.spotify.client 0x0000000102c304d6 0x102b68000 + 820438
20 libdyld.dylib 0x00007fff20421f3d start + 1

 

Thanks for nothing

7 Replies

Re: [Desktop] The Support tells me to share Crash Reports via posts here as a new IDEA! WOW!

FloriKori
Casual Listener

I Have the Same Problem (Macbook M1)

 

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000140614608ee8
Exception Note: EXC_CORPSE_NOTIFY

Re: [Desktop] The Support tells me to share Crash Reports via posts here as a new IDEA! WOW!

mnin
Casual Listener

I'm still shocked at how they apparently treat customers today who want to test the BETA software (because it's not stable) and give feedback.

 

I was very uncomfortable reading that I should just download Spotify again. And instead of taking the CrashLog at the developers to open a ticket to post here as Idea.

Re: [Desktop] The Support tells me to share Crash Reports via posts here as a new IDEA! WOW!

Eni
Moderator
Moderator

Hi folks, 

 

Thanks for reaching out about this here in the Community. 

 

@mnin, we're sorry that you feel this way. Just to make sure, are you a beta/alpha tester? If so, you can send your feedback about the app's performance via Test flight. If you aren't and you're having issues with the latest official version of the desktop app, could you let us know what troubleshooting steps you've already tried? This will help us give you better suggestions. On another note, the Idea Exchange is a great way for us to see what our users are interested in and how many people like a certain idea. Check out this Spotify Answer to learn more about it.

 

@FloriKori, could you let us know if this issue started happening after a specific update and what troubleshooting steps you've already tried? 

 

We'll be on the lookout for your reply. 

EniModerator
Help others find this answer and click "Accept as Solution".
If you appreciate my answer, maybe give me a Like.
 
“Music acts like a magic key, to which the most tightly closed heart opens.”– Maria von Trapp

Re: [Desktop] The Support tells me to share Crash Reports via posts here as a new IDEA! WOW!

mnin
Casual Listener

@Eni nope, it's the 'stable' version.

 

TestFlight is only available on iOS/iPadOS devices. Not on macOS.

 

Just download the latest version of Spotify and run it on an M1 Mac. That's enough to reproduce it.

 

And I think, this Spotify Community Site is totally broken, when I try to just response it doesn't let me post my message, because of Robot reasons every 2 minutes, some 500 error also occurred. After another try, the captcha was solved since 10 seconds, clicked on POST again and run into the same, not be able to just post it, have to solve the captcha again and again and again and again and again.

Re: [Desktop] The Support tells me to share Crash Reports via posts here as a new IDEA! WOW!

FloriKori
Casual Listener
I think we are all talking about the same problem. Latest version (and some before) + MacBook with m1 Chip causes the problem.

https://community.spotify.com/t5/Desktop-Mac/M1-Mac-Constantly-crashes-Absolute-Nightmare/td-p/51779...

Re: [Desktop] The Support tells me to share Crash Reports via posts here as a new IDEA! WOW!

CarlosE
Moderator
Moderator

Hey folks,

 

Thanks for keeping in touch.

 

As with any new CPU and OS architecture, some time might need to pass until apps are optimized to run on those. In the meantime, we suggest adding your +Vote to this idea thread. You can add your crash logs there as well for easy tracking, and any other comments/reports you have about it.

 

@mnin, we're sorry to hear that you had some trouble when posting in the Community. We suggest trying from an incognito/private window in the browser and if possible, with a different connection.

 

Hope this helps. If you have any questions or need anything else, give us a shout.

 

Take care!

CarlosEModerator
 
Help others find this answer and click "Accept as Solution".
If you appreciate my answer, maybe give me a Like.
 

Re: [Desktop] The Support tells me to share Crash Reports via posts here as a new IDEA! WOW!

mnin
Casual Listener

Let's look back for a moment, I am a developer myself and have had the Developer Transition Kit from Apple. It arrived here at the end of June 2020 and I had it available here until a few weeks ago.

 

I then ordered a Mac with the new CPU technology as recently as December 2020. This arrived here in January.

 

So I have had time to test the new architecture and switch to it for 11 months. It is not clear to me what should be a problem for Spotify here, or why I should vote for the present.

 

Spotify has very likely also had the chance to work on this already here. After all, Spotify will have users who have already adapted this new technology. Besides, the iOS app already runs fully on this technology, which is why I also assume that knowledge is available in the company to adapt this new architecture. So it isn't just a feature it's the current state of Apple Mac hardware.

 

Accordingly, it must be more a matter of politics that is putting the brakes on here.

SUGGESTED POSTS