The load of the system refers to the total number of processes that are running and ready to run. When a process is runnable, it is in a run queue and competes with other runnable processes for CPU time. In Linux, the process is divided into three states, one is the blocked process (waiting for I/O device data or system adjustment), one is the runnable process, and the other is the running process.
If I build a newer version of Qt (> 4.8), which version should I use? I'll build non-debug versions next week to see if the problem goes away with optimized libraries. I've been using the debug builds of Qt and Qwt during my testing. Here is a screenshot illustrating the font-size difference: If I noticed the font size of the lower button shrink significantly when the font of the top button stayed the same, I always saw excessive cpu usage. caQtDM used a normal amount of cpu most of the times that I stopped. I slowly reduced the size of test.ui in both dimensions, stopping frequently to check the cpu usage of caQtDM. The problem still exists when I use commit d1a7c25. Reply to this email directly, view it on GitHub, or mute the thread. You are receiving this because you commented. It only takes the single resize event for the CPU usage to spike and the memory to begin leaking. This is the ui file after the resize event: This is the ui file before the resize event: I include the output of the ldd command in my script that starts gdb so I can confirm I'm using the correct shared libraries. I built Qt 4.8.7 and Qwt 6.1.3 locally, with debugging on (otherwise the gdb backtrace isn't helpful). I started fresh on a different linux machine.
2017 à 00:13, Kevin Peterson > a écrit :Įverything has been rebuilt. I think that solves the problem, but probably it should be done in another way I made a dirty correction in order to prevent firing of resize events for one pixel difference in size.
0 kommentar(er)
