Spotify crashes when adding/removing tracks from playlist

[seanbateman7]

So I'm listening to a Radio, a song comes up that I want to add to a playlist, I click on teh album art and select add to playlist select the playlist then BAM music stops, dissapears. I'm rocking a W7 with plenty of memory (8core) NO reason for it to crash.

Also went to play Que to add the song Still crashes

If you can help it would be appreciated cause I'm getting angry.

[Edit - Title for clarity - Mod]

[Groffeaston]

@Sam

Several times I had tried to contact Spotify about this issue and could not find the article that says "How to contact Spotify".  I was redirected back to the main Help page everytime! Then When I did a search for a specific subject, I was also redirected back to the main help page.  A couple of times I got: "No answer available"  and was redirected back to the main help page.  I think a lot of people had the same experience and became very frustrated by it. They wanted to contact Spoify to let them know about their problem they were experiencing. Yes, SPotify was inundated with tons of emails about the problem, but at least they could have done was to let everyone know they are aware of the problem and if people have any problems to report, post them in a specific Topic section instead of sending a "Bug Report" or an "Email for help".  

Also another thing that would have helped to ease the frustration on most users' minds would have been for Spotify to keep everyone updated on any progress. However I know it maybe difficult at times to keep people upated on any progress made on an issue with a "Bug" or "Technical Glitch" until the very last minute. Also sometimes it is difficult to find what is causing the problem and takes a long time to go through all of the data, log files, and other information that is gathered, and sort through it and then see what data is useful and which is not for that specific problem. Sometimes the solution is very simple but it takes a long time to find that out. Other times the solution is complicated or complex, but was found quickly and will take a long time to program the solution.

Then there are those times when you fix one thing and another pops up! The solution to fix one problem causes another one to pop up. ANd that takes even longer to fix overall! 

Basically What I am saying is everyone has to be patient when dealing with problems/bugs/technical glitches and waiing for the fixes. Also the people who come up with the solutions should keep those who are waiting for the fixes, up to date on what is going on, if at all possible. We want to be able to help the Techs/Developers/etc..come up with a solution!

I hope that the users, the Moderators, and the Techs can work together and keep each other in the know when any other problems like this arise. Hopefully we can learn from this and find ways to help expedite support and streamline support requests and sending in the data logs and other information. 

[MarkMacabre]

I have the exact same problem and its been going on for weeks and I am gettng extremely frustruated.

[MarkMacabre]

This solved my issues. Thank you!

[skitslicker]

New version - success. Thanks folks.

[Groffeaston]

I noticed trhat there are still people posting in other Topic Posts about this problem, I hope that one of the Moderators can post a link to either this Topic post or edit those Topic Posts to include a link to the fix. Also one of the Moderators should post that there will be an update on the way and to please be patient untill their Spotify Player receives the update and then installs it.

[Rollo_]

http://community.spotify.com/t5/Help-Desktop-Linux-Mac-and/Release-Notes-Spotify-for-Desktop-0-9-4/t...

The biggest problem is that only of handful of posters seem to read other posts before posting themselves.

[SalsaShark]

Rorey,

Spotify Premium members will be getting a credit for the amount time that this issue took to fix, correct?

[SalsaShark]

Picking a nit here as I'm also a software engineer with a large multinational computer systems company:

"It's important we understand that is not a simple bug to reproduce, because it required some unknown amount of time to pass while context-switched to some other program for it to occur (somewhere between 20 and 45 minutes in my experience). That's a long time for a computer, and any number of things could have happened during it to trigger the crash. It's also a long time for a developer to wait to reproduce a bug (about a 10th of their working day), and because of the uncertainty around what during that time was triggering the issue, it makes it difficult to create an automated test for the crash. As a result, just causing the bug and capturing the necessary information about the programs state and context was harder for this bug than most of the others they deal with. It's exactly this kind of bug I dread having to deal with."

This is an incorrect statement and pretty much invalidates a large part of your defense of the issue.  For the crash-during-deletion issue, it could be reproduced in a matter of seconds.  Thus, it should not have taken long to identify the root cause and determine a resolution.  That said, I would have still given them a few days to do QA/regression testing.

[uberjoe]

---

@SalsaShark wrote:

Picking a nit here as I'm also a software engineer with a large multinational computer systems company:

