qdiff makes Xorg eats up all RAM on Oneiric

Bug #851379 reported by Francis J. Lacoste
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
qbzr (Ubuntu)
New
Undecided
Unassigned

Bug Description

I'm unable to vizualise diff using qdiff since I've upgraded to Oneiric.

Doing a bzr qdiff on any tree of any size with or without actual difference will make Xorg take 2G of RSS and make my workstation unusable. Killing the bzr process frees the X server memory.

I have the following appearing on the terminal when the window is about to come up:
(python:13375): Gtk-CRITICAL **: IA__gtk_widget_style_get: assertion `GTK_IS_WIDGET (widget)' failed
QWidget::setMinimumSize: (/DiffWindow) The largest allowed size is (16777215,16777215)

I suspect the window is created too big :-)

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: qbzr 0.21.1-1
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
Date: Thu Sep 15 17:45:56 2011
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
SourcePackage: qbzr
UpgradeStatus: Upgraded to oneiric on 2011-09-08 (7 days ago)

Revision history for this message
Francis J. Lacoste (flacoste) wrote :
Revision history for this message
Jonathan Riddell (jr) wrote :

Thanks for the report, I'm afraid I can't recreate it. What video card and driver are you using?

Do other PyQt applications have the same problem? (e.g. language-selector-kde)

Revision history for this message
Francis J. Lacoste (flacoste) wrote :

My video card is a "Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) (rev 0c)", I'm using the i915 kernel module. I'm attaching my Xorg log file.

Revision history for this message
Francis J. Lacoste (flacoste) wrote :
Revision history for this message
Francis J. Lacoste (flacoste) wrote :

Might this be a duplicate of bug 805303?

Revision history for this message
Francis J. Lacoste (flacoste) wrote :

Looks like it, the same work-around (running qtconfig and selecting something else than GTK+ / default) works.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.