Bug 151128 - Memory leak occurs in KPDF when searching for a word not present in a large file
Summary: Memory leak occurs in KPDF when searching for a word not present in a large file
Status: RESOLVED DUPLICATE of bug 149232
Alias: None
Product: kpdf
Classification: Applications
Component: general (show other bugs)
Version: 0.5.8
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Albert Astals Cid
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-10-21 12:18 UTC by Chandra Sekar
Modified: 2007-10-21 13:10 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Chandra Sekar 2007-10-21 12:18:59 UTC 
Version:           0.5.8 (using KDE KDE 3.5.8)
Installed from:    Ubuntu Packages
OS:                Linux

When I open large PDF files and search for a text which is not present in it, KPDF consumes too much of memory to the extent of making the system freeze temporarily. This does not happen for smaller files or if the text is found near the current position.

My memory settings in KPDF is set to "Normal".

While KPDF as a whole is a slick PDF viewer (even better than Adobe's), this memory leak makes it difficult to use it when I need to quickly refer to some particular text in a large PDF file
Comment 1 Pino Toscano 2007-10-21 12:28:01 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.
Comment 2 Chandra Sekar 2007-10-21 12:43:51 UTC 
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.
Comment 3 Pino Toscano 2007-10-21 12:48:51 UTC 

*** This bug has been marked as a duplicate of 101701 ***
Comment 4 Chandra Sekar 2007-10-21 12:51:25 UTC 
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.
Comment 5 Pino Toscano 2007-10-21 13:05:09 UTC 
Wrong duplicate bug...
Comment 6 Pino Toscano 2007-10-21 13:05:23 UTC 

*** This bug has been marked as a duplicate of 149232 ***
Comment 7 Chandra Sekar 2007-10-21 13:10:23 UTC 
Ha thanks.  That is a real duplicate.  Somehow that bug didn't show up in the wizards list.

Sorry for reporting a duplicate bug!  :-)