On Mon, 2004-11-29 at 11:36 -0500, Noah Silva [Mailing list] wrote:
> Forgot some ...
> a. I have had performance problems and found some applications using an
> ENORMOUS amount of memory. Evolution was taking nearly 400mb at one
> I can't be the only one who's noticed this.
I see this with the out of date version of Evolution I am running
(evolution-1.5.93-2) on an FC2 system:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
20276 kms 16 0 330m 135m 34m S 0.0 35.9 40:43.51 evolution
I will be upgrading to FC3 soon, and I hope that will reducing things.
The memory usage appears to grow with time, and is directly related to
the number of messages per folder on my remote IMAP server (Dovecot on
another FC2 system).
This is bad since I have some folders with many many thousands of messages
(like the account used for this list). You'd think if I don't even go to
a message it wouldn't be saving that much info about it.
At any rate, I didn't seem to have this problem with 1.5. I mean... I
have 1 GB of ram on this machine, it is kind-of irritating when it goes
into a swapping frenzy because... email and web browsing is too much for
> b. In evolution, in the calendar, the scrolling seems not to
> It won't scroll until I go 4 or 5 blocks (in the month view) and then it
> will suddenly jump. Should this be files with Novell or Redhat? This
> seems to happen not on my rawhide machine. (Also sometimes entries don't
> update properly until restarting evo.)
Again, I see this with my 1.5.x evolution, but on my laptop (FC2
evolution-2.0.1-2) the calendar works much better, but I still get the
odd scrolling problem, like you describe, in the month view.
I've never had the problem in 1.5. But - I only ever use the month view.
I saw it on the 2.0 betas that were in the FC3 tests (1.6?), but I can't
believe that made it to release.
Dave Malcolm should be able to let you know where to raise the bugs.
When you do create bugs, please let me know and I'll add my experiences.
ok, I am going to have a look on Novell's site for now, since I know the
new redhat policy is to get things fixed upstream as much as possible.