8
« on: September 21, 2024, 04:54:03 pm »
Been using Paul's latest QT6 with Dooble successfully as a Win11 VirtualBox 7.1.0 guest in ArcaOS 5.1 for awhile, with Remy's script and acpi powerman disabled it works the best it ever has. But it is not perfect. Never had a system hang yet, rarely a Dooble hang, very occasionally a silent exit, but the biggest problem I see is having a web page (usually heavy javascript) stop rendering, the mouse scroll wheel stops working (although I can grab the scroll bar with the mouse and scroll) and one of the 4 CPU's will show 100% and pass that 100% back and forth among the 4 CPU's. The system keeps working no problem, but Dooble at that point is no longer usable and I have to close it. Then start it again, go back to the same page and it works fine.
Does this seems like some kind of 'timing' or 'deadlock' issue? I'm curious if anyone else sees this phenomenon, and wonder what might cause it.
Regards,