Description of problem: The PackageKit-browser-plugin white boxes stop appearing on reopened pages. It shows nothing in the place of the boxes. Version-Release number of selected component (if applicable): Clean installation of Fedora 12. rpm -qa \*PackageKit\* PackageKit-0.5.4-0.4.20091029git.fc12.i686 PackageKit-gtk-module-0.5.4-0.4.20091029git.fc12.i686 PackageKit-browser-plugin-0.5.4-0.4.20091029git.fc12.i686 PackageKit-yum-plugin-0.5.4-0.4.20091029git.fc12.i686 PackageKit-gstreamer-plugin-0.5.4-0.4.20091029git.fc12.i686 PackageKit-yum-0.5.4-0.4.20091029git.fc12.i686 PackageKit-glib-0.5.4-0.4.20091029git.fc12.i686 PackageKit-device-rebind-0.5.4-0.4.20091029git.fc12.i686 How reproducible: Everytime. Sometimes it crashes firefox. Steps to Reproduce: 1. open http://www.packagekit.org/temp/ 2. click on test.html It should open 4 packagekit object boxes. 3. Click on the back button 4. click on test.html again It will show a clean page. Actual results: Starting in the second time you reopen a page with packagekit objects it will show nothing. Needs to restart firefox to work again. Expected results: The boxes would appear everytime. Additional info: Sometimes, it crashes firefox.
It always crashes firefox on my system. See the abrt trace posted in BZ #547113
Adding here the report of the crash. It happens all the times now: Running firefox from valgrind having the following tabs: https://bugzilla.redhat.com/show_bug.cgi?id=547578 https://bugzilla.redhat.com/show_bug.cgi?id=547113 www.packagekit.org/temp/test.html [hugo@ganesha ~]$ valgrind firefox > /tmp/valgrind.log 2> /tmp/valgrind.err [hugo@ganesha ~]$ cat /tmp/valgrind.log ** (firefox:11443): DEBUG: installed firefox;3.5.5-1.fc12;i686;installed Mozilla Firefox Web browser ** (firefox:11443): DEBUG: available kdeedu;4.3.3-2.fc12;i686;updates Educational/Edutainment applications ** (firefox:11443): DEBUG: available gnubg;1:0.9.0.1-8.fc12;i686;fedora A backgammon game and analyser ** (firefox:11443): DEBUG: available f-spot;0.6.1.5-1.fc12;i686;updates Photo management application [hugo@ganesha ~]$ cat /tmp/valgrind.err ==11428== Memcheck, a memory error detector ==11428== Copyright (C) 2002-2009, and GNU GPL'd, by Julian Seward et al. ==11428== Using Valgrind-3.5.0 and LibVEX; rerun with -h for copyright info ==11428== Command: firefox ==11428== ==11428== ==11428== HEAP SUMMARY: ==11428== in use at exit: 22,920 bytes in 794 blocks ==11428== total heap usage: 2,639 allocs, 1,845 frees, 80,248 bytes allocated ==11428== ==11428== LEAK SUMMARY: ==11428== definitely lost: 18 bytes in 1 blocks ==11428== indirectly lost: 0 bytes in 0 blocks ==11428== possibly lost: 0 bytes in 0 blocks ==11428== still reachable: 22,902 bytes in 793 blocks ==11428== suppressed: 0 bytes in 0 blocks ==11428== Rerun with --leak-check=full to see details of leaked memory ==11428== ==11428== For counts of detected and suppressed errors, rerun with: -v ==11428== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 14 from 8) ==11428== ==11428== HEAP SUMMARY: ==11428== in use at exit: 22,103 bytes in 756 blocks ==11428== total heap usage: 2,639 allocs, 1,883 frees, 80,105 bytes allocated ==11428== ==11428== LEAK SUMMARY: ==11428== definitely lost: 0 bytes in 0 blocks ==11428== indirectly lost: 0 bytes in 0 blocks ==11428== possibly lost: 0 bytes in 0 blocks ==11428== still reachable: 22,103 bytes in 756 blocks ==11428== suppressed: 0 bytes in 0 blocks ==11428== Rerun with --leak-check=full to see details of leaked memory ==11428== ==11428== For counts of detected and suppressed errors, rerun with: -v ==11428== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 14 from 8) ==11428== ==11428== HEAP SUMMARY: ==11428== in use at exit: 23,008 bytes in 799 blocks ==11428== total heap usage: 2,776 allocs, 1,977 frees, 83,557 bytes allocated ==11428== ==11428== LEAK SUMMARY: ==11428== definitely lost: 18 bytes in 1 blocks ==11428== indirectly lost: 0 bytes in 0 blocks ==11428== possibly lost: 0 bytes in 0 blocks ==11428== still reachable: 22,990 bytes in 798 blocks ==11428== suppressed: 0 bytes in 0 blocks ==11428== Rerun with --leak-check=full to see details of leaked memory ==11428== ==11428== For counts of detected and suppressed errors, rerun with: -v ==11428== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 14 from 8) ==11428== ==11428== HEAP SUMMARY: ==11428== in use at exit: 22,185 bytes in 761 blocks ==11428== total heap usage: 2,776 allocs, 2,015 frees, 83,420 bytes allocated ==11428== ==11428== LEAK SUMMARY: ==11428== definitely lost: 0 bytes in 0 blocks ==11428== indirectly lost: 0 bytes in 0 blocks ==11428== possibly lost: 0 bytes in 0 blocks ==11428== still reachable: 22,185 bytes in 761 blocks ==11428== suppressed: 0 bytes in 0 blocks ==11428== Rerun with --leak-check=full to see details of leaked memory ==11428== ==11428== For counts of detected and suppressed errors, rerun with: -v ==11428== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 14 from 8) (firefox:11443): GLib-WARNING **: g_set_prgname() called multiple times GLib-ERROR **: gmem.c:136: failed to allocate 40 bytes aborting... /usr/lib/firefox-3.5.5/run-mozilla.sh: line 131: 11443 Aborted "$prog" ${1+"$@"} [hugo@ganesha ~]$
This bug has been triaged Steven M. Parrish KDE & Packagekit Triager Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
What info is needed in this ticket? I see (NEEDINFO) in the title.
I'm also seeing OOM failures with the plugin now, specifically that make firefox go boom. I'm pretty certain the plugin is correct, but it's something to do with the plugin loader.
IBM is still very interested in leveraging this feature but we're stalled because of this bug. Have we compared whether Firefox 3.5.x or Firefox 3.6.x is a determining factor in this crash? I've been using 64bit Firefox 3.5.x on my F12 x86-64 system.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
There's another bug crashing firefox actually which is already reported. So, i am closing this one.