Apple Working on Fix for Spotify Kernel Panic Bug on OS X

[69Mustang]

Yes. What I originally quoted.

" OS X 10.9.5 was crashing after updating to Spotify version 1.0.15.133."

It doesn't say that Spotify was crashing after updating OS X, so it's obviously something Spotify changed in their code. (unless MR is just doing a ****** job reporting the story and has the details wrong.)

Your explanation completely ignores that, according to the article: 1. Apple acknowledges the bug. 2. Is working on a fix. 3. The bug affects other apps.

So either Spotify and the other affected apps made the exact same changes to their software, causing kernel panics, or it's a known bug that Apple will eventually fix. Based on evidence presented, I'm more inclined to believe Apple knows about the bug and will fix it.

 

[macsrcool1234]

I mean it sounds like it's Spotify's software causing the crash. Why can't they fix their own code? I wouldn't exactly be expecting a swift response from Apple when their  Music competitor is having issues.

Edit: I'm not saying that Apple's shouldn't fix whatever bug is on their end. Just that Spotify wasn't crashing until they changed something in their own code for 1.0.15.133. Yes, Apple needs to fix their OS, but Spotify shouldn't just let their customers suffer in the interim— what's preventing them from reverting to the code that wasn't causing their user's computers to crash?

Clearly you have absolutely no idea how programming works.

If Apple provides an API, it's Apple's responsibility to make sure that API doesn't cause a kernel panic. Simple.

Also, it's not just Spotify crashing.....

 

[whooleytoo]

User space code should never be able to cause a kernel panic. If it's happening, it's the fault of the kernel space code.

Absolutely this. The fact that it's triggered by something in Spotify could mean there's a serious bug in the app, or simply there's some code path it's triggering that is causing serious issues. But either way, the kernel shouldn't panic.

When it comes to assigning guilt for panics, it's always the kernel (in the library, with the candlestick, in the libary... cluedo reference anyone?)

 

[thermodynamic]

Yeah let me just turn off my Firewall.

If it helps, Macs come with their internal firewall disabled and at least Macs have it to enable (for now, anyway). iOS has none unless you jailbreak the thing and download one somewhere, hoping it doesn't have any hidden issues... considering computing history and why firewalls were put in to begin with, Apple - as usual - is behind the times or falling backwards and devolving.

 

[ck2875]

Clearly you have absolutely no idea how programming works.

Haha, I completely agree with this assessment.

 

[macs4nw]

It impacts Spotify...how convenient for Apple!

Not convinced Apple would stoop that low..... also, a bug on their end only reflects on Apple's competence, and not on Spotify's. Why would Apple deliberately erode people's confidence in their software expertise? With all the recent bugs, they definitely don't need that.

 

[ck2875]

Your explanation completely ignores that, according to the article: 1. Apple acknowledges the bug. 2. Is working on a fix. 3. The bug affects other apps.

So either Spotify and the other affected apps made the exact same changes to their software, causing kernel panics, or it's a known bug that Apple will eventually fix. Based on evidence presented, I'm more inclined to believe Apple knows about the bug and will fix it.

Geez. Again, I'm NOT saying there isn't a bug in Apple's OS (yay double negatives). There clearly is. My entire point was just that Spotify shouldn't put all of the blame on Apple, when it's their own update that started the issue (for Spotify).

• Yes, there are other apps that cause the panic.
• Yes, Apple is aware of the bug.
• Yes, Apple is working on a fix.
• BUT... why can't Spotify undo whatever the F they changed in their own code that started causing their users computers to crash when they rolled out Spotify version 1.0.15.133 and suddenly there are issues? I'm completely aware that OS X shouldn't be crashing. I'm just asking what is preventing Spotify from trying to release a stable build that doesn't cause a kernel panic until Apple fixes their bug.

I really wasn't planning on getting into a debate at who is at fault. My original post was just saying if I was Spotify, I wouldn't be waiting around for Apple to fix OS X when prior Spotify builds were working properly.

 

[emm386]

I'm just asking what is preventing Spotify from trying to release a stable build that doesn't cause a kernel panic until Apple fixes their bug

Why re-invent the wheel? If Apple has an API for that job - you naturally use it. That's what they are for.

And heck - They (Apple) change their OS- and API-behavior within minor Operating System - Upgrades themselves. So developers never really know, how their application might behave after Apple's latest innovative ajustments to the core OS.

 

[69Mustang]

Geez. Again, I'm NOT saying there isn't a bug in Apple's OS (yay double negatives). There clearly is. My entire point was just that Spotify shouldn't put all of the blame on Apple, when it's their own update that started the issue.

• Yes, there are other apps that cause the panic.
• Yes, Apple is aware of the bug.
• Yes, Apple is working on a fix.
• BUT... why can't Spotify undo whatever the F they changed in their own code that started causing their users computers to crash when they rolled out Spotify version 1.0.15.133 and suddenly there are issues? I'm completely aware that OS X shouldn't be crashing. I'm just asking what is preventing Spotify from trying to release a stable build that doesn't cause a kernel panic until Apple fixes their bug.

Your post ignores the changes that have been made under the hood to OSX. Neither Apple nor Spotify's software exists in a vacuum and remains static. Anything Spotify might do to mitigate the issue could further exacerbate the issue. The bug is the reason for the kernel panic. Ask yourself this: If Spotify could fix the problem with a simple rollback don't you think that would been their first action?

