Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#10780 - Liferea use 100% of CPU and crash when I close it
Attached to Project:
Arch Linux
Opened by Maximilien Cuony (the_glu) - Sunday, 29 June 2008, 21:52 GMT
Last edited by Eric Belanger (Snowman) - Friday, 22 May 2009, 21:44 GMT
Opened by Maximilien Cuony (the_glu) - Sunday, 29 June 2008, 21:52 GMT
Last edited by Eric Belanger (Snowman) - Friday, 22 May 2009, 21:44 GMT
|
DetailsDescription:
Some times (after a moment of use, no particular actions with it), lifera use 100% of CPU (but he is stil working). When I want to close it, icon disaper, his windows appear but dosen't respond. After a second click on the close buton, he crash. I have this errors in .xsession-errors : (liferea:7871): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed ** (liferea:7871): WARNING **: mozsupport_get_zoom(): Could not retrieve browser... (liferea:7871): Gtk-CRITICAL **: gtk_tree_view_get_selection: assertion `GTK_IS_TREE_VIEW (tree_view)' failed (liferea:7871): Gtk-CRITICAL **: gtk_tree_selection_unselect_all: assertion `GTK_IS_TREE_SELECTION (selection)' failed ** ** ERROR:(node.c:515):node_foreach_child_full: assertion failed: (NULL != node) |
This task depends upon
screenkey.c
ERROR: No output during decompression
too.
The 100% CPU use seems to be related to xulrunner 1.9: http://liferea.blogspot.com/2008/07/serious-problems-with-xulrunner-19.html
Crash on exit: http://sourceforge.net/tracker/index.php?func=detail&aid=2017269&group_id=87005&atid=581684
They'll probably make a new release once they figured them out. Still, I'll look if there are patches out there.
I will use liferea-webkit for some days and tell you if the problem still occur...
Version 1.4.28 (Stable)
* Adds a possible fix for the 100% CPU issues by settings
places.frecency.updateIdleTime to 0.
(suggested by Axel Beckert)