Tray menu frequently won't close

[akulp]

This happens several times each week and I have to kill the process from Task Manager and restart it to make it go away. It would be great if this could be fixed!



Windows 10 Pro, all builds since I installed Viscosity

[Eric]

Hi akulp,

Are you able to elaborate on what's happening? We've never heard of the tray menu not closing before. Is it a case of you open it and then it won't respond to clicking on it? Or you can't find a way to close the menu without wanting to click on something?

Regards,
Eric

[akulp]

As in, it ceases to respond. I can't click menu options to do anything, and clicking on or away from it does nothing. It's just stuck there. Happens often, but not every time.

[Eric]

Hi akulp,

Next time this happens, can you open Task Manager and go to the details tab. Find Viscosity.exe and let us know how much CPU and Memory it's using.

Also, can you let us know the version of Viscosity and Windows you are using.

Regards,
Eric

[akulp]

Windows 10 Pro, Version 1709, Build 17074.1002
Viscosity: 1.7.6 (1540)

I'll check task manager next time it happens.

[akulp]

Next time this happens, can you open Task Manager and go to the details tab. Find Viscosity.exe and let us know how much CPU and Memory it's using.

I totally forgot about this post until I decided to search for a solution again today and found that I had already reached out! It has continued to happen at least once/week.

.5% CPU, 266MB

I've also created a dump file for debugging that I can send if that will help.

[Eric]

Hi akulp,

Unfortunately we've seen no other reports other than this thread and we haven't been able to replicate the problem. We've made some changes in the current betas which we hope may address the problem based on some theories, please give the latest beta a try - https://sparklabs.com/support/kb/articl ... -versions/

Regards,
Eric

[akulp]

That's surprising since it's not that uncommon for me (weekly at least). Let me know what else I can provide (system info, kernel dump, etc). I've opted into the beta builds. We'll see if that helps.

[Eric]

Hi akulp,

As nothing is crashing, rather hanging, I'm afraid there is no such information to collect. Hangs are usually caused by a problem with the machine, it could be hardware like faulty RAM or Windows just needs a refresh. If there is something we can do to work around the problem we will do it, but it sounds like a fresh install of Windows might be required here.

Please let us know if the problem reoccurs using the latest beta.

Regards,
Eric