Bug 12986 - VTE terminal resizing is REALLY slow with Xorg 1.4
Summary: VTE terminal resizing is REALLY slow with Xorg 1.4
Status: RESOLVED NOTOURBUG
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/General (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: medium major
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-10-28 17:46 UTC by Philip Langdale
Modified: 2008-09-26 09:46 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Philip Langdale 2007-10-28 17:46:23 UTC
Couldn't find a version entry for the 1.4 server. odd.

Anyway, with Xorg 1.4, any terminal emulator based on the VTE widget (eg: gnome-terminal or xfce Terminal) is very very very slow to resize. Over a second delay before the window resizes after the drag is made.

The same build of the terminal emulator and vte (0.16.9) with Xorg 1.3 is fast and responsive.
Comment 1 Michel Dänzer 2007-10-29 00:41:03 UTC
Please attach (as opposed to paste) the full xorg.conf and Xorg.0.log files. Also, what kind of window manager are you using, do you have any special terminal settings such as transparent background, ...
Comment 2 Philip Langdale 2007-12-27 02:25:23 UTC
Not sure why I left out so much relevant information...

This is with the nvidia binary driver and xfwm4 doing xrender accelerated compositing or compiz doing GL accelerated compositing. According to this thread:

http://www.nvnews.net/vbulletin/showthread.php?t=98277

it's because of the switch from XCopyArea to a Composite call in Xorg 1.4.

The suggestion to change the pixmap allocation policy of the driver does help but it's not perfect. So it seems this bug just reduces to the general one of how to do resizing efficiently under compositing.
Comment 3 Philip Langdale 2008-09-26 09:46:16 UTC
nvidia have introduced multiple optimizations into their latest drivers to make this fast.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.