After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 683373 - Performance of native 2.8.2 build on Mac OS is extremely poor
Performance of native 2.8.2 build on Mac OS is extremely poor
Status: RESOLVED DUPLICATE of bug 705645
Product: GIMP
Classification: Other
Component: General
2.8.2
Other Mac OS
: Normal major
: 2.8
Assigned To: GIMP Bugs
GIMP Bugs
: 687033 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2012-09-04 22:45 UTC by pkclsoft
Modified: 2013-10-11 19:35 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
GIMP 2.8.0 non-native crash after enabling xquartz cursor (41.26 KB, application/octet-stream)
2012-09-04 22:45 UTC, pkclsoft
Details
Second crash report (41.26 KB, application/octet-stream)
2012-09-04 22:46 UTC, pkclsoft
Details

Description pkclsoft 2012-09-04 22:45:14 UTC
Created attachment 223478 [details]
GIMP 2.8.0 non-native crash after enabling xquartz cursor

With the update to Mountain Lion, I've been forced to use the new native build of GIMP.  At first I installed xquartz and tried using the v2.8.0 Lion build of GIMP but that refuses to use the mouse for anything within the canvas because the xquartz input device is disabled.  Enabling the xquartz cursor as an input device causes GIMP to crash (crash logs attached) as soon as the mouse enters the canvas.

So, failing this, I've installed the native version of GIMP, v2.8.2 which sounds like a great idea.  It works, but it's performance is probably 10x slower than the non-native GIMP.

In an image about 2500x2500, with 4 layers, hiding a middle layer takes about 10 seconds whereas with the old non-native GIMP it might have taken 1.

This is going to make the app unusable in the long term which is really unfortunate.
Comment 1 pkclsoft 2012-09-04 22:46:42 UTC
Created attachment 223479 [details]
Second crash report

This is a second crash report from v2.8.0 (non-native, Lion)
Comment 2 Michael Natterer 2012-09-05 07:30:38 UTC
About the crashes, they probably come from bogus event coordinates delivered
by the X sever, I'm about to add a workaround for that.

The slowness is unclear, but I would guess it's due to atomic operations
being poorly implemented in GLib. We'll make sure to include the right
GLib patch in the next release.
Comment 3 Michael Natterer 2012-09-05 09:40:28 UTC
This should fix the crash, pushed to master and gimp-2-8. Doesn't
deal with the slowness.

commit 0e2bce2b82eec153244aa874a1648f73be11798e
Author: Michael Natterer <mitch@gimp.org>
Date:   Wed Sep 5 11:29:45 2012 +0200

    app: make handling of coordinates more robust against broken input drivers
    
    Initialize the axes[] array with zeros and change pressure curve
    mapping to not try to "interpolate" shit like NaN and crash.
    (cherry picked from commit c7b9728cc8b9c5af28ac04e021246ab23d8f1eba)

 app/core/gimpcurve-map.c            |   38 ++++++++++++++++++++++++++---------
 app/widgets/gimpdeviceinfo-coords.c |    2 +-
 2 files changed, 29 insertions(+), 11 deletions(-)
Comment 4 Michael Natterer 2012-11-03 11:18:20 UTC
*** Bug 687033 has been marked as a duplicate of this bug. ***
Comment 5 Christopher Martin 2012-11-03 11:35:59 UTC
Instruments sample it is.

For this, I Isolated the GIMP-bin process with an event handler sampler. Started with a blank A4 template, started record, and attempted to change "Background" layer to "what is this" layer.

Can't attach .trace files, here's a link: http://www.christophermartin.name/developer/GIMP/2.8.2/index.html

Excuse the poor look of the page; quick job.
Comment 6 Christopher Martin 2012-11-03 11:45:45 UTC
(In reply to comment #5)
> Instruments sample it is.
> 
> For this, I Isolated the GIMP-bin process with an event handler sampler.
> Started with a blank A4 template, started record, and attempted to change
> "Background" layer to "what is this" layer.
> 
> Can't attach .trace files, here's a link:
> http://www.christophermartin.name/developer/GIMP/2.8.2/index.html
> 
> Excuse the poor look of the page; quick job.

Sorry, file access problems. Mirror! http://bayfiles.com/file/q7G1/aV9IoS/GIMP-layer-rename.trace.zip
Comment 7 Clayton Walker 2013-10-11 19:35:15 UTC

*** This bug has been marked as a duplicate of bug 705645 ***