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 51780 - Memory allocation problems on Tru64 4.0.
Memory allocation problems on Tru64 4.0.
Status: VERIFIED FIXED
Product: GIMP
Classification: Other
Component: General
1.x
Other OSF/1
: Normal critical
: 1.2
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2001-03-06 18:19 UTC by jnielsen
Modified: 2015-12-21 09:41 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description jnielsen 2001-03-06 18:19:27 UTC 
Attempting to set the memory cache to greater than 100 MB and open any
image causes upon redraw of the image window.

Setting below 100 MB any image can be opened within the limitation of
system processing due to memory usage. ie: Opening a 200 MB image with a 99
MB cache makes the system/software unuseable.

Consistent across 4 machines, 4.0e and 4.0f as well as not only compiled on
those machines but installation of Tru64 setld package created by other
True64 users.

GLib-ERROR **: could not allocate 4096 bytes
aborting...
/usr/local/bin/gimp terminated: IOT/Abort trap

LibGimp-WARNING **: tiff: wire_read: unexpected EOF

LibGimp-WARNING **: script-fu: wire_read: unexpected EOF
Comment 1 Raphaël Quinet 2001-04-26 18:10:34 UTC 
Re-assigning all Gimp bugs to default component owner (Gimp bugs list)
Comment 2 Sven Neumann 2001-06-18 20:13:14 UTC 
How much memory had the machines you tested this on?
Comment 3 Sven Neumann 2001-06-19 00:15:40 UTC 
Softplotter User <jnielsen@aero-graphics.com> writes:

> Several machines were tested containing the following:
> 
> 128MB
> 256MB
> 2GB
> 4GB
> 
> The 2 and 4 GB machines seem to work ok.

well, opening a 90MB image file needs quite a lot of memory
resources. If this memory exceeds the tile_cache_size as set
in the Preferences dialog, GIMP starts to swap to disk (what
else can it do?). Make sure your swap file (also set in the 
Preferences) is on a fast (local!) disc with enough space.

Please report back if this solves your problem.
Comment 4 Raphaël Quinet 2002-04-11 11:30:55 UTC 
I suppose that the problem was solved, since no further information
was received from the original reporter.