Summary: | Memory leak occurs in KPDF when searching for a word not present in a large file | ||
---|---|---|---|
Product: | [Applications] kpdf | Reporter: | Chandra Sekar <chandru.in> |
Component: | general | Assignee: | Albert Astals Cid <aacid> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | 0.5.8 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Chandra Sekar
2007-10-21 12:18:59 UTC
It seems you confuse "memory leak" with "(large) memory consumption". In case it is really a memory leak, do you have a valgrind log that could show us the leak? And, the blocking search is already reported in bug #101701. I'm not sure about whether it is a leak or a huge consumption. I don't have a valgrind log. All I see is a sudden surge in the memory usage of my system, which becomes normal when kpdf is killed. So I know kpdf is the culprit. Also, everything is normal till I start a normal search. The other bug is speaking about quick search and its synchronous nature. Mine is about normal search and huge memory usage/leak. I dunno if the same fix can solve both. But fundamentally they seem to be different. *** This bug has been marked as a duplicate of 101701 *** Could you please tell why this has been marked a duplicate of a report which has nothing to do with memory consumption? As far as I can see, the two issues don't seem to be related. Wrong duplicate bug... *** This bug has been marked as a duplicate of 149232 *** Ha thanks. That is a real duplicate. Somehow that bug didn't show up in the wizards list. Sorry for reporting a duplicate bug! :-) |