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 739456 - GIMP 2.8.14 Hangs on Loading Data on OSX 10.10
GIMP 2.8.14 Hangs on Loading Data on OSX 10.10
Status: RESOLVED DUPLICATE of bug 449848
Product: GIMP
Classification: Other
Component: General
2.8.14
Other Mac OS
: Normal normal
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2014-10-31 16:27 UTC by Benjamin Kerensa
Modified: 2015-02-06 15:01 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Benjamin Kerensa 2014-10-31 16:27:39 UTC
GIMP 2.8.4 Hangs on Loading Data on OSX 10.10 even under fresh install with all app data blasted away.
Comment 1 Benjamin Kerensa 2014-10-31 16:27:54 UTC
2.8.14 correction
Comment 2 Michael Schumacher 2014-11-03 20:48:50 UTC
It could be building the initial font cache.
Comment 3 Benjamin Kerensa 2014-11-03 23:49:24 UTC
(In reply to comment #2)
> It could be building the initial font cache.

That's actually exactly where it hangs. Worked fine on OSX 10.9
Comment 4 Michael Schumacher 2014-11-06 15:35:57 UTC
It could be that the font cache on OSX is actually built somewhere in the GIMP package for your platform, then this would happen once for each new version. Subsequent runs of GIMP won't have that then. 

If you can check what the GIMP process is doing during this phase, you will most likely find that many font files are parsed.
Comment 5 Daniel Macks 2014-11-10 15:44:49 UTC
Related to Bug #449848?
Comment 6 Michael Schumacher 2014-11-10 23:24:25 UTC
Maybe - if this is due to the font cache, but we won't know that without a reply from Benjamin.
Comment 7 Benjamin Kerensa 2014-11-11 07:15:50 UTC
(In reply to comment #4)
> It could be that the font cache on OSX is actually built somewhere in the GIMP
> package for your platform, then this would happen once for each new version.
> Subsequent runs of GIMP won't have that then. 
> 
> If you can check what the GIMP process is doing during this phase, you will
> most likely find that many font files are parsed.

How would I check what the GIMP process is doing when it hangs on OSX?
Comment 9 Benjamin Kerensa 2014-11-11 07:32:11 UTC
(In reply to comment #8)
> Have a look at
> http://apple.stackexchange.com/questions/14409/how-to-monitor-file-access-for-an-os-x-application

So in inspecting the process the last files open are the fonts thats where it also become unresponsive.
Comment 10 Michael Schumacher 2014-12-26 14:19:22 UTC
Then you will have to wait that out.
Comment 11 Michael Schumacher 2015-02-06 15:01:44 UTC
Let's assume this to be a duplicate.

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