rgdawson wrote: > Am I correct in assuming this happens sometimes on startup, before the > app has passed the initialization phase. I think it is possible to > experience this bug by clicking on the tray icon before the program has > fully initialized the browser. You can avoid it by waiting a couple > more seconds before clicking on the tray icon. (Like wait for it to > turn blue). For test purposes I had commented out a line of code that > defended against this error and forgot to put it back in the last > version. New version on the way. > > If this description is not the case. If you are getting an error like > this under other circumstances, then please let me know. > > R Greg Dawson
The Access Violation window appears BEFORE the icon appears in the task bar. It is either when I reboot Windows 10 - or if I stop Squeezelite-X (kill the process tree) and restart the app. The Access Violation window always appears before the loading of the icon. I most cases the configuration screen has the correct data and I can see in the application log that the app does not see an error condition. So I guess the error occurs before the app starts the application log ? If I wait, the app connects to my server, icon turns blue and everything works as usual. Just the initial error on load isthe odd occurrence. Many thanks for the app by the way :-) ------------------------------------------------------------------------ rodlogic's Profile: http://forums.slimdevices.com/member.php?userid=8716 View this thread: http://forums.slimdevices.com/showthread.php?t=108550 _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/plugins
