konqueror sessions are not killed...

[Whitehawk Stormchaser]

On Saturday 22 November 2003 16:44, David Faure wrote:
> On Saturday 22 November 2003 14:29, Whitehawk Stormchaser wrote:
> > Greetings!
> > I have looked today in the ksysguard to see, what is happening there, and
> > I have been looking into the konqueror processes, and I was stunned to
> > find 158 processes running. Now sure, that that is nothing really
> > strange, but that is the status AFTER all the konqueror browsers were
> > closed...
> >
> > Is that normal? Probably the worst side effect of this is, that every
> > process burns about 19 megs of RAM... Isn't the process killed after konq
> > is shut down, and if so, why not?
>
> Sounds like a bug that's already fixed - but since you didn't tell your KDE
> version, it's hard to be sure...

I always forget that -- sorry... It's the CVS built today...

-- 
Unix is very simple, but it takes a genius to understand the simplicity.
(Dennis Ritchie)
---------------------
KDE XMame Wrapper: The KMameleon Project
http://designs.stormheart.com/kmameleon/

K Desktop Environment: "Best is opened"
http://www.kde.org/