[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-panel-devel
Subject:    Re: Re: Thoughts about a better Quality Management process for Plasma
From:       Martin =?ISO-8859-1?Q?Gr=E4=DFlin?= <mgraesslin () kde ! org>
Date:       2013-01-17 11:54:27
Message-ID: 3596302.R8UjJbHR60 () martin-desktop
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Thursday 17 January 2013 12:30:03 Luca Beltrame wrote:
> In data giovedì 17 gennaio 2013 11:22:04, David Edmundson ha scritto:
> > backtrace it's impossible to see who's at fault. The backtrace only
> > shows some timer firing, or a python binding call or something generic
> > - it's impossible to tell what's at fault. I have no idea how we can
> > fix this.
> 
> Chiming in for the Python parts: at least part of the crashes are due to
> errors in the Python applets themselves. To be more precise, Python uses a
> garbage-collection method based on references, which includes the bindings
> to C++ objects. In such cases I've noticed that the exception makes the
> object marked for garbage collection → deleted at the C++ level as well,
> and if you try accessing it again → crash.
uh that sounds bad. I thought we do these script stuff to get the applet into 
a sandbox so that it cannot crash. Pity :-(
> 
> By errors I mean Python exceptions (IOW, errors in the Python code itself).
> 
> --
> Luca Beltrame - KDE Forums team
> KDE Science supporter
> GPG key ID: 6E1A4E79

["signature.asc" (application/pgp-signature)]

_______________________________________________
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel


[prev in list] [next in list] [prev in thread] [next in thread]