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 124167 - GIMP crashes at start-up looking for fonts
GIMP crashes at start-up looking for fonts
Status: RESOLVED DUPLICATE of bug 121752
Product: GIMP
Classification: Other
Component: General
1.x
Other Windows
: Normal critical
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2003-10-09 00:29 UTC by Phil Harper
Modified: 2003-10-11 18:17 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Phil Harper 2003-10-09 00:29:54 UTC 
The GIMP 1.3.21(binary from TML) causes a GPF on
win98 after more than 5 minutes of searching(huge
amount of HDD activity during that time) for fonts
on start-up.

GIMP-1 caused an invalid page fault in
module MSVCRT.DLL at 0167:78002320.
Registers:
EAX=00000000 CS=0167 EIP=78002320 EFLGS=00010246
EBX=00000000 SS=016f ESP=0105fc0c EBP=0105fc28
ECX=00000000 DS=016f ESI=00000000 FS=7547
EDX=012a6990 ES=016f EDI=00000001 GS=0000
Bytes at CS:EIP:
8b 01 ba ff fe fe 7e 03 d0 83 f0 ff 33 c2 83 c1 
Stack dump:
00cfb434 00000000 0105fc58 7800d81b 00000000
00000000 00000001 0105fc58 00cfa8ac 00000000
012a907d 012a9000 00ce50ba 0000000e 00000008 0105ff68
Comment 1 Sven Neumann 2003-10-09 11:31:31 UTC 
What version of fontconfig are you using?
Comment 2 Phil Harper 2003-10-09 12:01:18 UTC 
it's fontconfig 2.2.1
Comment 3 Sven Neumann 2003-10-09 12:12:32 UTC 
That is bad since this problem only shows up on Windows then. Seems to
work well on Unix systems with that version of fontconfig. Someone
will have to look into this with a debugger on Windows.
Comment 4 Phil Harper 2003-10-09 16:04:44 UTC 
ok, version corrected, sorry, my brain seems to have wandered off again.
Comment 5 Dave Neary 2003-10-11 18:17:45 UTC 
Looks like a duplicate in that case. This is fixed in the latest
binaries released yesterday.

Cheers,
Dave.

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