RSS/Atom feed Twitter
Site is read-only, email is disabled
  1. Chat
  2. Useful links
  3. Polls

Featured content

crash after saving tif

This discussion is connected to the gimp-developer-list.gnome.org mailing list which is provided by the GIMP developers and not related to gimpusers.com.

This is a read-only list on gimpusers.com so this discussion thread is read-only, too.

6 of 6 messages available
Toggle history

Please log in to manage your subscriptions.
crash after saving tif Roberto Winter 25 Mar 05:19
  crash after saving tif Tim Jedlicka 25 Mar 05:49
  crash after saving tif Michael Natterer 25 Mar 13:32
   crash after saving tif Roberto Winter 26 Mar 03:51
  crash after saving tif Kai-Uwe Behrmann 26 Mar 13:03
   crash after saving tif Roberto Winter 27 Mar 06:38
Roberto Winter
2006-03-25 05:19:58 UTC (over 18 years ago)

crash after saving tif

hi.

as i saved a file just now gimp crashed. i had it built from cvs some 10 days ago (gcc 3.3.5).
i'm using debian unstable, e16 window manager, nvidia drivers 8178 on xorg and kernel 2.6.13.1 .

on the terminal i got:

file_save_dialog_check_uri: URI = file:///home/media/fotos_tangara/xcf/tif/IMG_6384.TIF

file_save_dialog_check_uri: basename = IMG_6384.TIF file_save_dialog_check_uri: selected save_proc: NULL file_save_dialog_check_uri: URI save_proc: TIFF image file_save_dialog_check_uri: basename save_proc: TIFF image

file_save_dialog_check_uri: no save_proc was selected from the list file_save_dialog_check_uri: use URI's proc 'TIFF image' so indirect saving works
*** glibc detected *** corrupted double-linked list: 0x0a86a390 *** /opt/gimp/bin/gimp-2.3: terminated: Aborted

(script-fu:4033): LibGimpBase-WARNING **: script-fu: wire_read(): error

the image is a 8Mp photograph. it was a single layer file.

is this known? should i report a bug (i suspect it might be something with my environment, not gimp)? has it been noticed? fixed? the thing is it had been running absolutely stable the last days. and the weirder is that it crashed while doing something that i do often (saving as tif).
another thing that might matter is that the file was written fine and is not corrupted (~10Mb in size).

thanks for any help, roberto

Tim Jedlicka
2006-03-25 05:49:26 UTC (over 18 years ago)

crash after saving tif

On 3/24/06, Roberto Winter wrote:

as i saved a file just now gimp crashed. i had it built from cvs some 10 days ago (gcc 3.3.5).
i'm using debian unstable, e16 window manager, nvidia drivers 8178 on xorg and kernel 2.6.13.1 .
...
*** glibc detected *** corrupted double-linked list: 0x0a86a390 *** /opt/gimp/bin/gimp-2.3: terminated: Aborted

(script-fu:4033): LibGimpBase-WARNING **: script-fu: wire_read(): error

Don't know if this is your problem but I saw something similiar a long while back. Turned out I ran out of swap space. Confirm that your swap is functioning (via "top" or various other methods).

Michael Natterer
2006-03-25 13:32:41 UTC (over 18 years ago)

crash after saving tif

On Sat, 2006-03-25 at 01:19 -0300, Roberto Winter wrote:

hi.

as i saved a file just now gimp crashed. i had it built from cvs some 10 days ago (gcc 3.3.5).
i'm using debian unstable, e16 window manager, nvidia drivers 8178 on xorg and kernel 2.6.13.1.

on the terminal i got:

file_save_dialog_check_uri: URI = file:///home/media/fotos_tangara/xcf/tif/IMG_6384.TIF file_save_dialog_check_uri: basename = IMG_6384.TIF file_save_dialog_check_uri: selected save_proc: NULL file_save_dialog_check_uri: URI save_proc: TIFF image file_save_dialog_check_uri: basename save_proc: TIFF image

file_save_dialog_check_uri: no save_proc was selected from the list file_save_dialog_check_uri: use URI's proc 'TIFF image' so indirect saving works
*** glibc detected *** corrupted double-linked list: 0x0a86a390 *** /opt/gimp/bin/gimp-2.3: terminated: Aborted

I've seen crashes with exactly this glibc warning with a lot of different apps recently on sid, and after yesterday's update they didn't occur again.

IMHO this is not a gimp problem.

ciao, --mitch

Roberto Winter
2006-03-26 03:51:32 UTC (over 18 years ago)

crash after saving tif

On 3/25/06, Michael Natterer wrote:

On Sat, 2006-03-25 at 01:19 -0300, Roberto Winter wrote:

hi.

as i saved a file just now gimp crashed. i had it built from cvs some 10 days ago (gcc 3.3.5).
i'm using debian unstable, e16 window manager, nvidia drivers 8178 on xorg and kernel 2.6.13.1.

on the terminal i got:

