Summary: | Large, persistent X virtual memory usage | ||
---|---|---|---|
Product: | [Applications] okular | Reporter: | Benoît Jacob <jacob.benoit.1> |
Component: | general | Assignee: | Okular developers <okular-devel> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Benoît Jacob
2009-10-06 04:10:55 UTC
Yes, we use X memory to cache rendering results, if X doesn't recover his memory after we stop using it, i think you'll agree it is X fault not ours. If you can provide evidence we are not freeing all the QPixmaps we crate we will be happy to investigate. Basically this bug is duplicate from the others that complain about X memory usage, don't have to find them right now. Sure, I understand. As I said at the bottom, it really seems that Okular _IS_ freeing all the pixmaps that it uses. I was just wondering if Okular did anything wrong, to get X to use as much as 1500M memory. If it's just a X bug, so be it. Feel free to close as invalid. *** This bug has been marked as a duplicate of bug 177213 *** |