Mail applet messes with other threads (like Weather)

Bug #657803 reported by Tsu Jan
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cairo-Dock Plug-ins
Expired
Undecided
Unassigned

Bug Description

This bug is somehow odd but I try to explain it as clearly as possible. I use my whole band-width for some download, for example, when downloading heavy files with Synaptic. Then I intentionally middle click on the weather applet to see what happens. Of course, it can't get any information and its icon changes because my whole band-width is used by Synaptic or another heavy download process. But, after a few seconds, something bad happens: one of my CPU cores goes to 100%. I can't quit Cairo-Dock normally but can kill its process and then, CPU usage gets normal again.

When I don't middle click on the weather applet, sometimes the same thing happens and sometimes Cairo-Dock crashes and automatically restarts.

In the case of 100% CPU usage, I see no message in xsession-errors except normal messages related to the weather and mail applets, which say that they cannot retrieve information. In the case of crash and restart, I don't clearly remember the messages but I think they said that the culprit might be the weather applet.

I see this problem only after the recent changes in the weather applet of the bazaar releases (5th Oct). However, I'm not sure that it's the main cause.

Revision history for this message
Tsu Jan (tsujan2000) wrote :

The crash report doesn't seem useful:

Cairo-Dock has crashed (sig 6).
It will be restarted now (cairo-dock -o).
Feel free to report this bug on glx-dock.org to help improving the dock !
info on the system :
Linux debian 2.6.32-5-686-bigmem #1 SMP Sat Sep 18 02:52:26 UTC 2010 i686 GNU/Linux
Couldn't guess if it was an applet's fault or not. It may have crashed inside the core or inside a thread

Revision history for this message
Fabounet (fabounet03) wrote : Re: [Cairo-dock-team] [Bug 657803] Re: Weather Applet and High CPU Usage

Hi,
what would be very helpful is to launch the dock with ddd and reproduce the
bug, ddd will then stop the program where it crashed and hopefully gives an
useful backtrace.
I don't think the recent changes in the applet are involved here (it was
about double-click on the icons)
it may be a problem in libcurl or in libxml, failing to get data or getting
wrong xml data, hard to say (and hard to reproduce).
Thanks in advance !

2010/10/11 Tsu Jan <email address hidden>

> The crash report doesn't seem useful:
>
> Cairo-Dock has crashed (sig 6).
> It will be restarted now (cairo-dock -o).
> Feel free to report this bug on glx-dock.org to help improving the dock !
> info on the system :
> Linux debian 2.6.32-5-686-bigmem #1 SMP Sat Sep 18 02:52:26 UTC 2010 i686
> GNU/Linux
> Couldn't guess if it was an applet's fault or not. It may have crashed
> inside the core or inside a thread
>
> --
> Weather Applet and High CPU Usage
> https://bugs.launchpad.net/bugs/657803
> You received this bug notification because you are a member of Cairo-
> Dock Team, which is subscribed to Cairo-Dock Plug-ins.
>
> Status in Cairo-Dock : Plug-ins: New
>
> Bug description:
> This bug is somehow odd but I try to explain it as clearly as possible. I
> use my whole band-width for some download, for example, when downloading
> heavy files with Synaptic. Then I intentionally middle click on the weather
> applet to see what happens. Of course, it can't get any information and its
> icon changes because my whole band-width is used by Synaptic or another
> heavy download process. But, after a few seconds, something bad happens: one
> of my CPU cores goes to 100%. I can't quit Cairo-Dock normally but can kill
> its process and then, CPU usage gets normal again.
>
> When I don't middle click on the weather applet, sometimes the same thing
> happens and sometimes Cairo-Dock crashes and automatically restarts.
>
> In the case of 100% CPU usage, I see no message in xsession-errors except
> normal messages related to the weather and mail applets, which say that they
> cannot retrieve information. In the case of crash and restart, I don't
> clearly remember the messages but I think they said that the culprit might
> be the weather applet.
>
> I see this problem only after the recent changes in the weather applet of
> the bazaar releases (5th Oct). However, I'm not sure that it's the main
> cause.
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~cairo-dock-team<https://launchpad.net/%7Ecairo-dock-team>
> Post to : <email address hidden>
> Unsubscribe : https://launchpad.net/~cairo-dock-team<https://launchpad.net/%7Ecairo-dock-team>
> More help : https://help.launchpad.net/ListHelp
>

Revision history for this message
Tsu Jan (tsujan2000) wrote : Re: Weather Applet and High CPU Usage

Hi,

First, thanks for introducing me to ddd. Its so useful.

I couldn't reproduce the crash with ddd but, at some point, Cairo-Dock froze (without 100% CPU usage) and I got these messages on the bottom pane of ddd:

