Serious issues on Mac with latest build

Submitted by dynamitri on Sat, 08/15/2015 - 16:42
Forums: 
Soulseek General Discussion

I'm on the latest MB Pro, with OS X 10.10.4. Fresh machine, barely anything installed barring SoulSeek QT. Unfortunately, I have ran into serious issues with the app:

- if "Minimize to Close" is turned on, I'm unable to quit the app. It just minimises to the dock, there's no way to effectively exit it, Cmd + Q or anything. This makes Finder go crazy, and I can't do any reboots, nor can I switch the laptop off. Looks to me like the system desperately attempts to close the app, but is unable to for whatever reason. The only way to restart/turn the computer off then is via a hard reboot/shutdown (i.e. with the Power key), which is generally not recommended as might result in disk errors or even data loss (I've messed up a drive like this once, being too lazy to switch my apps after 3 weeks' uptime and hundreds of things open used to just cut the power off until the disk kicked the bucket).

- if "Minimise to Close" is turned off, while admittedly it eventually quits the apps, it takes a fair while to do so (16GB RAM and freshly rebooted so no memory/CPU hogs running that might be causing the issue). It also gives a BBOD (beach ball of death) for solid two minutes if not more, while clicking on the SoulSeek QT icon in the dock. While it attempts to quit for a few minutes, the Force Quit option is not available, either.

Just throwing this out there, as I've just paid for 35 days Privilege as I do every month, but I think I'll have to wait until a more stable release with those issues hopefully rectified is out there, and will withhold from using the app for now as it seems a bit uneven on my machine.

Many thanks!

Submitted by Nir on Sat, 08/15/2015 - 23:39.

Hi dynamitri,

The "Minimize to Close" problem is a very serious one, I'll make it so that it's turned off by default for the OSX build, maybe even hide it altogether. Regarding the BBOD, I'm guessing it has to do with the time it takes for the client to save its configuration data. I'd definitely like to improve on that, but in the meantime, how many files are you sharing? And do you remember what build version this problem started with?

Thanks, Nir

Submitted by dynamitri on Sun, 08/16/2015 - 02:07.

Hey Nir, thanks so much for a quick reply. Really appreciated. I'm sharing about 16k files at the moment and am on an SSD drive so things generally go super-quick.

As far as the version - I can only say it's happening with the current one, 2015.6.12. I've just had a brand new machine for a few days and haven't even done any restoring or anything, just have set up everything from scratch so it's the only version I've used on this particular machine.

I can't recall this happening on my previous Mac, though - which has had an older version.

Submitted by Nir on Mon, 08/17/2015 - 11:48.

There's definitely something very wrong with the 6/12 build, I tried sharing a few thousands of files and indeed, the client wouldn't quit. After I force quit and restarted, the entire operating system started malfunctioning to the point that I had to hard boot it. I rebuilt it against Qt 5.4.2 and it seems to be working much better. I updated the link in the sidebar, let me know how it works for you!

Thanks, Nir

Submitted by dynamitri on Tue, 08/18/2015 - 08:47.

Thanks for that, I'll be checking this out later today. You mentioned the problems - does that mean that I'll have to format my hard drive and restore my system from scratch? What actually has gone wrong? Kinda worried that a build that self-admittedly can mess up a system to the point of a hard-boot requirement has gone into the public and I've used it on a fresh system. Thanks!

Submitted by dynamitri on Thu, 08/20/2015 - 05:12.

Considering I'm donating on a monthly basis (and have been doing so for quite some time), I would appreciate a reply from someone connected to the developing team with regards to my question regarding the admitted issues with Soulseek QT and the fact that it might render a system unusable.

I am experiencing massive connectivity issues past few days (happened after installing and using SoulSeek) on a brand new machine, it's quite stressful as it blows my work out of the water and I'm trying to pin down what might be causing it - and whether it would make sense to make an Apple Store appointment with a Genius/Technician to have a look. There's a whole chain of events that I might need to set off because of that, but I'd need to know if the app might have been the cause of the issues in the first place.

Thanks.

Submitted by Nir on Thu, 08/20/2015 - 19:32.

Sorry, there's only me and I've been very busy at work. There shouldn't be any long lasting effects using the 6/12 build, as far as I can tell the problems were just a result of ignoring the window close signal. I can't say it with absolute certainty, but it sounds like your connectivity issues are unrelated.