You've already stated you're not exactly knowledgeable about software. Fixes aren't as easy as Scorpion makes them out to be You seem to be caught up in the blame game. By that I mean, you think Spotify is blaming Apple so you want to come to Apple's defense by laying the blame on Spotify. It's not about blame at all. It's about finding root cause for an issue. Letting customers know what the issue is and letting them know how it's going to get fixed.

 

[rdlink]

By "working on it" do they mean trying to find a way to make it happen consistently...?

I kid.

 

[Ries]

Disable the firewall? This "workaround" really unsafe and untenable. Google is probably going to buy Spotify. Hope they don't shutter it

The firewall is default off.

 

[kirky29]

Disable the firewall? This "workaround" really unsafe and untenable. Google is probably going to buy Spotify. Hope they don't shutter it

What makes you say Google is probably going to buy Spotify?

 

[Trik]

Spotify didn't have an issue until they updated their own software. Yes, Apple needs to fix whatever is causing a kernel panic, but Spotify could just roll back whatever changes they made in their own code that's causing the issue instead of throwing the blame on Apple. It's not like Apple issued a software update that broke Spotify, but rather Spotify issued an update that broke OS X. Unless Eddy Cue has the pre-cogs from Minority Report working for him, it's not like Apple can predict ways to cause future versions of Spotify to crash OS X.

Perception vs reality. The fact is, "There is a bug in OS X that crashes Spotify"... Apple has admitted to that fact. That's all the headline has to say to get people talking. I'm just saying they should prioritize a fix based on that perception.

 

[Kissaragi]

I thought this was just me, I was planning on reinstalling OSX tomorrow to try and fix it.

 

[mdriftmeyer]

Is this related to the fact that Spotify takes FOREVER to load on my Macbook? So much so, that I almost don't even open it up on my mac. I would rather just launch it on my iPad. I have 8gigs of Ram and an i7.. so I have no idea why it takes this long.. but its unbearable and sometimes locks up my entire computer.

Check your system logs for output.
[doublepost=1456511876][/doublepost]

I thought this was just me, I was planning on reinstalling OSX tomorrow to try and fix it.

Never reinstall OS X based upon a third party app crash.

 

[Keirasplace]

Yeah let me just turn off my Firewall.

Well, if you can use your router as a firewall, if it has this capability; which most have. Usually it's a bit messy to do that, but it works.

If you're core OS services are sound, having or not having a firewall doesn't make much difference.

It's more for third party apps that you may need it.

[doublepost=1456512226][/doublepost]

if a modern multitasking os panics as a result of something a user application does, it is always the os creator's fault

They're using directly or indirectly a OS service, or API, so obviously it's their fault; you wouldn't get a Kernel Panic if everything stayed in user space.
But, it may show rarely because few use those capabilities in this way, or something that shows up only because a third party lib uses the system in a novel way (one that's not been tested for).

 

[ReneR]

now THAT is awesome kernel quality in the internet connected world :-/

 

[Tonishal]

I just experienced this spotify crash on Yosemite couple a day ago

 

[DUCKofD3ATH]

TURN OFF MY FIREWALL?!

That's Apple's solution? Yeah, right. I'm sure they'd rather say "Stop using Spotify".

 

[SlipperySlop]

A perfectly-designed OS should never kernel panic at all because of malfunctioning third-party software.

I think it is a serious bug/exploit if a end user program can crash the OS.

This would have never happened if Steve Jobs were still alive. He kept very tight control over every line of code. This kind of thing is just another strike against Apple. How many more strikes like this can Apple survive? It may be time to move to another platform.

 

[urtho]

I just use the website. I hate having generally useless apps on my system. With how rarely I use Spotify the app makes no sense.

 

[JosephAW]

OS X 10.4 & 10.6 were the rock and hardly ever crashed, now everything is just milk toast. Even iOS is declining since iOS 7.

 

[69Mustang]

This would have never happened if Steve Jobs were still alive. He kept very tight control over every line of code. This kind of thing is just another strike against Apple. How many more strikes like this can Apple survive? It may be time to move to another platform.

Bit of revisionist history don't you think? There are plenty of examples that run contrary to your "woulda never happened under Steve". Perception and reality sometimes don't intersect when people discuss Jobs. Shame really. The man was special enough without the RDF.

TURN OFF MY FIREWALL?!

That's Apple's solution? Yeah, right. I'm sure they'd rather say "Stop using Spotify".

That's not Apple's solution. Nor is it Spotify's solution. That was a user suggested work around.

 

[emm386]

OS X 10.4 & 10.6 were the rock and hardly ever crashed, now everything is just milk toast. Even iOS is declining since iOS 7.

Still Using Snow Leopard on my MacBook. It's fast, super-responsive, very low on memory and CPU cycles and only ever crashed on me once. Lion was a catastrophe in these aspects. Ever after, I did not want to try the new versions... I'm not a beta tester, I need my notebook to get work done on.

 

[Ishayu]

This ain't the first time I've seen networking related code crash a Mac. When I bought my 2011 MacBook Pro for university way back in... well, 2011, it really liked kernel panicking for no discernable reason.

Fortunately I was studying computer science and found out that the crash happened due to a malformed network package being sent by two people to everyone on the network, because they'd found out it would crash all Macs on the Wi-Fi part of the network. -.-' They kept doing this for half a year, the jerks.

This bug eventually got fixed, but turns out there's a new one...

Look, OS X should never crash because of receiving or sending garbage data via a network. That's ridiculous. This one is definitely on Apple, which they have admitted, and are hopefully going to fix.