Hi All: El Miércoles, 5 de Mayo de 2010, Mark Purcell escribió: > On Wednesday 05 May 2010 10:38:46 Francesco wrote: > > The program start using even more ram; it stops only when killed or when > > swap is full and thus other programs are affected by crash > > Francesco, > > Sounds like an upstream problem. > > You may have better response via bugs.kde.org. > > Mark
Well, KVIrc it's not part of what's now called KDE SC (software compilation), but rather developed by a separated group of people [0], anyway Mark is right. This looks like an upstream problem. Unfortunately the information you provide is not enough to file a new bug report against KVIrc [1]. It looks like an infinite loop starving machine resources. However you can provide more information answering these questions: · When do you experience the problem? · Do you have any automatic connection to servers on startup? · Could you try moving the KVIrc config dir which is usually ~/.kvirc or ~/.config/kvirc elsewhere and retry? Whereever it works or not you can safely remove the newly created dir an move the old back to the original place, restoring your usual configuration. · Depending on your knowledge, could you try installing kvirc-dbg package, starting kvirc and then getting a backtrace of the loop. Hint: gdb -p $(pidof kvirc) and then bt from the gdb command line. Thanks for help. Regards, [0] http://kvirc.net [1] https://svn.kvirc.de/kvirc/ -- Raúl Sánchez Siles ----->Proud Debian user<----- Linux registered user #416098
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ pkg-kde-extras mailing list pkg-kde-extras@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-kde-extras
