On Tuesday, May 21, 2013 23:26:03 Dominik George wrote:
> Hi,
> 
> > On Sunday, May 12, 2013 20:07:52 Dominik George wrote:
> > > We already limited the botification number to one event per minute,
> > > however, the code still freezes KDE.
> > 
> > by "KDE" i assume you mean the plasma-desktop process (and that other
> > application windows remain responsive; alt-tab'ing still works, etc)
> 
> actually not - the whole desktop freezes, including any running
> applications.

Huh .. that implies one of a limited number of possibilities:

* x itself is dieing (in which case there is little we can do about it); this 
is unlikely, particularly if notifications from other applications work.

* the call is causing something on the system to consume large amounts of 
memory, and the machine has gone into a swap storm. you said that it sometimes 
makes the dbus call more than once .. could it be that it is calling it a 
large number of times?

... i can't think of another realistically possible explanation for all 
applications freezing as well. (excessive CPU usage should still offer some 
interactivity rather than a complete freeze ...)

one really out there possibility is if you are using desktop effects (the 
default) that kwin is freezing which would give a similar appearance even 
though the system would still actually be up. that's a very remote possibility 
in this case, though.

might be useful to ssh into the machine from a second system and see what is 
happening on the affected system when it freezes.

> > > Attached is the plasmoid code that crashes, removing the comment sign at
> > > the beginning of line 317 introduces notifications and the freeze.
> > 
> > i'm not sure why, but you are using the org.kde.KNotify dbus interface
> > directly via QtDBus .. and doing so with a blocking call.
> 
> Because this way was the only one I found. It is documented in a ton of
> places.

Ugh. :/ Copy and paste gone wild :) It happens ...

-- 
Aaron J. Seigo

Attachment: signature.asc
Description: This is a digitally signed message part.

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Reply via email to