8

Closed

[FIXED] Toastify Errors with New Spotify Version

description

The Basic Problem
While technically speaking the new version of Spotify (1.0.23.90) can run to some extent with Toastify, it appears that Toastify album art is broken, keyboard commands have been reported to lag, and I've personally found that the new version of Spotify when running with Toastify is significantly more taxing on my processor than older versions (or when Toastify is disabled).


Solution
Update to the new version of Toastify (1.8.3). In terms of the functionality that I use, the new Toastify version works flawlessly.


Original Post
With Spotify version 1.0.23.90.g42187855 the latest version of Toastify causes errors and crashing.

When I launch Toastify now, two command line windows open in addition to Spotify. The first one is blank, the second one says this:
[0219/000031:ERROR:main_delegate.cc(764)] Could not load cef_extensions.pak
If I close the blank command prompt Spotify crashes/closes.

If I close the second one I get a third saying this:
[0219/000200:ERROR:main_delegate.cc(764)] Could not load cef_extensions.pak
[0219/000200:ERROR:gles2_cmd_decoder.cc(14033)] [.Compositor-0E27E640]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[0219/000200:ERROR:gles2_cmd_decoder.cc(7430)] [.Compositor-0E27E640]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
This third error message is displayed again if I try to close that command prompt but after that the errors go away.

Technically speaking Spotify will run and appear to work properly with Toastify as long as the blank command prompt is left open.

EDIT
I believe what is breaking are Toastify album covers in notifications. I've been listening to music for several hours both online and offline and not once has Toastify displayed an album cover.


Basic System Info
Intel i7-3630QM
Nvidia GTX 770M
Windows 10 Pro 64-bit
Closed Jun 7, 2016 at 8:21 AM by nachmore
All fixed :)

comments

firekilroy wrote Feb 20, 2016 at 8:05 AM

Same Spotify-version for me, it upgraded this morning. Running on Win 8.1x64

Had Toastify 1.7.6 at first with only one cmd-window (Could not load...). Upgraded to T 1.7.8 and now have both windows. Some difference there maybe?

I only use toastify for hotkeys, with toasts disabled, so I cannot help you with any guesswork as to the toasts.

wrote Feb 20, 2016 at 10:02 PM

abulawright wrote Feb 21, 2016 at 2:38 PM

I have the same Spotify version running in Windows 10 x64bit. As mentioned, two command windows open when Spotify is started using Toastify (does not occur when Spotify is launched manually). Also, album covers do not work as well, just Toasify logo is shown.

Alex

wrote Feb 21, 2016 at 2:39 PM

abulawright wrote Feb 21, 2016 at 2:39 PM

I have the same Spotify version running in Windows 10 x64bit. As mentioned, two command windows open when Spotify is started using Toastify (does not occur when Spotify is launched manually). Also, album covers do not work as well, just Toasify logo is shown.

Alex

wrote Feb 22, 2016 at 12:05 PM

ReLexEd wrote Feb 22, 2016 at 12:09 PM

Bummer... I get the same here...
Only using Toastify for the hotkeys, which now leaves me with two extra windows open during the workdays ;-)

First extra window : [0222/140215:ERROR:main_delegate.cc(764)] Could not load cef_extensions.pak
(Running Appdata\Roaming\Spotify\spotify.exe)
second extra window: stays blank, but also runs Appdata\Roaming\Spotify\spotify.exe

Also, I get the feeling that the hotkeys are being relayed slower than before (approx. 500ms delay)

wrote Feb 23, 2016 at 8:51 PM

robbyus1111 wrote Feb 23, 2016 at 8:54 PM

Same for me here.

My toastify is not installed in my C drive by the way (don't know if it has something to do with it)

i7 4970k
Gtx970
16g ram
Windows 10 Pro x64

wrote Feb 24, 2016 at 1:36 AM

Exper1mental wrote Feb 24, 2016 at 1:38 AM

I have edited the opening post to include a temporary solution for those who are interested.

wrote Feb 24, 2016 at 1:46 AM

wrote Feb 24, 2016 at 1:49 AM

abulawright wrote Feb 24, 2016 at 8:19 PM

Tried method mentioned in the opening post. Seems to prevent multiple cmd windows opening upon start-up, however, album covers are still not working.

Also, Spotify managed to successfully update to the latest version once opened, even though I had created the extra file and marked it read-only.

Alex

Exper1mental wrote Feb 24, 2016 at 10:58 PM

@abulawright
What version did you try using? Have you tried using a 0.9.x version?

Here are some other ideas you could try
Block upgrade.spotify.com
Spotify waking my PC through the night really ticked me off. Whilst the tricks with "Spotify_new.exe" and "Spotify_new.exe.sig" worked well on older versions, but not on the newer versions. I stumbled upon mention of "upgrade.spotify.com". Adding it as a bogus entry in the hosts file has so far worked a treat.

Step by step instructions are here for those who need it. Otherwise, you guys know what I mean.
  1. Hit "windows key" + R
  2. Enter "notepad %windir%\system32\drivers\etc\hosts"
  3. Add "127.0.0.1 upgrade.spotify.com" to the bottom of the file.
  4. Save and close
Set installer to Win 95 mode
Found a solution, just make sure you've got an older version of spotify up with a prompt to update to the latest version
  1. Locate Spotify folder in appdata/roaming/Spotify
  2. Find Spotify_new.exe and open the properties of that file
  3. Go to compability tab and press "change settings for all users"
  4. Set compability mode to always run as windows 95
  5. Apply settings
Now whenever spotify "updates", the old version will stay the same and the new version will install in C:\ProgramData\Spotify. The old version will stay intact in appdata/roaming/Spotify. Run Spotify.exe from there and you won't get any updates!
Create a Batch File Deleting Update Files
You could arrange to run a batch file containing
del C:\Users\username\AppData\Roaming\Spotify\Spotify_new.exe
del C:\Users\username\AppData\Roaming\Spotify\Spotify_new.exe.sig
and arrange to have it run when your PC starts up.
Mine's rarely rebooted, so I have no problem reinstalling the old one occasionally, if necessary.
All of these I found in this Spotify thread.

wrote Feb 24, 2016 at 11:07 PM

wrote Feb 24, 2016 at 11:09 PM

wrote Feb 27, 2016 at 4:20 PM

nachmore wrote Mar 1, 2016 at 7:36 AM

sigh sadly a lot of this makes sense:
  • Spotify is more taxing under Toastify because, to control the new client it needs to run it under what is essentially a debugger (ChromeDriver) making Spotify consume more resources
  • The command lines are a side effect of the debugger, though their obviously something new that Spotify added in, would be nice to eliminate those
  • No idea about the keyboard lag, those commands haven't changed much
  • The album art is a new one, likely due to a recent Spotify change
To summarize, I'm investigating everything. Removing ChromeDriver (which should now be possible, though we'll lose some functionality) will be a pain, but I'll look into getting it done asap.

Note that all development is now happening on github...

wrote Mar 4, 2016 at 11:06 PM

wrote Mar 12, 2016 at 11:25 AM

wrote Mar 12, 2016 at 11:38 AM

Exper1mental wrote Mar 12, 2016 at 11:40 AM

Just got the new Toastify version, everything is fixed and back to normal :D

Thanks for keeping Toastify updated!

wrote Jun 7, 2016 at 8:21 AM