file_save_dialog_check_uri: URI = file:///home/media/fotos_tangara/xcf/tif/IMG_6384.TIF file_save_dialog_check_uri: basename = IMG_6384.TIF file_save_dialog_check_uri: selected save_proc: NULL file_save_dialog_check_uri: URI save_proc: TIFF image file_save_dialog_check_uri: basename save_proc: TIFF image

file_save_dialog_check_uri: no save_proc was selected from the list file_save_dialog_check_uri: use URI's proc 'TIFF image' so indirect saving works
*** glibc detected *** corrupted double-linked list: 0x0a86a390 *** /opt/gimp/bin/gimp-2.3: terminated: Aborted

I've seen crashes with exactly this glibc warning with a lot of different apps recently on sid, and after yesterday's update they didn't occur again.

IMHO this is not a gimp problem.

I guess you are right.

ciao,

--mitch

Kai-Uwe Behrmann
2006-03-26 13:03:04 UTC (over 18 years ago)

crash after saving tif

Similiar problems where reported for CinePaint. Look at your libtiff version. If it has 3.8.0 update or downgrad. This libtiff version is buggy.

Hopd this helps.

kind regards Kai-Uwe Behrmann
+ development for color management + imaging / panoramas + email: ku.b@gmx.de + http://www.behrmann.name

Am 25.03.06, 01:19 -0300 schrieb Roberto Winter:

hi.

as i saved a file just now gimp crashed. i had it built from cvs some 10 days ago (gcc 3.3.5).
i'm using debian unstable, e16 window manager, nvidia drivers 8178 on xorg and kernel 2.6.13.1 .

on the terminal i got:

file_save_dialog_check_uri: URI = file:///home/media/fotos_tangara/xcf/tif/IMG_6384.TIF

file_save_dialog_check_uri: basename = IMG_6384.TIF file_save_dialog_check_uri: selected save_proc: NULL file_save_dialog_check_uri: URI save_proc: TIFF image file_save_dialog_check_uri: basename save_proc: TIFF image

file_save_dialog_check_uri: no save_proc was selected from the list file_save_dialog_check_uri: use URI's proc 'TIFF image' so indirect saving works
*** glibc detected *** corrupted double-linked list: 0x0a86a390 *** /opt/gimp/bin/gimp-2.3: terminated: Aborted

(script-fu:4033): LibGimpBase-WARNING **: script-fu: wire_read(): error

the image is a 8Mp photograph. it was a single layer file.

is this known? should i report a bug (i suspect it might be something with my environment, not gimp)? has it been noticed? fixed? the thing is it had been running absolutely stable the last days. and the weirder is that it crashed while doing something that i do often (saving as tif).
another thing that might matter is that the file was written fine and is not corrupted (~10Mb in size).

thanks for any help, roberto

Roberto Winter
2006-03-27 06:38:12 UTC (over 18 years ago)

crash after saving tif

On 3/26/06, Kai-Uwe Behrmann wrote:

Similiar problems where reported for CinePaint. Look at your libtiff version.

$ apt-cache policy libtiff4
libtiff4:
Installed: 3.8.0-3
Candidate: 3.8.0-3
Version Table:
*** 3.8.0-3 0
500 http://ftp.uk.debian.org unstable/main Packages 500 http://ftp.fr.debian.org unstable/main Packages 100 /var/lib/dpkg/status

If it has 3.8.0 update or downgrad. This libtiff version is

buggy.

really?
mmm... good to know!

Hopd this helps.

kind regards
Kai-Uwe Behrmann
+ development for color management + imaging / panoramas + email: ku.b@gmx.de + http://www.behrmann.name

Am 25.03.06, 01:19 -0300 schrieb Roberto Winter:

hi.

as i saved a file just now gimp crashed. i had it built from cvs some 10 days ago (gcc 3.3.5).
i'm using debian unstable, e16 window manager, nvidia drivers 8178 on

xorg

and kernel 2.6.13.1 .

on the terminal i got:

file_save_dialog_check_uri: URI = file:///home/media/fotos_tangara/xcf/tif/IMG_6384.TIF

file_save_dialog_check_uri: basename = IMG_6384.TIF file_save_dialog_check_uri: selected save_proc: NULL file_save_dialog_check_uri: URI save_proc: TIFF image file_save_dialog_check_uri: basename save_proc: TIFF image

file_save_dialog_check_uri: no save_proc was selected from the list file_save_dialog_check_uri: use URI's proc 'TIFF image' so indirect

saving

works
*** glibc detected *** corrupted double-linked list: 0x0a86a390 *** /opt/gimp/bin/gimp-2.3: terminated: Aborted

(script-fu:4033): LibGimpBase-WARNING **: script-fu: wire_read(): error

the image is a 8Mp photograph. it was a single layer file.

is this known? should i report a bug (i suspect it might be something

with

my environment, not gimp)? has it been noticed? fixed? the thing is it had been running absolutely stable the last days. and

the

weirder is that it crashed while doing something that i do often (saving

as

tif).
another thing that might matter is that the file was written fine and is

not

corrupted (~10Mb in size).

thanks for any help, roberto