View Single Post
Posts: 726 | Thanked: 345 times | Joined on Apr 2010 @ Sweden
#58
Originally Posted by jacobkorf View Post
Hello Joorin, the .deb file works flawlessly. No problem with that, great job. I think I know what the "bug" is where I talked about earlier.
What I do to let the program crash:
- Login -> search tab -> look for song -> start song -> click on other song in search results = Crash
- Login -> playlist tab -> look for song -> start song -> click on other song in search results = Crash
- Login -> playlist tab -> look for song -> start song -> click on next / previous (for 2 or 3 times) = Crash

Don't get me wrong, this is my contribution for this great program. If you need anything, just post in this thread. Keep up the great work.
Reporting bugs is good, so no problem. And if you also take the time to test my .deb file, I'm only grateful.

I managed to get it to crash too, but with a longer route, suggesting something a little more complicated than a simple memory error.

I logged in, did a search, started a song, picked another song from search and started that while the other one was still playing. Then I looked in a playlist and started a song from there and, finally, I started a new song from the search result. And this was when it crashed on me. So, I got a bit more fun out of it.

My guess is that this is all related to how my client gets music data from despotify. While changing songs, the data that has just been collected is deallocated resulting in bad things when played. Being able to crash the application with Previous/Next song points in this direction too.

Thank you for the feedback!
 

The Following User Says Thank You to Joorin For This Useful Post: