kpdf dev anyone?

dario balozzi dbalozzi at gmail.com
Fri Mar 14 15:41:34 CET 2008


On Fri, Mar 14, 2008 at 2:28 PM, Sebastian Kuegler <sebas at kde.org> wrote:
> On Friday 14 March 2008 14:44:44 dario balozzi wrote:
>  > On Fri, Mar 14, 2008 at 11:54 AM, Sebastian Kuegler <sebas at kde.org> wrote:
>  > > On Friday 14 March 2008 11:27:07 dario balozzi wrote:
>  > >  > i was a little misinformed about the kpdf->okular thing  ( i use an
>  > >  > old version of Pardus linux  that came with kpdf )
>  > >  >
>  > >  > i will try in okular mailing list or irc channel
>  > >
>  > >  Or maybe have a look at Okular first, it might address your issue (the
>  > > one you're not telling us :-)).
>  > >
>  > :-)))
>  >
>  > i open a 2293 page PDF [1] , do a search on the document and this
>  > operation results in a machine freeze  ( too much memory usage .. the
>  > hard disk keep running and running , i lose control of the GUI and
>  > have to reset ) ( AMD Athlon 2.2GHZ 512 MB RAM, 1GB swap, 30GB hd free
>  > space , Pardus Linux 2007.2 with KDE 3.5.7 )
>
>  It does work here with KPDF from 3.5.8, but this machine has 2.5 GB of RAM,
>  searching for "body" takes about 20 seconds.

try to search a non existent term

> You can setup KPDF's memory
>  usage pattern in the config dialogue, not sure if it changes a lot though.

thanks for that, i will try some tunning

>  Did you try other PDF readers, btw?
>

Evince: takes ~2 min to scan the entire document ( and don't freeze my PC )
Acrobat Reader :  ~ Evince times and performance

>...
>  Hehehe, Urghs. The meaning of that huge document is probably not to have
>  people read it, but to have people ignore it,

you are absolutely right

  --dario


More information about the kde-quality mailing list