Bug#645961: [Segnalazioni] Bug#645961: xulrunner-7.0: Iceweasel/icedove eats 100% cpu after closing
Alle 08:26 di giovedì 20 ottobre 2011, Mike Hommey ha scritto: > On Thu, Oct 20, 2011 at 12:58:30AM +0200, Iacopo Spalletti wrote: > > Package: xulrunner-7.0 > > Version: 7.0.1-4 > > Severity: normal > > > > Dear Maintainer, > > *** Please consider answering these questions, where appropriate *** > > > >* What led up to the situation? > >* What exactly did you do (or not do) that was effective (or > > > > ineffective)? > > > >* What was the outcome of this action? > >* What outcome did you expect instead? > > > > *** End of the template - remove these lines *** > > > > When i close xulrunner applications (I tested only icedove / iceweasel, > > but i guess it's a xulrunner problem) program windows close but the > > processes remain active and eats 100% cpu time. > > This behaviour occurs on different profiles / different PCs (tested on a > > desktop and a laptop, both 64bit unstable, 1 AMD based, 1 Intel based). > > This occurs even on a empty profile (or in safe mode) just opening the > > default page (about:home). > > Apparently this don't cause any dataloss or any error in profile data, > > but it's quite annoying as it makes opening new browser session > > impossibile. How can i debug this situation further and provide more > > info? > > Are you using the Gtk engine that uses the Qt/KDE theme? > > Mike That was the problem! Thanks for pointing me in the right direction: i was using Qt4 Gtk theme; changed to QtCurve and the problem is gone. I'll check bug reports for gtk theme. Feel free to close this bug. I'll reopen against the theme. -- Regards Nephila sas PGP key block: http://www.nephila.it/pgp -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#645961: xulrunner-7.0: Iceweasel/icedove eats 100% cpu after closing
On Thu, Oct 20, 2011 at 12:58:30AM +0200, Iacopo Spalletti wrote: > Package: xulrunner-7.0 > Version: 7.0.1-4 > Severity: normal > > Dear Maintainer, > *** Please consider answering these questions, where appropriate *** > >* What led up to the situation? >* What exactly did you do (or not do) that was effective (or > ineffective)? >* What was the outcome of this action? >* What outcome did you expect instead? > > *** End of the template - remove these lines *** > > When i close xulrunner applications (I tested only icedove / iceweasel, but i > guess it's a xulrunner problem) program windows close but the processes remain > active and eats 100% cpu time. > This behaviour occurs on different profiles / different PCs (tested on a > desktop and a laptop, both 64bit unstable, 1 AMD based, 1 Intel based). > This occurs even on a empty profile (or in safe mode) just opening the default > page (about:home). > Apparently this don't cause any dataloss or any error in profile data, but > it's > quite annoying as it makes opening new browser session impossibile. > How can i debug this situation further and provide more info? Are you using the Gtk engine that uses the Qt/KDE theme? Mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#645961: xulrunner-7.0: Iceweasel/icedove eats 100% cpu after closing
Package: xulrunner-7.0 Version: 7.0.1-4 Severity: normal Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these lines *** When i close xulrunner applications (I tested only icedove / iceweasel, but i guess it's a xulrunner problem) program windows close but the processes remain active and eats 100% cpu time. This behaviour occurs on different profiles / different PCs (tested on a desktop and a laptop, both 64bit unstable, 1 AMD based, 1 Intel based). This occurs even on a empty profile (or in safe mode) just opening the default page (about:home). Apparently this don't cause any dataloss or any error in profile data, but it's quite annoying as it makes opening new browser session impossibile. How can i debug this situation further and provide more info? -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (200, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-2-amd64 (SMP w/3 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xulrunner-7.0 depends on: ii libasound21.0.24.1-4 ii libatk1.0-0 2.2.0-2 ii libbz2-1.01.0.5-7 ii libc6 2.13-21 ii libcairo2 1.10.2-6.1 ii libdbus-1-3 1.5.8-1 ii libevent-1.4-21.4.14b-stable-1 ii libfontconfig12.8.0-3 ii libfreetype6 2.4.6-2 ii libgcc1 1:4.6.1-15 ii libgdk-pixbuf2.0-02.24.0-1 ii libglib2.0-0 2.28.8-1 ii libgtk2.0-0 2.24.7-1 ii libhunspell-1.3-0 1.3.2-4 ii libjpeg8 8c-2 ii libmozjs7d7.0.1-4 ii libnotify40.7.4-1 ii libnspr4-0d 4.8.9-1 ii libnss3-1d3.12.11-3 ii libpango1.0-0 1.29.4-1 ii libpixman-1-0 0.22.2-1 ii libreadline6 6.2-7 ii libsqlite3-0 3.7.8-1 ii libstartup-notification0 0.12-1 ii libstdc++64.6.1-15 ii libvpx0 0.9.7.p1-2 ii libx11-6 2:1.4.4-2 ii libxext6 2:1.3.0-3 ii libxrender1 1:0.9.6-2 ii libxt61:1.1.1-2 ii zlib1g1:1.2.3.4.dfsg-3 xulrunner-7.0 recommends no packages. Versions of packages xulrunner-7.0 suggests: ii libcanberra0 0.28-2 ii libdbus-glib-1-2 0.98-1 ii libgnomeui-0 2.24.5-2 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
