You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right-clicking the Volume² notification area icon creates more GDI objects and never releases them. Eventually, the per-process limit (10,000) is reached and the OSD will no longer come up, nor will Options, nor the built-in volume control UI (Standard regulator) function. The results are identical to the issues reported in #119.
Repro
Open Task Manager
Go to the Details (Win8+) or Processes tab
Right-click on one of the columns, choose Select columns
Find the GDI objects, select it and choose OK
Click on the GDI objects field to sort
Run Volume² if not already started
Go to the notification area (system tray) and right-click on the Volume² icon
Observe GDI objects for Volume2.exe rising
Repeat right-clicking and watch the GDI objects value
Since no one wants to spend all day clicking, here is an AutoHotKey script to continuously right-click the icon, and an executable version if you don't have AutoHotKey handy. The script will begin immediately right-clicking upon startup.
Here's a sped up GIF showing this. It takes about 2 minutes normally:
Although the volume control part still works, since only two new GDI objects can be created, it can't create the OSD, the built-in volume control UI, nor the Options, as shown here:
Windows version: 10 (20H2 and 21296 [current insider dev])
Volume² version: 1.1.6.411 and 1.1.6.428
Additional GDIView shows the vast majority of these objects as being bitmaps. Also, out of curiosity, why are 1,461 objects used at startup when nothing is on the screen? All the parts of the UI that the user interacts with are created later. I suspect this leak at initialization may be part of it as well.
The text was updated successfully, but these errors were encountered:
Right-clicking the Volume² notification area icon creates more GDI objects and never releases them. Eventually, the per-process limit (10,000) is reached and the OSD will no longer come up, nor will Options, nor the built-in volume control UI (Standard regulator) function. The results are identical to the issues reported in #119.
Repro
Since no one wants to spend all day clicking, here is an AutoHotKey script to continuously right-click the icon, and an executable version if you don't have AutoHotKey handy. The script will begin immediately right-clicking upon startup.
Here's a sped up GIF showing this. It takes about 2 minutes normally:
![](https://camo.githubusercontent.com/7e77f4ecd11e495454b0b10abed5b0bb7271e609777b9c2c6a4f9df43db7c1da/68747470733a2f2f692e696d6775722e636f6d2f767442677a42722e676966)
Although the volume control part still works, since only two new GDI objects can be created, it can't create the OSD, the built-in volume control UI, nor the Options, as shown here:
![](https://camo.githubusercontent.com/dbee3fc56649607385142d0935a8ec0f22dd27ade668e75cacb944706ae60172/68747470733a2f2f692e696d6775722e636f6d2f354a68656648772e706e67)
Additional
GDIView shows the vast majority of these objects as being bitmaps. Also, out of curiosity, why are 1,461 objects used at startup when nothing is on the screen? All the parts of the UI that the user interacts with are created later. I suspect this leak at initialization may be part of it as well.
The text was updated successfully, but these errors were encountered: