Re: [Gimp-user] "crash" I've seen Gimp recover one a while back. Is that an automatic feature?

[Liam R E Quin]

On Fri, 2022-08-19 at 03:05 -0500, William Phelps via gimp-user-list
wrote:

> [empty message]

Yes. Unfortunately it's not 100% reliable, but it does try.

liam


-- 
Liam Quin - paligo.net, delightfulcomputing.com
Cancer gofundme https://www.gofundme.com/f/5u9v7-every-little-helps
Vintage pictures & texts https://www.fromoldbooks.org/
___
gimp-user-list mailing list
List address:gimp-user-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
List archives:   https://mail.gnome.org/archives/gimp-user-list

[Gimp-user] "crash" I've seen Gimp recover one a while back. Is that an automatic feature?

[William Phelps via gimp-user-list]

___
gimp-user-list mailing list
List address:gimp-user-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
List archives:   https://mail.gnome.org/archives/gimp-user-list

Re: [Gimp-user] Crash after new install

[Jernej Simončič]

On Wed, 16 Jan 2019 16:01:10 +0100, Cahjr wrote:

> If any suggestions can be had, i'll listen; because I deleted the old Gimp 
> 2.08
> install program, so I cannot revert back to the older version, unless it is
> still available from any download site.

Make sure you download the latest installer from www.gimp.org - the error
you're seeing was present in the original 2.10.8 installer, but was fixed
in one of the updates.

-- 
< Jernej Simončič ><><><><>< http://eternallybored.org/ >

___
gimp-user-list mailing list
List address:gimp-user-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
List archives:   https://mail.gnome.org/archives/gimp-user-list

[Gimp-user] Crash after new install

[Cahjr]

I just updated (not uninstall first) from Gimp 2.08 to 2.10 on a Win32bit Win7
machine. After running the install program this popped on the screen. Gimp 2.08
was running before without crashing.

If any suggestions can be had, i'll listen; because I deleted the old Gimp 2.08
install program, so I cannot revert back to the older version, unless it is
still available from any download site.

I have an attached screenshot ... 
thanks 

Attachments:
* https://www.gimpusers.com/system/attachments/1094/original/Gimp_crash.JPG

-- 
Cahjr (via www.gimpusers.com/forums)
___
gimp-user-list mailing list
List address:gimp-user-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
List archives:   https://mail.gnome.org/archives/gimp-user-list

[Gimp-user] Crash after new install

[Cahjr]

>I just updated (not uninstall first) from Gimp 2.08 to 2.10 on a
>Win32bit Win7 machine. After running the install program this popped
>on the screen. Gimp 2.08 was running before without crashing.
>
>If any suggestions can be had, i'll listen; because I deleted the old
>Gimp 2.08 install program, so I cannot revert back to the older
>version, unless it is still available from any download site.
>
>I have an attached screenshot ... 
>thanks
Ok I just clicked the "OK" button in the popup box, and GIMP 2.10 loaded up and
is running 

And I just assumed (like an idiot) that this was a usual Windows crash that
would stop GIMP from running ...
You guys did an awesome job of app recovery coding ... most of the time, a crash
like this; and your stuck with software that is broke ...

-- 
Cahjr (via www.gimpusers.com/forums)
___
gimp-user-list mailing list
List address:gimp-user-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
List archives:   https://mail.gnome.org/archives/gimp-user-list

Re: [Gimp-user] Crash after Rotate

[Partha Bagchi]

You should submit this to the developer list or file a bug report.

There was a recent bugrepot like this for the Mac. It was fixed by Ell in
the master branch.

On Mon, Sep 25, 2017 at 10:21 AM, Wiel Aerts  wrote:

>
> Hello All,
>
> I'm using GIMP 2.9.7, an unstable development release
> commit 6dfe04e9283f8435979758ac7a1519481bc73694.
>
> I'm not shure this is the right place to tell about a new problem (at
> least for me the last couple of weeks).
>
> I load some picture (jpeg, tiff doesn't matter), from the toolbox choose
> "rotate", rotate some degrees (corrective).
> If rotation is complete start "Curves". Then GIMP immediately crashes.
>
> The last sentence from stderr/stdout was:
>
> gimp_color_transform_new: using babl for 'linear TRC variant generated by
> GIMP' -> 'GIMP built-in sRGB'
> using gegl copy
> gimp: fatal error: Segmentation fault
> gimp (pid:5664): [E]xit, [H]alt, show [S]tack trace or [P]roceed:
>
> When I immediately after rotate the file save (xcf file), that after
> opening apply "Curves" it also crashes.
>
> Hope I could help (you developers are doing great job).
>
> Greetings,
> Wiel
>
> ___
> gimp-user-list mailing list
> List address:gimp-user-list@gnome.org
> List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
> List archives:   https://mail.gnome.org/archives/gimp-user-list
>
___
gimp-user-list mailing list
List address:gimp-user-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
List archives:   https://mail.gnome.org/archives/gimp-user-list

Re: [Gimp-user] Crash when opening/processing files in quick succession

[Jehan Pagès]

Hi,

On Fri, Jul 1, 2016 at 2:08 PM, Matthew Malthouse  wrote:
> On 30 June 2016 at 08:41, Ofnuts  wrote:
>
>>
>> Processing and disk space are cheap. Script the whole lot, eyeball the
>> results, and redo the odd ones manually (or with a different script). Or
>> first do a visual check, split in two batches, one processed with
>> auto-levels and one without, and apply a different script on each batch.
>
>
> In the end that's what I did.  Couldn't get Gimp script  on command line to
> work* so used Fred Weinhaus' autowhite
>  script which
> employs the Imagemagick function suit.
>
> It was very effective, only 4 of 325 needed re-doing.

Even though you found a more effective way to do it, we'd still
welcome a bug report with your stacktrace and step-by-step
reproduction steps. :-)
Thanks!

Jehan

> Matthew
>
> * gimp -i -b '(batch-levels-stretch "*.jpg")' -b '(gimp-quit 0)' resulted in
>
>
> (ufraw-gimp:5401): Gtk-WARNING **: Unable to locate theme engine in
> module_path: "pixmap",
> While parsing XMP metadata:
> Error on line 46 char 1: End of element  not expected in this
> context
> While parsing XMP metadata:
> Error on line 56 char 1: End of element  not expected in this
> context
>
> Metadata parasite seems to be corrupt
> While parsing XMP metadata:
> Error on line 46 char 1: End of element  not expected in this
> context
>
> ** (file-jpeg:5404): WARNING **: JPEG - unable to decode XMP metadata packet
> ___
> gimp-user-list mailing list
> List address:gimp-user-list@gnome.org
> List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
> List archives:   https://mail.gnome.org/archives/gimp-user-list



-- 
ZeMarmot open animation film
http://film.zemarmot.net
Patreon: https://patreon.com/zemarmot
Tipeee: https://www.tipeee.com/zemarmot
___
gimp-user-list mailing list
List address:gimp-user-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
List archives:   https://mail.gnome.org/archives/gimp-user-list

Re: [Gimp-user] Crash when opening/processing files in quick succession

[Matthew Malthouse]

On 30 June 2016 at 08:41, Ofnuts  wrote:

>
> Processing and disk space are cheap. Script the whole lot, eyeball the
> results, and redo the odd ones manually (or with a different script). Or
> first do a visual check, split in two batches, one processed with
> auto-levels and one without, and apply a different script on each batch.


In the end that's what I did.  Couldn't get Gimp script  on command line to
work* so used Fred Weinhaus' autowhite
 script which
employs the Imagemagick function suit.

It was very effective, only 4 of 325 needed re-doing.

Matthew

* gimp -i -b '(batch-levels-stretch "*.jpg")' -b '(gimp-quit 0)' resulted in


(ufraw-gimp:5401): Gtk-WARNING **: Unable to locate theme engine in
module_path: "pixmap",
While parsing XMP metadata:
Error on line 46 char 1: End of element  not expected in this
context
While parsing XMP metadata:
Error on line 56 char 1: End of element  not expected in this
context

Metadata parasite seems to be corrupt
While parsing XMP metadata:
Error on line 46 char 1: End of element  not expected in this
context