---------------------
cairo-dock: ath.c:193: _gcry_ath_mutex_lock: Assertion `*lock == ((ath_mutex_t) 0)' failed.

Program received signal SIGABRT, Aborted.
[Switching to Thread 0xae325b70 (LWP 8494)]
0xb7fe2424 in __kernel_vsyscall ()
(gdb)
---------------------

I attached the screenshot of the Backtrace window.

Revision history for this message
Fabounet (fabounet03) wrote : Re: [Cairo-dock-team] [Bug 657803] Re: Weather Applet and High CPU Usage

oh, it looks like a bug listed on Launchpad recently, about the use of
GnuTLS in libetpan (which is used in the mail applet)
I remember of a bug that you opened and closed on the mail applet, not sure
if both are linked.
anyway, it may be useful to do the tests without the mail applet first, to
test the weather applet only
maybe we will find that the mail applet is the only culprit (since it is
threaded, it runs in parallel of the other applets, that's why the dock says
it's weather's fault).

2010/10/11 Tsu Jan <email address hidden>

> Hi,
>
> First, thanks for introducing me to ddd. Its so useful.
>
> I couldn't reproduce the crash with ddd but, at some point, Cairo-Dock
> froze (without 100% CPU usage) and I got these messages on the bottom
> pane of ddd:
>
> ---------------------
> cairo-dock: ath.c:193: _gcry_ath_mutex_lock: Assertion `*lock ==
> ((ath_mutex_t) 0)' failed.
>
> Program received signal SIGABRT, Aborted.
> [Switching to Thread 0xae325b70 (LWP 8494)]
> 0xb7fe2424 in __kernel_vsyscall ()
> (gdb)
> ---------------------
>
> I attached the screenshot of the Backtrace window.
>
>
> ** Attachment added: "ddd screenshot"
>
> https://bugs.launchpad.net/cairo-dock-plug-ins/+bug/657803/+attachment/1684629/+files/Screenshot.png
>
> --
> Weather Applet and High CPU Usage
> https://bugs.launchpad.net/bugs/657803
> You received this bug notification because you are a member of Cairo-
> Dock Team, which is subscribed to Cairo-Dock Plug-ins.
>
> Status in Cairo-Dock : Plug-ins: New
>
> Bug description:
> This bug is somehow odd but I try to explain it as clearly as possible. I
> use my whole band-width for some download, for example, when downloading
> heavy files with Synaptic. Then I intentionally middle click on the weather
> applet to see what happens. Of course, it can't get any information and its
> icon changes because my whole band-width is used by Synaptic or another
> heavy download process. But, after a few seconds, something bad happens: one
> of my CPU cores goes to 100%. I can't quit Cairo-Dock normally but can kill
> its process and then, CPU usage gets normal again.
>
> When I don't middle click on the weather applet, sometimes the same thing
> happens and sometimes Cairo-Dock crashes and automatically restarts.
>
> In the case of 100% CPU usage, I see no message in xsession-errors except
> normal messages related to the weather and mail applets, which say that they
> cannot retrieve information. In the case of crash and restart, I don't
> clearly remember the messages but I think they said that the culprit might
> be the weather applet.
>
> I see this problem only after the recent changes in the weather applet of
> the bazaar releases (5th Oct). However, I'm not sure that it's the main
> cause.
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~cairo-dock-team<https://launchpad.net/%7Ecairo-dock-team>
> Post to : <email address hidden>
> Unsubscribe : https://launchpad.net/~cairo-dock-team<https://launchpad.net/%7Ecairo-dock-team>
> More help : https://help.launchpad.net/ListHelp
>

Revision history for this message
Tsu Jan (tsujan2000) wrote : Re: Weather Applet and High CPU Usage

> oh, it looks like a bug listed on Launchpad...

This could be true bcause I started to use the mail applet again only recently.

> ... test the weather applet only...

I'll do so but it may take some time since the bug happens randomly.

Revision history for this message
Tsu Jan (tsujan2000) wrote :

After I removed the mail applet, I couldn't reproduce the bug anymore. I reloaded the weather applet again and again while my band-width was exhausted by another process but the dock was stable.

So, this bug is related to the mail applet and, perhaps, its source is libetpan, as you mentioned above.

Fabounet (fabounet03)
summary: - Weather Applet and High CPU Usage
+ Mail applet messes with other threads (like Weather)
Changed in cairo-dock-plug-ins:
status: New → Triaged
Revision history for this message
Matthieu Baerts (matttbe) wrote :

Hello! (and sorry for this very long delay!)

Do you still have this bug with the latest stable version? (3.3.0)

Changed in cairo-dock-plug-ins:
status: Triaged → Incomplete
Revision history for this message
Tsu Jan (tsujan2000) wrote :

Please read my reply at bug #654952.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Cairo-Dock Plug-ins because there has been no activity for 60 days.]

Changed in cairo-dock-plug-ins:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.