-
Notifications
You must be signed in to change notification settings - Fork 64
CPU consumption #268
Comments
That's a touch nut for those not fortunate enough to have a MacOS machine to reproduce this, such as us, scap-workbench developers. Unless any owner of such system helps us to nail this one down, we can't do anything about it. |
How can I help? What information can I provide? |
Try to execute the command in a console, and see whether there is any output that could point towards the cause. |
Ok, when I get some time later today, I'll take a look and see. It may be that the SCAP content is taking a while to load, but I'll test and see. |
So far, the app just shows an icon in the dock, with no foreground window. It's used about 12GB of memory according to Activity Monitor, and from the command line, only shows this:
I'm going to let it run some more to see if it ever comes up, or if it gets killed by the OOM killer or something. |
18GB and counting... |
A list of the open files and ports (from Activity Monitor)
|
The app showed 0 bytes written to disk, and only 44KB read from disk. I finally just killed it, since it didn't seem to be reading SCAP content from disk. |
I'm pretty sure this is a QT5 issue. There are numerous bugs out there with big sur and other QT apps. The app probably just need to be rebuilt with an update to QT for the big sur patching. I'm not skilled enough myself to make that happen, especially on a mac. |
Opening current release of scap-workbench on Mac OS 11.0.1 results in 100% cpu consumption and an unresponsive app.
The text was updated successfully, but these errors were encountered: