Version: 0.5.5 (using KDE KDE 3.5.5) Installed from: Gentoo Packages Compiler: version gcc 4.1.1 (Gentoo 4.1.1-r3) Configuré avec: /var/tmp/portage/gcc-4.1.1-r3/work/gcc-4.1.1/configure --prefix=/usr --bindir=/usr/i686-pc-linux-gnu/gcc-bin/4.1.1 --includedir=/usr/lib/gcc/i686-pc-linux-gnu/4.1.1/include --datadir=/usr/share/gcc-data/i686-pc-linux-gnu/4.1.1 --mandir=/usr/share/gcc-data/i686-pc-linux-gnu/4.1.1/man --infodir=/usr/share/gcc-data/i686-pc-linux-gnu/4.1.1/info --with-gxx-include-dir=/usr/lib/gcc/i686-pc-linux-gnu/4.1.1/include/g++-v4 --host=i686-pc-linux-gnu --build=i686-pc-linux-gnu --disable-altivec --enable-nls --without-included-gettext --with-system-zlib --disable-checking --disable-werror --enable-secureplt --disable-libunwind-exceptions --disable-multilib --disable-libmudflap --disable-libssp --disable-libgcj --enable-languages=c,c++,fortran --enable-shared --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu OS: Linux i download a file le_c.zip. i open this with ark. i make double clic on pdf file inside the .zip i search (scroll down with my mouse) a paragraph. more i scroll down more my memory go down and swap use more and more. when swap is full, kpdf crash. i try this another this. If i scroll down fast, when my memory is full (not the swap memory) kpdf crash immediately. I make a pdf with OOo and i compress this. it's the same thing, kpdf crash (sorry for my poor english)
Does KPDF crashes when opening the very same PDFs but from disk (e.g. when they are extracted)? Could you provide the backtrace of the crash?
yes it crash with the same PDF on disk (ftp://ftp2.developpez.biz/developpo/c/tutoriels/le_c.zip if you want to try) how can i provide you the backtrace ?
Here it works correctly (ie no crash, both both the extracted PDF and directly from ark). The backtrace is what you can get from the KDE crash dialog, clicking on the 'Backtrace' tab (you need to install 'gdb' to get it).
gdb is installing but no KDE crash dialog :/
try this: - Open kpdf and go to Settings -> Configure KPDF -> Performance and uncheck Enable background generation (this will give a better backtrace). - Close kpdf - Open a shell and type "gdb kpdf" - Type "run" - Open the pdf file and wait it to crash - Write "bt" - Paste it here
(gdb) run Starting program: /usr/kde/3.5/bin/kpdf Failed to read a valid object file image from memory. (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1231653200 (LWP 10136)] Couldn't get registers: Aucun processus de ce type. (gdb) bt Cannot fetch general-purpose registers for thread -1231653200: generic error
We can't do much with this backtrace. You should re-emerge kdegraphics or kpdf (whatever ebuild you chose) and use the 'debug' use flag for that. Also make sure the nostrip feature is in /etc/make.conf .
Any updates about this bug? Does it happen with a newer KPDF version?
Closing the bug as worksforme as as far as i remember this was happening because both KPDF and Ark had a class that had the same name and when one was loaded inside the other weird things happended. We fixed this so it should not be crashing anymore. Anyway KPDF is no longer maintained, so if you still have problems in this regard when using Okular (KPDF successor) please open a bug against it.