zaps166
Using 100% of a core (QMPlay being idle), Win64
Running QMPlay2 (portable @ Win64) it occupies a single core to 100% continually.
All communcation widgets are closed, automatical update is disabled.
That should not be, should it?
Windows: Win7-64 Prof. SP1 etc. OMPlay2: actual release 25.06.27-portable (x86_64)
EDIT: Additional info. Log shows: [13 Aug 2025 12:38:45.337] Vulkan is unable to work with QMPlay2 on this platform: Failed to load vulkan library!: ErrorInitializationFailed
[13 Aug 2025 12:38:45.337] Vulkan is unable to work with QMPlay2 on this platform: Failed to load vulkan library!: ErrorInitializationFailed
If you have old GPU (or drivers), Vulkan will not work and QMPlay2 switches to OpenGL.
Running QMPlay2 (portable @ Win64) it occupies a single core to 100% continually.
Do you have steps to reproduce or it happens after start with clean settings?
[13 Aug 2025 12:38:45.337] Vulkan is unable to work with QMPlay2 on this platform: Failed to load vulkan library!: ErrorInitializationFailed
If you have old GPU (or drivers), Vulkan will not work and QMPlay2 switches to OpenGL.
I justed wanted to tell you, as I can't assess its effect. I don't mind the log entry. For me it looks like QMPLay2 wants to use Vulkan where it shouldn't want. However I don't have a GPU at all, it's onboard graphics from intel cpu from abt. 2017.
Do you have steps to reproduce or it happens after start with clean settings?
After start with clean settings. And also with the settings I mentioned in first post (I made them to rule out communication load, although 100% would be "a bit much" for that).
However I don't have a GPU at all, it's onboard graphics from intel cpu from abt. 2017.
It's iGPU (integrated GPU). If it's Intel 2017 it supports Vulkan for sure (but maybe Windows drivers have never been updated - Intel doesn't care; on Linux you should be able to use Vulkan, QMPlay2 + Vulkan runs nice on Intel Core 3rd gen on Linux, so much older hardware).
Do you have steps to reproduce or it happens after start with clean settings?
After start with clean settings. And also with the settings I mentioned in first post (I made them to rule out communication load, although 100% would be "a bit much" for that).
I don't have access to Windows 7, I disabled the GPU drivers in device manager (I have the same Vulkan error in logs) and it still has 0% CPU load at idle.
Please try in Renderer settings:
- select OpenGL manually and apply - the Vulkan error log should gone on QMPlay2 restart - does it still have 100% cpu core load?
- select legacy renderer manually and apply - does it still have 100% cpu core load?
Opening the renderer settings Renderer is already selected: Renderer: OpenGL (active). Switching that to something else, than back to OpenGL, then Apply and Close. QMPlay2 want's to start again: Still 100%.
Now enable "Use OpenGL on entire window" QMPlay2 want's to start again: Load gone. No log entry. ==> About there is the cause.
Now disable again. QMPlay2 want's to start again: Load still gone. ==> There seems to be something wrong too.
Close QMPlay manually. Start manually again: Load is at 100% again.
No log and no load for legacy entry.
Only at first switch to "Use OpenGL on entire window" there came a message about possible efficiency problems.
OK, all in all: What is the consequence?
Use OpenGL on entire window
I should remove this option, it should be avoided in most cases. QMPlay2 should decide automatically where it's needed.
If the legacy renderer doesn't cause 100% CPU load so I see that there's a problem with Intel OpenGL driver (as usual, Intel always have problem with their OpenGL driver). You can update Intel GPU driver to the newest (https://www.intel.com/content/www/us/en/search.html#sort=%40lastmodifieddt%20descending&f:@operatingsystem_en=[Windows%207%2C%2064-bit*]&f:@tabfilter=[Downloads]&f:@stm_10385_en=[Graphics,Processor%20Graphics,Intel%C2%AE%20HD%20Graphics%20Family] - choose correct driver for your CPU/iGPU).
But it's strange driver BUG, if you have "Use OpenGL on entire window' disabled the OpenGL is initialized, but it's used only when you play a video.
Thank you for providing the link to intel drivers! I d/l for HD Graphics 530. Maybe I'm a bit too timid, but I really would like not to change the running system. I probably won't be able to fix it again if it crashes.
So... there is a workaround for me to "Use OpenGL on entire window". (As long as you offer the option). But if you remove it then there will be no way for me to use but with 100% load. I'm at my way to migrate to openSUSE anyhow, but for some time I will be at Win7. So what will be the best solution... for me, and for you?
EDIT: Having to update the driver maybe shouldn't be a must; as your baby shouldn't produce 100% load if driver is not updated... right?
"Use OpenGL on entire window"
What if you disable this option and you'll have 100% CPU load and you play a video and stop - does it stop using 100% CPU core?
as your baby shouldn't produce 100% load if driver is not updated... right?
I don't know what is doing the 100% load - if it's QMPlay2 - I'll fix it, if it's Qt (a library I use) - it'll be more difficult to fix (for Windows 7 it's old version anyway), if it's inside the Intel driver - I can't do anything (I guess Qt calls some OpenGL functions on initialization which your Intel driver doesn't like).
OK, I disable "Use OpenGL on entire window". QMPlay automatically starts anew. However at the point note the effect that it is still no load as I said above. Only if then I close QMPlay2 manually, and then start again there will be the 100% in effect.
What if you disable this option and you'll have 100% CPU load and you play a video and stop - does it stop using 100% CPU core?
Surprise, surprise: It does indeed! (???) But closing and restarting QMPlay takes all of it again.
You're surely right not to do too much effort on this. If it should point to a bug in QMPlay... good luck... but if not I can very live the remaining months until finally dropping Win7. (Actually I only installed at Win to get experience and do some tests before finally using it at openSUSE wonderland) :)