GNOME Bugzilla – Bug 741546
evince and evince-thumbnailer stuck with high cpu load
Last modified: 2015-10-16 21:26:02 UTC
Created attachment 292743 [details] File that reproduces this problem. Both evince and evince-thumbnailer get stuck with high CPU load. It consumes also all the memory in my system. See also: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1386120 I attach a file that causes this to happen.
I attach a backtrace. When I killed the process, evince-thumbnailer had eaten all RAM memory and the system was starting to use swap. After I killed the process evince-thumnbailer survived in the background keeping all the memory, and I had to kill that process to free the memory again.
Created attachment 292744 [details] Stacktrace
GNU gdb (Ubuntu 7.8-1ubuntu4) 7.8.0.20141001-cvs Copyright (C) 2014 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from evince...Reading symbols from /usr/lib/debug//usr/bin/evince...done. done. (gdb) handle SIG33 pass nostop noprint Signal Stop Print Pass to program Description SIG33 No No Yes Real-time event 33 (gdb) set pagination 0 (gdb) run formules-[K2_eng.pdf Starting program: /usr/bin/evince formules2_eng.pdf [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7fc0d6230700 (LWP 14250)] [New Thread 0x7fc0d55c0700 (LWP 14251)] [New Thread 0x7fc0d4bbb700 (LWP 14294)] [New Thread 0x7fc0c7fff700 (LWP 14334)] [New Thread 0x7fc0ba1e2700 (LWP 14477)] [New Thread 0x7fc0b3bdd700 (LWP 14559)] [New Thread 0x7fc0b33dc700 (LWP 14562)] (evince:13778): Gtk-CRITICAL **: gtk_widget_show: assertion 'GTK_IS_WIDGET (widget)' failed (evince:13778): Gtk-CRITICAL **: gtk_widget_show: assertion 'GTK_IS_WIDGET (widget)' failed [Thread 0x7fc0d4bbb700 (LWP 14294) exited] [Thread 0x7fc0b33dc700 (LWP 14562) exited] [New Thread 0x7fc0b33dc700 (LWP 16850)] [New Thread 0x7fc0d4bbb700 (LWP 16851)] [New Thread 0x7fc0b24e3700 (LWP 16852)] [New Thread 0x7fc0b1ce2700 (LWP 16853)] [New Thread 0x7fc0b14e1700 (LWP 16854)] [New Thread 0x7fc0b0ce0700 (LWP 16855)] [New Thread 0x7fc0a3fff700 (LWP 16856)] [New Thread 0x7fc0a37fe700 (LWP 16857)] [New Thread 0x7fc0a2ffd700 (LWP 16858)] [Thread 0x7fc0b3bdd700 (LWP 14559) exited] [Thread 0x7fc0d4bbb700 (LWP 16851) exited] [Thread 0x7fc0b0ce0700 (LWP 16855) exited] [Thread 0x7fc0b1ce2700 (LWP 16853) exited] [Thread 0x7fc0a2ffd700 (LWP 16858) exited] [Thread 0x7fc0a37fe700 (LWP 16857) exited] [Thread 0x7fc0a3fff700 (LWP 16856) exited] [Thread 0x7fc0b24e3700 (LWP 16852) exited] [Thread 0x7fc0b14e1700 (LWP 16854) exited] [New Thread 0x7fc0b14e1700 (LWP 18231)] [New Thread 0x7fc0b24e3700 (LWP 18232)] [New Thread 0x7fc0a37fe700 (LWP 18233)] [New Thread 0x7fc0a3fff700 (LWP 18234)] [New Thread 0x7fc0d4bbb700 (LWP 18235)] [New Thread 0x7fc0b3bdd700 (LWP 18236)] [New Thread 0x7fc0b1ce2700 (LWP 18237)] [New Thread 0x7fc0b0ce0700 (LWP 18434)] [New Thread 0x7fc0a2ffd700 (LWP 18435)] [Thread 0x7fc0a3fff700 (LWP 18234) exited] [Thread 0x7fc0b24e3700 (LWP 18232) exited] [Thread 0x7fc0b14e1700 (LWP 18231) exited] [Thread 0x7fc0a37fe700 (LWP 18233) exited] [Thread 0x7fc0b0ce0700 (LWP 18434) exited] [Thread 0x7fc0d4bbb700 (LWP 18235) exited] [Thread 0x7fc0b1ce2700 (LWP 18237) exited] [Thread 0x7fc0b3bdd700 (LWP 18236) exited] [Thread 0x7fc0a2ffd700 (LWP 18435) exited] [New Thread 0x7fc0a2ffd700 (LWP 19024)] [New Thread 0x7fc0b3bdd700 (LWP 19025)] [New Thread 0x7fc0b1ce2700 (LWP 19026)] [New Thread 0x7fc0d4bbb700 (LWP 19027)] [New Thread 0x7fc0b24e3700 (LWP 19028)] [New Thread 0x7fc0b14e1700 (LWP 19029)] [Thread 0x7fc0b24e3700 (LWP 19028) exited] [Thread 0x7fc0b14e1700 (LWP 19029) exited] [Thread 0x7fc0b33dc700 (LWP 16850) exited] [Thread 0x7fc0a2ffd700 (LWP 19024) exited] [Thread 0x7fc0b1ce2700 (LWP 19026) exited] [Thread 0x7fc0b3bdd700 (LWP 19025) exited] [Thread 0x7fc0d4bbb700 (LWP 19027) exited] [New Thread 0x7fc0d4bbb700 (LWP 28213)] [Thread 0x7fc0d4bbb700 (LWP 28213) exited] Program received signal SIGINT, Interrupt. 0x00007fc0df43c2cd in poll () at ../sysdeps/unix/syscall-template.S:81 81 ../sysdeps/unix/syscall-template.S: No such file or directory. (gdb) bact[Kktrad[Kce full
+ Trace 234426
Thread 6 (Thread 0x7fc0ba1e2700 (LWP 14477))
A debugging session is active. Inferior 1 [process 13778] will be killed. Quit anyway? (y or n)
This does not seem to happen anymore with newer Evince/poppler (>3.18/0.37.0). Please, feel free to re-open this bug if you can see the issue with newer versions.