Bug 765890 - Probable EXA performance bug exposed by libreoffice
Summary: Probable EXA performance bug exposed by libreoffice
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-server
Version: 17
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: card_R300e/M
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-09 16:12 UTC by Thierry Vignaud
Modified: 2013-08-01 13:22 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 494699
Environment:
Last Closed: 2013-08-01 13:22:26 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Thierry Vignaud 2011-12-09 16:12:02 UTC
+++ This bug was initially created as a clone of Bug #494699 +++

Description of problem: 
I've the same problem as Bug #494699.
However I can precise what librenoffice usage is making the x11 server to eat all CPU.

The problem exists for many fedora releases up to fc16, with openoffice in prior releases and with libreoffice in new ones.

Once several cells are selected for pasting in oocalc, the x11 server eats all CPU until the copying is canceled through pressing the <escape> key.

Libreoffice and the system become unresponsive (somewhat less when having a multicore CPU).


Version-Release number of selected component (if applicable):
kernel-3.1.4-1.fc16.noarch
libreoffice-base-3.4.4.2-3.fc16.x86_64
xorg-x11-server-Xorg-1.11.2-3.fc16.x86_64
xorg-x11-drv-nouveau-0.0.16-27.20110720gitb806e3f.fc16.x86_64


How reproducible:
every time


Steps to Reproduce:
1. start oocalc
2. open any document
3. select several cells with contents (eg: a 5x5 square)
   (do not select the whole sheet, the bug won't happen)
4. press <Ctrl>+C
   (in order to copy; but do not actually paste)
  

Actual results:
Oocalc animates dashes around the selected cells.
x11 instantatly eat nearly all CPU, whether oocalc is minimized or not.
Indefintely.
Oocalc CPU usage remains low but oocal is nearly unusable, irresponsible even on a dual core machine, despite having one CPU free, implying it's serializing on the X11 server.
This will only stop once pressing <escape> in oocalc in order to cancel pasting.


Expected results:
CPU usage should remain minimal for both oocalc & xorg


Additional info:
Video chipset: nVidia G98 [GeForce G100] (PCIe card, not IGP)
Video driver: nouveau
Desktop: XFCE (no compiz)
CPU: Intel(R) Core(TM)2 Duo CPU     E7500  @ 2.93GHz
RAM: 4Gb DDR2@800MHz

A powerful machine yet oocalc is making the Xorg server punch the CPU.
Happens with other video cards...

Comment 1 Adam Jackson 2012-04-09 22:25:55 UTC
I can't reproduce this with the i915 driver, so I suspect this is a deficiency in EXA.  My first guess was the classic mistake of using 1-wide lines instead of 0-wide, but the code to draw the marching ants there doesn't look like it's core rendering (in that i can see the antialiasing).

Comment 2 Fedora End Of Life 2013-01-16 21:01:49 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Thierry Vignaud 2013-01-18 16:57:32 UTC
Still valid with FC17

Comment 4 Fedora End Of Life 2013-07-04 04:23:59 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 5 Fedora End Of Life 2013-08-01 13:22:30 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.