Martin, yeah, after I started looking into the other bug (among other things) is when I noticed finally that syslog was that big. After logrotate had moved the log on (and I'd made a snapshot of it just in case :) ) I did verify that apport was functioning fine with more reasonable sized log files.
So that led me to think, perhaps apport should have a prompt to let the submitter know that a log file is above a certain size... I don't know if that would be an arbitrary size or perhaps a calculated percentage of available RAM, and then warn the user that the log file is too big, and provide a mechanism to skip the upload of that one file. Perhaps that could provide a message that would point the user to the specific file being skipped and maybe the advice to copy the log and trim out unnecessary stuff before manually adding it to the bug the user opened. Anyway, it was a thought I had... not sure if what I encountered is something that would be encountered often enough to make that added functionality worthwhile... though I CAN easily see this being a good idea for some things, like .xsession-errors. On my system with the nVidia GT240M card, I have to routinely delete .xsession-errors as it very quickly grows to hundreds of gigabytes in size. It got to the point where I just had cron delete the file every week. Anyway, I digress, that was but an example. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/984256 Title: recent_logfile() causes a huge memory leak for large log files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/984256/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
