Jason Tackaberry wrote:
> On Tue, 2009-01-27 at 18:36 +0100, Duncan Webb wrote:
>> The CPU is running at 80% which is way to much.
>
> Wow. When the UI is otherwise idle, anything over 2% is too much.
>
>
>> The poll time is set to 200 ms, which is much higher than I would
>> normally use (50 m
On Tue, 2009-01-27 at 18:36 +0100, Duncan Webb wrote:
> The CPU is running at 80% which is way to much.
Wow. When the UI is otherwise idle, anything over 2% is too much.
> The poll time is set to 200 ms, which is much higher than I would
> normally use (50 ms).
If nothing else is going on (e.g
Jason Tackaberry wrote:
> On Mon, 2009-01-26 at 19:50 +0100, Duncan Webb wrote:
>> The first stop-stopper is that the CPU usage is very high when freevo is
>> idle.
>>
>> Wonder if anyone knows how to find out what the problem could be?
>> Profiling the code also crashes, so that didn't help much.
On Mon, 2009-01-26 at 19:50 +0100, Duncan Webb wrote:
> The first stop-stopper is that the CPU usage is very high when freevo is
> idle.
>
> Wonder if anyone knows how to find out what the problem could be?
> Profiling the code also crashes, so that didn't help much.
There's no substitute for a w
Hi all,
I've been examining how Freevo-1 is running under Python-2.6.x.
The first stop-stopper is that the CPU usage is very high when freevo is
idle.
Wonder if anyone knows how to find out what the problem could be?
Profiling the code also crashes, so that didn't help much.
The next problem is
