David Abrahams wrote: > on Mon Mar 03 2008, Brad Anderson <brad-AT-dsource.org> wrote: > > >> We didn't figure out what part of Trac triggered this within Python, >> but I thought I'd mention it for this thread. I had always assumed it >> was my use of a CentralDatabaseManager customization that I've made to >> the Trac code base. You're talking about high memory usage, and not >> so much CPU, so I don't know if it's related or not... >> > > We've also had periodic runaway Trac processes. I just had to kill this > one: > > PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND > 84924 www 4 20 0 116M 2848K kserel 0 40.0H 98.73% python > > This is with 0.11-dev. > >
If this happens again, please attach to the process with gdb before killing it. The backtrace could give a hint about what's going on. -- Christian --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to trac-dev@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