"It's important we understand that is not a simple bug to reproduce, because it required some unknown amount of time to pass while context-switched to some other program for it to occur (somewhere between 20 and 45 minutes in my experience). That's a long time for a computer, and any number of things could have happened during it to trigger the crash. It's also a long time for a developer to wait to reproduce a bug (about a 10th of their working day), and because of the uncertainty around what during that time was triggering the issue, it makes it difficult to create an automated test for the crash. As a result, just causing the bug and capturing the necessary information about the programs state and context was harder for this bug than most of the others they deal with. It's exactly this kind of bug I dread having to deal with."

This is an incorrect statement and pretty much invalidates a large part of your defense of the issue.  For the crash-during-deletion issue, it could be reproduced in a matter of seconds.  Thus, it should not have taken long to identify the root cause and determine a resolution.  That said, I would have still given them a few days to do QA/regression testing.

---

Why does the crash not happen in the first 20 minutes or so after you restart Spotify?

[Rorey]

@Groffeaston We're definitely tackling several other issues which should be fixed. Staff are updating these accordingly but if you see any threads not getting some love feel free to ping me or send me a PM with the links.

[Kingodin]

What are the actual locations ??

Cant find a Library Location for spotify.

Running win 7 64 bit with latest Spotify

[Peter__]

---

@Kingodin wrote:

What are the actual locations ??

Cant find a Library Location for spotify.

Running win 7 64 bit with latest Spotify

---

The default folders on Windows are:

C:\Users\...\AppData\Roaming\Spotify

C:\Users\...\AppData\Local\Spotify

AppData is a hidden folder, so you might need to change your settings to allow you to see it in Windows Explorer. 

Peter

[SalsaShark]

I'm not sure why you keep insisting that's the case. 

[Rollo_]

Rorey wrote:

if you see any threads not getting some love feel free to ping me or send me a PM with the links.

Please restore View as Album List feature 

At the VERY LEAST, track numbers should be listed.

[JWofNC]

I believe Windows could be knocking out Spotify when it tries to access its files without granted permissions or if these files/folders are locked with "read only" attributes. If this is the case, you might try this:

Right-click on each of these folders one by one and select "Properties" then do the following for both folders:

1. Under the "Security" tab, check to make sure your Windows Username appears in the User's box, and that you have full control. If not:

    a. Click the "Add" button.

    b. When the next window opens, type in your Windows Username, then click on the "Search Names" button.

    c. Your Username should appear underscored in the big white box if entered correctly. Click the "OK" button.

    d. Check the box for "Full Control" in the "Permissions" list and click the "Apply" and "Close" buttons.

2. These folders have the "read only" attributes set which could prevent Spotify from accessing them. Clear the box and click the "Apply" button. (You may need to log onto Windows as "administrator" if the settings don't stay.

3. Under the "Share" Tab, enable sharing - "Spotify" or "Spotify2" should automatically appear in the field.

4. This may also help improve Spotify performance - use at your own discretion:

     a. Click on the "Advanced Sharing" button

     b. Click on the "Caching" button (Offline Settings)

     c. Select the 3rd radio button and the check box for "Optimize for Performance".

Other possible reasons for the crash might be runtime issues or that Spotify is allowed only a limited number of drag-and-drop actions per session while running it. In any case, only the Spotify developers would know for sure (they should).

[LoneSoldierRyan]

this **bleep** is happeneing with me aswell on vista 32 bit

[LoneSoldierRyan]

i recently added a song to my playlist and tspotify crashes , then i relaunch it and it and it says installing spotify, then it launches and all my starred songs have been reset...

[Rollo_]

Read the previous comments.  Update to version 0.9.4.

[Groffeaston]

@Rorey  Thanks for the Reply, The only reason I mentioned the other posts was that it was dealing with the same problem. How do I know that? because I had posted there, before I was redirected to this one. I had received an update the other day stating that someone had posted they had the same problem, after I had posted there, which was several weeks ago; just over 3 weeks now.

So far, since the new update came out I have not had any of the problems I experienced before.   If some people are still having problems, even with the new update, the only things that I can think of that might have happened is that some people may have accidentally deleted some needed files or may have had them corrupted in some way and that is causing them to still have problems.  Some Security programs might be interfering, if people made changes thinking that they had a virus or some other malware and forgot to undo the changes. And the only other thing I can think of is some people may have made some change to either their Web Browsers settings, Computer settings, and/or Spotify settings and then forgot to undo them before the new update was installed. 

I hope my thoughts and Ideas help.

[SalsaShark]

Having good luck with the new version--no crashes yet.

Just waiting for you guys to issue credit for Spotify Premium members.