** (file-jpeg:5404): WARNING **: JPEG - unable to decode XMP metadata packet
___
gimp-user-list mailing list
List address:gimp-user-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
List archives:   https://mail.gnome.org/archives/gimp-user-list

Re: [Gimp-user] Crash when opening/processing files in quick succession

[Matthew Malthouse]

On 30 June 2016 at 00:43, Jehan Pagès  wrote:

>
> Could you try the last version of GIMP (2.8.16) and if the problem
>

This is strange, GUI Gimp's "About", gimp --version and Software Center all
agree that it's actually 2.8.16.  Only Ubuntu's crash reporter says 2.8.12.

#> gimp --version
GNU Image Manipulation Program version 2.8.16





> still persists, could you run GIMP in gdb, get a stacktrace upon the
> crash and open a bug report with this information please?
> More about getting a stacktrace:
>
> https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces/Details
> For bug reports: https://bugzilla.gnome.org/enter_bug.cgi?product=GIMP


Okay.  Had to install some debugging symbol libraries to get more than ??
but done, and the problem is repeatable. So will submit.

Thanks,

Matthew
___
gimp-user-list mailing list
List address:gimp-user-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
List archives:   https://mail.gnome.org/archives/gimp-user-list

Re: [Gimp-user] Crash when opening/processing files in quick succession

[Ofnuts]

On 29/06/16 19:05, Matthew Malthouse wrote:

I don't want to batch script because I need to eyeball the images to catch
the occasional ones where auto-levels is a bad idea.


Processing and disk space are cheap. Script the whole lot, eyeball the 
results, and redo the odd ones manually (or with a different script). Or 
first do a visual check, split in two batches, one processed with 
auto-levels and one without, and apply a different script on each batch.

___
gimp-user-list mailing list
List address:gimp-user-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
List archives:   https://mail.gnome.org/archives/gimp-user-list

Re: [Gimp-user] Crash when opening/processing files in quick succession

[Mark Morin]

On 6/29/2016 1:05 PM, Matthew Malthouse wrote:

Over the last two days I've processed about 500 JPG files.  Typically:

Open, auto levels (on F10 key) or manual, Crop or resize, maybe unsharp
mask, overwrite (F9 key) with my default jpeg settings.  each takes between
1 and 3 minutes.  So fairly leisurely.

But the next group has already been processed for crop and size so all I
need to is auto levels and over rewrite, keying:

Ctrl-O, ↓, ↓, Ent, F10, F9, Ent, Ctrl-W Ctrl-D

Open, down-arrow twice to select next image, enter, auto-levels, overwrite,
enter, close, discard changes.

It's very rapid, processing four or five images a minute...

But after 5 or 6 images Gimp crashes  —  here are bits from the crash report

