https://bugs.kde.org/show_bug.cgi?id=388854
--- Comment #31 from Rooty <zy...@gmx.us> --- (In reply to Albert Astals Cid from comment #28) > I'm not going to answer further in this bug because i don't feel compelled > to have a discussion with people that saying things like "no way a 90kb PDF > can take XX Mb of memory" as if they knew anything about they are talking > about. > > *BUT* this may actually be a manifestation of "glibc is useless and doesn't > actually free memory when you tell it to" that i workarounded at > https://cgit.kde.org/okular.git/commit/ > ?id=95bc29a76fc1f93eaabe5383d934644067dfc884 > > If this is the case one may need to add more malloc_trim around and not only > when the document is closed, but i totally don't feel like being dragged to > discuss with people that have no clue what they're talking about and have no > respect for people that give them stuff for free. "no respect for people that give them stuff for free"? "don't know what you're talking about"? for real? i meant no disrespect, i don't even use okular but i was trying to direct you to something that clearly bears closer examination. there are a myriad of other PDF readers out there we could be using but we're still here, reporting bugs/problems in okular. think long and hard about what that means with respect to the appreciation we show for the software you make. that being said, all of this is a moot point. it's taking up a lot more RAM than any other PDF reader (i'll leave you to decide whether that's appropriate). i'm sorry i can't help you out more, i know how to report a bug, but the diagnostics is beyond me (not an IT guy). thanks @Tobias for fleshing it out -- You are receiving this mail because: You are watching all bug changes.
