Re: Gnome 2.14 Module Proposal: Deskbar Applet

Le jeudi 27 octobre 2005 à 13:32 +0100, Gustavo J. A. M. Carneiro a
écrit :
> Qui, 2005-10-27 às 11:05 +0200, Benoît Dejean escreveu:
>   The result: a single process (per user, per display), and a single
> main loop, for all applets.  Of course this means if one applet
> deadlocks or dies, they all die.  But at least dying in python is not so
> easy.  You usually get only an exception that is ignored.  Deadlock is
> easier if they use threads.

We don't do it for C applets because if "one applet deadlocks or dies,
they all die". But thanks for raising the problem of many VM-based
applets : currently, 3 applets would take ~ 50MB of RES memory.

But before trying to run each applet on a common interpreter, you need
to get sure that the current situation:

	12MB readonly/shared + (<N applets> * 10MB private)

would turn into :

	12MB readonly/shared + 10MB shared + (<N applets> * 3MB private)

Which would eventually make python applets lighter than C applets (and
maybe leakproof).

But again, "one applet deadlocks or dies, they all die". Here again, i
have some bad memories about nasty desklets / 3rd party desklets in
gdesklets that screwed the whole program.

Je cherche un emploi de développeur / admin sys&réseau sous GNU/Linux
JID: TazForEver jabber org

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

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]