In the meantime (actually nearly a year ago), log parsing was rewritten
and now does de-duplication instantly. This should reduce memory usage a
lot - my experience is that especially large lots have lots of
duplication included.
I also removed some intermediate steps in the chain from logfile to aa-
logprof questions, which means less intermediate variables/arrays that
eat quite some memory.
The new log parsing is currently only in git master (not in 2.13.x). It
will be included in the next major release (probably 3.0).
Processing / asking about the log events one by one (instead of reading
the whole log first) would in theory save even more memory. However,
IMHO it would make the user experience worse because it would also mean
loosing the ability to sort the questions aa-logprof asks by profile and
rule type.
Therefore I'm closing this bug as "mostly fixed" ;-) - if you still see
aa-logprof eating too much memory, feel free to open a new bug.
** Changed in: apparmor
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/387657
Title:
aa-logprof: doesn't handle large logs
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/387657/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
