Re: [Gimp-user] large tile sizes and large images on Freebsd [solved]
Bram Van Steenlandt wrote: Hi list, I run FreeBSD 6.2 (2 gig ram) and use gimp-2.2.17 for editing my large (1x1pixels) photos. This works when the tile cache is set to 256MB but this is not enough for fast editing. When I set the tile cache to 512MB or more it stops with error: GLib-ERROR **: gmem.c:135: failed to allocate 16384 bytes I checked in top while the gimp was opening the image and I still had 400MB free before it stopped (not counting my 4000MB free swap). After asking the gnome/freebsd guys some nice person said I should try adding kern.maxdsiz=1073741824 to /boot/loader.conf and reboot. This worked, the gimp now opens the large files when the tile cache is set to 512MB, editing is the same speed as fedora. turning off the layer preview things also helped a lot. I tried krita but it crashed when I asked to do a 90 degree turn. nip2 opened the files ok but it's kind of a strange program to work with. thanks all for the answers ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
[Gimp-user] large tile sizes and large images on Freebsd
Hi list, I run FreeBSD 6.2 (2 gig ram) and use gimp-2.2.17 for editing my large (1x1pixels) photos. This works when the tile cache is set to 256MB but this is not enough for fast editing. When I set the tile cache to 512MB or more it stops with error: GLib-ERROR **: gmem.c:135: failed to allocate 16384 bytes I checked in top while the gimp was opening the image and I still had 400MB free before it stopped (not counting my 4000MB free swap). I have another computer with Fedora 7 and less RAM (1 gig) and here this does work, tile size is set to 512MB and editing is rather fast. I found this old thread: http://www.mail-archive.com/gimp-user@lists.xcf.berkeley.edu/msg07633.html wich a bit the same. So my questions are: -Is there some magic setting wich allows the tile size to be bigger ? -Can't the gimp be configured to not save to disk after every edited pixel ? If you put one pencil dot on an image it takes 4 seconds before you can do the next. -Is there a way to work in ram only ? Can I for example buy 2 additional gig and then force the gimp to use only this memory and give me a messages out of memory when this does not work ideas ? kind regards below is the full output: $ gimp --debug-handlers --stack-trace-mode always scan13.tif GLib-ERROR **: gmem.c:135: failed to allocate 16384 bytes aborting... gimp: terminated: Abort trap: 6 #0 0x28cea6cd in wait4 () from /lib/libc.so.6 #1 0x28cc96ad in waitpid () from /lib/libc.so.6 #2 0x28c75242 in waitpid () from /lib/libpthread.so.2 #3 0x28a3ad79 in g_on_error_stack_trace () #4 0x080646b4 in ?? () #5 0x083ace00 in ?? () #6 0xbfbfd560 in ?? () #7 0x in ?? () #8 0x24075e00 in ?? () #9 0x in ?? () #10 0x in ?? () #11 0x in ?? () #12 0x in ?? () #13 0xbfbfd584 in ?? () #14 0x28d631a0 in ?? () from /lib/libc.so.6 #15 0xbfbfd5b4 in ?? () #16 0xbfbfd5b4 in ?? () #17 0x0282 in ?? () #18 0x28c904b4 in ?? () from /lib/libpthread.so.2 #19 0xbfbfd5a8 in ?? () #20 0x080646e1 in ?? () #21 0x0001 in ?? () #22 0xbfbfd5b4 in ?? () #23 0x0006 in ?? () #24 0x28c904b4 in ?? () from /lib/libpthread.so.2 #25 0xbfbfd980 in ?? () #26 0xbfbfd6c0 in ?? () #27 0xbfbfd5c8 in ?? () #28 0x0806421d in ?? () #29 0x28d631a0 in ?? () from /lib/libc.so.6 #30 0x09042d00 in ?? () #31 0xbfbfd5d8 in ?? () #32 0x28c8e3d1 in __error () from /lib/libpthread.so.2 (script-fu:13073): LibGimpBase-WARNING **: script-fu: wire_read(): error ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
