Mail Notification, A mail notification for freedesktop.org-compliant system trays - Bugs: bug #18367, No network connection causes...
You are not allowed to post comments on this tracker with your current authentication level.
bug #18367: No network connection causes 75-100% CPU usage
Submitter: | None | ||
Submitted: | Fri 24 Nov 2006 07:49:12 PM UTC | ||
Severity: | 3 - Normal | Status: | Need Info |
Privacy: | Public | Assigned to: | None |
Originator Name: | Originator Email: | -email is unavailable- | |
Open/Closed: | Closed |
Jump to the original submission
Mon 28 Jan 2008 06:03:13 PM UTC, comment #23: |
Jean-Yves Lefort <jylefort> |
Mon 05 Nov 2007 02:00:48 AM UTC, comment #22: I forgot to mention that the output will be much more useful if you use packages with debug symbols compiled-in. See https://wiki.ubuntu.com/DebuggingProgramCrash for more information. |
Jean-Yves Lefort <jylefort> |
Mon 05 Nov 2007 01:48:31 AM UTC, comment #21: I have never been able to reproduce this problem, but I could make good use of profiling information. For anyone interested, here is a simple way to generate it (applies to Ubuntu):
|
Jean-Yves Lefort <jylefort> |
Mon 05 Nov 2007 12:55:35 AM UTC, comment #20: Hello,
|
Anonymous |
Mon 16 Jul 2007 10:49:41 PM UTC, comment #19: Hi,
|
Anonymous |
Mon 16 Jul 2007 04:45:59 AM UTC, comment #18: Another one that sees the problem in Fedora (mn 4.0);
|
Anonymous |
Fri 27 Apr 2007 04:24:49 PM UTC, comment #17: Fedora Bug entry:
|
Russell Harrison <rtlm> |
Wed 29 Nov 2006 05:09:50 AM UTC, comment #16: FYI.
|
Pascal Giard <evilynux> |
Sat 25 Nov 2006 07:26:34 PM UTC, comment #15: Fair enough. It is very strange, as I can't seem to find any particular set of circumstances that will cause MN to do it either. Seems to be at random, unfortunately. |
Kyle Vanditmars <kylevan> |
Sat 25 Nov 2006 04:33:27 PM UTC, comment #14: That backtrace looks perfectly normal. At this point I'm afraid there's nothing I can do, since I cannot reproduce the high CPU usage myself. |
Jean-Yves Lefort <jylefort> |
Sat 25 Nov 2006 07:10:57 AM UTC, comment #13: alright, I followed your directions, I attached the file, gdb-mn5.txt |
Kyle Vanditmars <kylevan> |
Sat 25 Nov 2006 05:18:30 AM UTC, comment #12: Don't type continue. After attach, type:
|
Jean-Yves Lefort <jylefort> |
Sat 25 Nov 2006 02:55:02 AM UTC, comment #11: I've performed another backtrace, using the attach while running method. the file is gdb-mn2.txt |
Kyle Vanditmars <kylevan> |
Sat 25 Nov 2006 02:45:44 AM UTC, comment #10: I need a backtrace showing what the program is doing when it uses the CPU. Either run MN from gdb and then hit ^C, or attach to an already running MN process with gdb. |
Jean-Yves Lefort <jylefort> |
Sat 25 Nov 2006 02:42:50 AM UTC, comment #9: Well this is frustrating... Now the behaviour has cropped up even after accessing my wireless network. I tried doing another backtrace, but nothing caused the program to actually crash, I just had to exit it. |
Kyle Vanditmars <kylevan> |
Sat 25 Nov 2006 02:32:38 AM UTC, comment #8: Well, the problem behaviour has gone away. I installed the mail-notification-dbgsym package from the repository listed on http://live.gnome.org/GettingTraces/DistroSpecificInstructions for Ubuntu Edgy. I was planning to run another debugging trace, however, after installing that package, I can no longer reproduce the behaviour. |
Kyle Vanditmars <kylevan> |
Sat 25 Nov 2006 01:22:48 AM UTC, comment #7: Alright, I preformed the backtrace as per the wiki, and when I right-clicked the MN icon on the taskbar to remove it, I got a segmentation fault. After closing GDB, the built-in bug reporting tool popped up and created its own bug report. I have included both in case more information is included in one of them. |
Kyle Vanditmars <kylevan> |
Fri 24 Nov 2006 10:28:56 PM UTC, comment #6: Then you don't even need to build yourself, see this:
|
Jean-Yves Lefort <jylefort> |
Fri 24 Nov 2006 10:21:51 PM UTC, comment #5: If it makes any difference, I am using the Ubuntu 6.10 package of MN.
|
Kyle Vanditmars <kylevan> |
Fri 24 Nov 2006 10:15:40 PM UTC, comment #4: I cannot reproduce this. Please provide a backtrace with debugging symbols:
|
Jean-Yves Lefort <jylefort> |
Fri 24 Nov 2006 09:42:09 PM UTC, comment #3: Ok, I have attached the pertinent file. |
Kyle Vanditmars <kylevan> |
Fri 24 Nov 2006 09:27:19 PM UTC, comment #2: Please attach your ~/.gnome2/mail-notification/mailboxes.xml file (scrubbing passwords if necessary). |
Jean-Yves Lefort <jylefort> |
Fri 24 Nov 2006 08:08:51 PM UTC, comment #1: I should add that I've only recently installed MN, and that each boot since this behaviour has occurred. |
Kyle Vanditmars <kylevan> |
Fri 24 Nov 2006 07:49:12 PM UTC, original submission:
I have "mail-notification --sm-disable" in my GNOME startup programs. The past two boots, if I do not enter my GNOME keyring password to allow NetworkManager to connect to the wireless network before mail notification loads, mail-notification and python processes will cause the CPU load to go to 100%, with the vast majority being used by mail-notification (75-80%). Manually activating the update function will cause the CPU load to decrease momentarily to 25-30%, and then usage spikes again.
|
Anonymous |
Depends on the following items: None found
Items that depend on this one: None found
Follow 9 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2008-01-28 | jylefort | Open/Closed | Open | Closed | |
2007-04-27 | rtlm | Carbon-Copy | - | Added -email is unavailable- | |
2006-11-25 | kylevan | Attached File | - | Added gdb-mn5.txt, #11353 | |
2006-11-25 | kylevan | Attached File | - | Added gdb-mn2.txt, #11352 | |
2006-11-25 | kylevan | Attached File | - | Added mail-notification-bugreport.txt, #11350 | |
2006-11-25 | kylevan | Attached File | - | Added gdb-mail-notification.txt, #11349 | |
2006-11-24 | kylevan | Attached File | - | Added bugreport-mailboxes.xml, #11347 | |
2006-11-24 | jylefort | Status | None | Need Info | |
Carbon-Copy | - | Added -email is unavailable- |
Powered by Savane 3.13-f8d8.
Corresponding source code
This issue is now tracked in the new bug tracker (https://bugs.launchpad.net/mail-notification/+bug/182923).