← Back to team overview

registry team mailing list archive

[Bug 593290] Re: Terminator locks up with 100% CPU, when trying to split panes too many times

 

I've been idly wondering if some locking would help. It seems like a key
factor here is the speed at which splitting is happening - perhaps we
need to wait until a terminal has been fully rendered before we accept a
split request. I'm not 100% sure off the top of my head which gtk signal
can be used for "I have finished setting up", but I wondered if it could
be tied into our spawn_child(). That would depend on some guarantee from
vte that fork_command() returns at a point where the terminal definitely
exists and has been laid out.

** Bug watch added: Debian Bug tracker #596923
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=596923

** Also affects: terminator (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=596923
   Importance: Unknown
       Status: Unknown

-- 
Terminator locks up with 100% CPU, when trying to split panes too many times
https://bugs.launchpad.net/bugs/593290
You received this bug notification because you are a member of Registry
Administrators, which is the registrant for Debian.



References