| Summary: | gtk-qt engine causes Firefox to exit dirty and keep eating CPU when invoked from within KDE 4 on x86-64 | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Aragorn Son of Arathorn <stryder> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED WORKSFORME | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | balcaen.john, dmorganec, doktor5000, lmenut, marja11, stryder |
| Version: | 1 | Keywords: | USABILITY |
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | Errata | ||
| Source RPM: | gtk-qt-engine-1.1-5.r5.3.mga1.src.rpm | CVE: | |
| Status comment: | |||
Addendum : To exclude the possibility that one of the plugins is responsible for this, I have tried with all plugins disabled, as suggested by David W. Hodgins on alt.os.linux.mageia. However, this made things even worse. Firefox then no longer consumes as much CPU time after it is shut down in the normal way, but still remains resident in memory and even a SIGKILL won't terminate it. It still shows up in the process list, and not as a zombie, but as an active process, consuming about 4% CPU.
Aragorn Son of Arathorn
2011-11-11 15:21:12 CET
CC:
(none) =>
stryder Hi, thanks for reporting this bug. Dmorgan any idea ? CC:
(none) =>
dmorganec I can't reproduce here on my mageia 1 x86_64 :/ (& i do have a lot of plugins enabled/extensions enable :p ) CC:
(none) =>
balcaen.john @ Aragorn etc. Is this problem still there in fully updated mageia 1 with Firefox 9 ? Keywords:
(none) =>
NEEDINFO @ Aragorn Please reply to the question above within two weeks from now, to avoid this bug being closed as OLD. The problem persists. It is clearly not a Firefox coding problem, but a KDE problem. Firefox behaves perfectly normal when started in LXDE. (In reply to comment #6) > The problem persists. It is clearly not a Firefox coding problem, but a KDE > problem. Firefox behaves perfectly normal when started in LXDE. Thanks for replying. Unfortunately, the KDE maintainer can't reproduce this bug, so there is nothing he could do about it, now. I can't reproduce either, I'm writing this on a 64 bits laptop with Mageia 1 and KDE and I exit Firefox at least once a day, but this never happened to me (although it did happen twice with thunderbird, in my eyes a related program). There must be something very special about your system. Does FF have this behaviour, too, when you login as xguest and use and exit it then? (In reply to comment #7) > (In reply to comment #6) > > The problem persists. It is clearly not a Firefox coding problem, but a KDE > > problem. Firefox behaves perfectly normal when started in LXDE. > > Thanks for replying. No problem. ;-) > Unfortunately, the KDE maintainer can't reproduce this bug, so there is nothing > he could do about it, now. > I can't reproduce either, I'm writing this on a 64 bits laptop with Mageia 1 > and KDE and I exit Firefox at least once a day, but this never happened to me > (although it did happen twice with thunderbird, in my eyes a related program). > There must be something very special about your system. I believe that it's probably some a conflict between KDE/Qt on the one hand and the version of GTK+ that the Firefox and Thunderbird binaries are built against, which may not necessarily be the same GTK+ libraries as the ones used by other GTK+/Gnome applications on the system. > Does FF have this behaviour, too, when you login as xguest and use and exit it > then? As stated before, Marja, I do not have the xguest package installed. It was installed by default, but I removed it and deleted the account. ;-) (In reply to comment #8) > As stated before, Marja, I do not have the xguest package installed. It was > installed by default, but I removed it and deleted the account. ;-) A little voice told me this when I asked this question, although I wasn't sure about my memory ;) Anyway, do you mind doing one of the following: 1. make another account to try with, it doesn't necessarily need to be xguest 2. kill firefox, rename your .mozilla folder in your /home directory to .mozillaOLD and start Firefox again. And please tell whether you can reproduce this problem in either way. > I believe that it's probably some a conflict between KDE/Qt on the one hand and > the version of GTK+ that the Firefox and Thunderbird binaries are built > against, which may not necessarily be the same GTK+ libraries as the ones used > by other GTK+/Gnome applications on the system. @ John Balcaen @ DMorgan WDYT? nothing :/ (In reply to comment #9) > (In reply to comment #8) > > > As stated before, Marja, I do not have the xguest package installed. It was > > installed by default, but I removed it and deleted the account. ;-) > > A little voice told me this when I asked this question, although I wasn't sure > about my memory ;) Anyway, do you mind doing one of the following: > > 1. make another account to try with, it doesn't necessarily need to be xguest Tried that. Problem does NOT exist in the other account, BUT I have not done any customizing to the Firefox settings or to the KDE desktop in that other account. I have only created the account, logged into it, and launched Firefox, and then checked using the System Monitor. When I exited Firefox, the process exited cleanly. > 2. kill firefox, rename your .mozilla folder in your /home directory to > .mozillaOLD and start Firefox again. Tried that too, but the problem still persists there. As long as Firefox runs, everything is peachy, but as soon as I exit Firefox, it hogs up one of the two CPU cores to the max and sits there doing exactly that until I kill it with SIGKILL. So... I'm guessing that it has to do with a particular theme package in KDE, because the problem did NOT occur in the un-themed other account, and it also does not occur in LXDE. It's just a guess, and for what it's worth, I've ALWAYS had this problem in Mageia, ever since my first install and before the updates. It really puzzles me. So you don't use the default theme, but ? please give the output of $ rpm -qa | grep <theme> (so if you use oxygen: $ rpm -qa | grep oxygen ) @Marja, Well, I am using the Oxygen window decorations, with custom button positions, and I am using the Bespin theme, along with the Bespin X-bar widget, which requires being added to a panel at the top of the screen, and which then gives you the application menu for KDE-specific applications; it does not have any effect on GTK applications, because they do not support it - at least, not by way of the same mechanism, because Ubuntu's Unity interface is GTK-based and has the same feature but I don't know how Unity does it. It is either way a feature, now added to KDE 4 by way of the Bespin theme and its X-bar widget, that used to exist in KDE versions prior to 4.0, and it used to be called "Mac OS style menubar at the top of the screen". As for the command output you requested...: [22:47:55][localhost:/home/aragorn] [0][aragorn][$] > rpm -qa | grep bespin kde4-style-bespin-ksplash-0.1-0.1355svn.1.mga1 kde4-style-bespin-kdm-0.1-0.1355svn.1.mga1 kde4-style-bespin-0.1-0.1355svn.1.mga1 kde4-style-bespin-icons-0.1-0.1355svn.1.mga1 I was going to install your theme to see whether that would help me to reproduce your bug, but I'm to busy with more urgent things and can't restart FF atm. Do you have time to try logging in as aragorn and using a different theme? Or logging into that new account you made and using bespin there, too? (In reply to comment #14) > I was going to install your theme to see whether that would help me to > reproduce your bug, but I'm to busy with more urgent things and can't restart > FF atm. > > Do you have time to try logging in as aragorn and using a different theme? Or > logging into that new account you made and using bespin there, too? I've tried it with my other account. Set up Bespin there - but nothing too fancy yet, only selecting the theme without going over all the customization options, and at this point also still without the X-bar widget - and Firefox exits normally. I am stumped. :-/ P.S. : Sorry for the late reply. I have severe chronic health issues which may incapacitate me for days or weeks on end. :-/ (In reply to comment #15) > > I've tried it with my other account. Set up Bespin there - but nothing too > fancy yet, only selecting the theme without going over all the customization > options, and at this point also still without the X-bar widget - and Firefox > exits normally. I am stumped. :-/ > > P.S. : Sorry for the late reply. I have severe chronic health issues which may > incapacitate me for days or weeks on end. :-/ Outch! Please, if we close a bug report because we didn't get information we asked for, please reopen it as soon as you are fit enough to reply. (It might even happen to me, that I close one of your reports without giving you extra time to reply, not because I don't care about your health problems, but because my brain doesn't attach names (or faces) of people very well to who they are and how they are doing) Anyway, very best wishes for you and your health. What happens if you set up Bespin (one change at a time) to be like Bespin in your original account? (In reply to comment #16) > (In reply to comment #15) > > > > > I've tried it with my other account. Set up Bespin there - but nothing too > > fancy yet, only selecting the theme without going over all the customization > > options, and at this point also still without the X-bar widget - and Firefox > > exits normally. I am stumped. :-/ > > > > P.S. : Sorry for the late reply. I have severe chronic health issues which may > > incapacitate me for days or weeks on end. :-/ > > Outch! Please, if we close a bug report because we didn't get information we > asked for, please reopen it as soon as you are fit enough to reply. (It might > even happen to me, that I close one of your reports without giving you extra > time to reply, not because I don't care about your health problems, but because > my brain doesn't attach names (or faces) of people very well to who they are > and how they are doing) I understand that, Marja. ;-) > Anyway, very best wishes for you and your health. That is much appreciated. :-) > What happens if you set up Bespin (one change at a time) to be like Bespin in > your original account? I still have to try out that scenario. I've been thinking about it, and about possible changes which I have made to my main account's desktop configuration that could trigger this peculiar response from Firefox, but for the life of me, I see no logic in any of it. :-/ I will try to set it up like my regular account later. ;-) 2 wks extra(In reply to comment #17) > (In reply to comment #16) > > > What happens if you set up Bespin (one change at a time) to be like Bespin in > > your original account? > > I still have to try out that scenario. I've been thinking about it, and about > possible changes which I have made to my main account's desktop configuration > that could trigger this peculiar response from Firefox, but for the life of me, > I see no logic in any of it. :-/ > > I will try to set it up like my regular account later. ;-) Did you by any chance get around to trying that? (In reply to comment #18) > 2 wks extra(In reply to comment #17) > > (In reply to comment #16) > > > > > > What happens if you set up Bespin (one change at a time) to be like Bespin in > > > your original account? > > > > I still have to try out that scenario. I've been thinking about it, and about > > possible changes which I have made to my main account's desktop configuration > > that could trigger this peculiar response from Firefox, but for the life of me, > > I see no logic in any of it. :-/ > > > > I will try to set it up like my regular account later. ;-) > > Did you by any chance get around to trying that? Yep, did that. The only thing I have not done yet - but I don't think that this could possibly have any effect - is customize the color scheme. But I did set up the KDE session other account similar enough to this one, with the same theme, X-bar widget, et al. And in the other account, Firefox still behaves normally, but in this account here it does not. So whatever is causing it, it's not something that can be logically analyzed or reproduced. We've already tried with a blank ".mozilla" directory in my home directory, but the result is the same. As per David W. Hodgins request, I also tried disabling all plugins, and that made it even worse. With all the plugins disabled, even a SIGTERM wouldn't terminate Firefox anymore, and SIGKILL was needed. Thanks for all the feedback, Aragorn. So whatever causes it, it is related to that first account and it is not in .mozilla What happens when you move your .mozilla and all other important stuff to the new account and use that instead of the old account? (In reply to comment #20) > Thanks for all the feedback, Aragorn. > > So whatever causes it, it is related to that first account and it is not in > .mozilla > > What happens when you move your .mozilla and all other important stuff to the > new account and use that instead of the old account? Nothing spectacular. Firefox still behaves normally. It just doesn't make any sense. :-/ Thanks for replying, Aragorn. Since everything works now when you log in to your second account: Let's blame a flipped bit in or related to your first account and close this bug :) Of course, feel free to reopen when needed Status:
NEW =>
RESOLVED (In reply to comment #22) > Thanks for replying, Aragorn. You're welcome. ;-) > Since everything works now when you log in to your second account: > > Let's blame a flipped bit in or related to your first account and close this > bug :) > > Of course, feel free to reopen when needed It's that flipped bit that I'm worried about, Marja. As long as I don't know what causes it, I also don't know how to fix it. :-/ Please show the output of rpm -qa | grep gtk-qt CC:
(none) =>
doktor5000 [14:53:45][localhost:/home/aragorn] [0][aragorn][$] > rpm -qa | grep gtk-qt gtk-qt-kcm-1.1-5.r5.3.mga1 gtk-qt-engine-1.1-5.r5.3.mga1 lib64gtk-qt-engine-1.1-5.r5.3.mga1 Please remove all three of those and try again, gtk-qt-engine is the cause for many bugs in various applications and not maintained upstream. (In reply to comment #26) > Please remove all three of those and try again, gtk-qt-engine is the cause for > many bugs in various applications and not maintained upstream. Do you mean removal by way of rpm or urpmi? I don't know whether they might have dependencies and I don't want them to take half my system with them on their way out... Actually doesn't matter :) Just try via urpme gtk-qt-kcm gtk-qt-engine lib64gtk-qt-engine There should be no dependencies which are removed with this, as this is not in a default installation, as has been manually installed. You should keep gtk-qt-kcm; the problem is only with the gtk-qt engine (= gtk-qt-engine and lib64gtk-qt-engine). urpme gtk-qt-engine lib64gtk-qt-engine CC:
(none) =>
lmenut (In reply to comment #29) > You should keep gtk-qt-kcm; the problem is only with the gtk-qt engine (= > gtk-qt-engine and lib64gtk-qt-engine). > > urpme gtk-qt-engine lib64gtk-qt-engine Okay, that seems to have solved it. Firefox behaves normally this time. I suspected that it had something to do with Qt, but I didn't know where to look. Thanks guys. This bug is now officially closed, and if anyone has the same problem, you now know what fixed it. ;-) Thx for insisting :) Of course the gtk-qt engine isn't fixed, so I can't change the status of this bug to fixed Keywords:
NEEDINFO =>
(none)
Marja Van Waes
2012-02-12 19:22:17 CET
Source RPM:
firefox =>
gtk-qt-engine-1.1-5.r5.3.mga1.src.rpm
Manuel Hiebel
2012-02-12 20:42:31 CET
Keywords:
(none) =>
USABILITY |
Description of problem: When invoking Firefox from within KDE 4 on x86-64, it functions beautifully, until one exits Firefox again - whether via the window titlebar's "close" button, or whether from the Firefox menu. From that moment on, the firefox process consumes 100% CPU time on one of the two cores in my machine and must be explicitly killed via SIGKILL - SIGTERM has no effect. An strace shows that Firefox gets stuck in an infinite loop after it is shut down in the normal way. <snippet> poll([{fd=4, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=4, revents=POLLNVAL}]) </snippet> The curious thing is that Firefox does not show this behavior when run from LXDE. Version-Release number of selected component (if applicable): The problem occurred in the initial Mageia 1 install with KDE 4.6.3 and Firefox 3.x, and still persists in KDE 4.6.5 and with Firefox 7.x.