Segfault happened at: 0x71524: cmp %eax,(%r12)
PC(0x00715254) ok
source (%eax" ok
destination "(%r12)" (0x) not located in a known VMA region (needed
writable region)!

gimp 2.8.12-0trusty2~ppa [prigin:LP-PPA-otto-kesselgulasch-gimp]
gimp-2.8 crashed with SUGSEGV in file_open_image()
and64
Ubunty 14.04
Unity
Ubuntu 3.13.0-91.138-generic 3.13.11-ckt39



4-core hyperthreaded (so 8 virtual) 16 Gb RAM, gimp allocated 8195 tile
cache memory.


Computers a supposed to be faster than mere humans so I'm boggled that this
should happen just because I'm doing things more rapidly than before.


I don't have a fix but I do know that if I were doing all these 
underlying calculations "by hand," the first one would probably be done 
around Christmas time.




___
gimp-user-list mailing list
List address:gimp-user-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
List archives:   https://mail.gnome.org/archives/gimp-user-list

[Gimp-user] Crash when opening/processing files in quick succession

[Matthew Malthouse]

Over the last two days I've processed about 500 JPG files.  Typically:

Open, auto levels (on F10 key) or manual, Crop or resize, maybe unsharp
mask, overwrite (F9 key) with my default jpeg settings.  each takes between
1 and 3 minutes.  So fairly leisurely.

But the next group has already been processed for crop and size so all I
need to is auto levels and over rewrite, keying:

Ctrl-O, ↓, ↓, Ent, F10, F9, Ent, Ctrl-W Ctrl-D

Open, down-arrow twice to select next image, enter, auto-levels, overwrite,
enter, close, discard changes.

It's very rapid, processing four or five images a minute...

But after 5 or 6 images Gimp crashes  —  here are bits from the crash report

Segfault happened at: 0x71524: cmp %eax,(%r12)
PC(0x00715254) ok
source (%eax" ok
destination "(%r12)" (0x) not located in a known VMA region (needed
writable region)!

gimp 2.8.12-0trusty2~ppa [prigin:LP-PPA-otto-kesselgulasch-gimp]
gimp-2.8 crashed with SUGSEGV in file_open_image()
and64
Ubunty 14.04
Unity
Ubuntu 3.13.0-91.138-generic 3.13.11-ckt39



4-core hyperthreaded (so 8 virtual) 16 Gb RAM, gimp allocated 8195 tile
cache memory.


Computers a supposed to be faster than mere humans so I'm boggled that this
should happen just because I'm doing things more rapidly than before.

Is there a fix?

I don't want to batch script because I need to eyeball the images to catch
the occasional ones where auto-levels is a bad idea.


Matthew
___
gimp-user-list mailing list
List address:gimp-user-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
List archives:   https://mail.gnome.org/archives/gimp-user-list

Re: [Gimp-user] Crash

[Kevin Brubeck Unhammer]

Rob Antonishen rob.antonis...@gmail.com writes:

 On Wed, Nov 30, 2011 at 4:12 AM, Kevin Brubeck Unhammer unham...@fsfe.org 
 wrote:

 Bob Long writes:

  Stefan Maerz wrote,
 
  [..]
 
  It is possible to write a python-fu versioning system, right? I've yet
  to do anything with python-fu so I'm not sure.
 
  -Stefan
 
  I've never used it, but look at:
  http://registry.gimp.org/node/14246
 
  It will save a backup copy of your active image as
  [imagename]--MM-DD-HH-MM.xcfgz in the same directory as your
  active image.

 Just tried it, it works great :)

 Note: if you do two backups within one minute, only the last one will be
 saved. That's not really a bug though ;)

 Would you like it to not overwrite?  I can change it fairly easily, by 
 extending the
 naming convention to add seconds :)

For me it's sufficient, but perhaps others make more frequent backups?
I just noticed because I was purposely testing for it.

-Kevin

___
gimp-user-list mailing list
gimp-user-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gimp-user-list

Re: [Gimp-user] Crash

[Daniel Smith]

This thread brings back such memories.
I used to work in graphics making the phone book and we used
Canvas and Photoshop on 486DX, not even pentium, PCs!
Talk about slow! I can remember actually remaking bitmaps from old files
etc, taking parts out or adding, etc, by hand, pixel by pixel.
I used to joke about how I was going in, to a place where I could no longer
be reached, like at 1000+ percent zoom or whatever.

The other day I tried to open (on my present laptop) some images in gimp, real
big ones from my digital camera. Mistakenly I tried 48 of them at
once. It got to about
processing 16 of them, none open yet, before I shut it off. Just like the
old days!!!
:)

Dan


On 12/1/11, Kevin Brubeck Unhammer unham...@fsfe.org wrote:
 Rob Antonishen rob.antonis...@gmail.com writes:

 On Wed, Nov 30, 2011 at 4:12 AM, Kevin Brubeck Unhammer
 unham...@fsfe.org wrote:

 Bob Long writes:

  Stefan Maerz wrote,
 
  [..]
 
  It is possible to write a python-fu versioning system, right? I've
 yet
  to do anything with python-fu so I'm not sure.
 
  -Stefan
 
  I've never used it, but look at:
  http://registry.gimp.org/node/14246
 
  It will save a backup copy of your active image as
  [imagename]--MM-DD-HH-MM.xcfgz in the same directory as your
  active image.

 Just tried it, it works great :)

 Note: if you do two backups within one minute, only the last one will
 be
 saved. That's not really a bug though ;)

 Would you like it to not overwrite?  I can change it fairly easily, by
 extending the
 naming convention to add seconds :)

 For me it's sufficient, but perhaps others make more frequent backups?
 I just noticed because I was purposely testing for it.

 -Kevin

 ___
 gimp-user-list mailing list
 gimp-user-list@gnome.org
 http://mail.gnome.org/mailman/listinfo/gimp-user-list

