| 2012-10-05 19:31:14 |
Carroarmato0 |
description |
Since the 1.2.2 release, I've noticed that whenever I start Lightread, my system gets dog slow.
When taking a look at what happens after Lightread gets started through htop (or just top), I've noticed that the normal X process
( /usr/bin/X :0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch -background none ) skyrockets to 100% cpu usage. Every time.
The system keeps a high load right until Lightread finishes loading all the feeds.
After Lightread is ready, normal usage of Lightread seems to also have regressed in terms of speed, requiring a lot of work for X. |
Since the 1.2.2 release, I've noticed that whenever I start Lightread, my system gets dog slow.
When taking a look at what happens after Lightread gets started through htop (or just top), I've noticed that the normal X process
( /usr/bin/X :0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch -background none ) skyrockets to 100% cpu usage. Every time.
The system keeps a high load right until Lightread finishes loading all the feeds.
After Lightread is ready, normal usage of Lightread seems to also have regressed in terms of speed, requiring a lot of work for X.
Update:
When the problem occurred, I was using the officially provided Nvidia driver (made a clean reinstall yesterday of Ubuntu).
I removed the Nvidia driver, so that by default Ubuntu would switch over to the nouveau driver. After a reboot and trying to start Lightread again, everything went very smoothly. No X taking 100% of the cpu.
Perhaps some changes were made in Lightread 1.2.2 which upset something in the graphics stack causing X to overwork. |
|