___
gimp-user-list mailing list
gimp-user-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gimp-user-list

Re: [Gimp-user] Crash

[Kevin Brubeck Unhammer]

Destiny Bottino desbo...@yahoo.com writes:

 Hello,
 I was recently working on a big project of mine using GIMP. I had spent 5 
 hours straight
 working on it, saving it every 5 minutes, and then GIMP crashed and lost 
 everything but
 a few layers. This was not a saving issue because the layers that stayed were 
 made at
 completely different times. I lost pretty much all my work and I am furious. 
 I don't
 have time to do it all over again. I'm pretty sure there is no way of 
 bringing it back.
 GIMP is a wonderful drawing program and I use it all the time, but this was 
 just too
 overboard for me. It crashes almost everytime I use it but all those other 
 times,
 everything was saved alright and everything was fine. This time one of my 
 best drawings
 was lost and there is no way of bringing it back (trust me, I've tried 
 everything). I am
 letting you know because I don't want this to happen to anyone else and (even 
 though I
 am certain nothing can fix it) is there anyway to bring my drawing back? I 
 put my best
 work into it and it makes me furious that its gone. Please, if anyone knows 
 how to bring
 it back, please help me. This drawing meant a lot to me.

You might want to upload the xcf somewhere if you want people to help
with trying to get it back.

Howver, being able to keep a few layers (as opposed to completely losing
the whole file) does sound very odd (your harddrive isn't making strange
ticking noises, is it?).

In any case, if you're getting a lot of crashes, do ensure you're
running the newest version (click Help→About, should say 2.6.11). You
might also want to invest in some more RAM (I've got 3GB, haven't had a
GIMP crash in over a year).



best regards,
-Kevin

___
gimp-user-list mailing list
gimp-user-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gimp-user-list

Re: [Gimp-user] Crash

[Chris Mohler]

On Mon, Nov 28, 2011 at 6:16 PM, Destiny Bottino desbo...@yahoo.com wrote:
 I was recently working on a big project of mine using GIMP. I had spent 5
 hours straight working on it, saving it every 5 minutes

Personally, after a couple of hours or so of work (in any graphics
program), I usually do a File-Save As and append a number to the
filename.  So if I start a project, I'll save it as something like
my_project_01.xcf, then after a while save as my_project_02.xcf -
that way even if I close or crash GIMP I have a series of 'snapshots'
of the project I can go back to if needed.  This has saved me from
disaster more than once - I've seen everything from lightning strikes
to pets eating power cords, not to mention pilot error ;)

OTOH, I hardly ever crash GIMP - you definitely should try and track
down the cause of those crashes also.

Chris
___
gimp-user-list mailing list
gimp-user-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gimp-user-list

Re: [Gimp-user] Crash

[Stefan Maerz]

On 11/29/2011 3:16 PM, Frank Gore wrote:

On Tue, Nov 29, 2011 at 4:06 PM, Chris Mohlercr33...@gmail.com  wrote:

Personally, after a couple of hours or so of work (in any graphics
program), I usually do a File-Save As and append a number to the
filename.  So if I start a project, I'll save it as something like
my_project_01.xcf, then after a while save as my_project_02.xcf -
that way even if I close or crash GIMP I have a series of 'snapshots'
of the project I can go back to if needed.

I'd say the workflow you describe is probably one of the best ones to
adopt when working on any large graphic project. That's how all the
employees (including myself) did it when I worked for a multimedia
company, and it saved my ass more than once.
It is possible to write a python-fu versioning system, right? I've yet 
to do anything with python-fu so I'm not sure.


-Stefan
___
gimp-user-list mailing list
gimp-user-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gimp-user-list