RSS/Atom feed Twitter
Site is read-only, email is disabled

Gimp 2.4.0 rc2 access violation in WinXP - what to do?

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.

2 of 2 messages available
Toggle history

Please log in to manage your subscriptions.

Gimp 2.4.0 rc2 access violation in WinXP - what to do? buralex@gmail.com 15 Sep 17:22
  Gimp 2.4.0 rc2 access violation in WinXP - what to do? Øyvind Kolås 15 Sep 17:43
buralex@gmail.com
2007-09-15 17:22:58 UTC (about 17 years ago)

Gimp 2.4.0 rc2 access violation in WinXP - what to do?

Hi developers:

I have several times received an AV crash when double-clicking on a file to open it.
From what I've gathered lurking, this is more likely to be a GTK+ problem than a GIMP problem but with 2.4.0 final presumably just around the corner I thought I shouldn't just ignore it.

FWIW the main error (per the drmingw dump) is gimp-2.4.exe caused an Access Violation at location 00675c23 in module gimp-2.4.exe Reading from location 00000000. (I have the dump if its any use)

I searched for "product:GIMP Access Violation" in bugzilla and only found one hit :
314529 filed against
2.2.8 in 2005 and with no activity since 2007-07-25 14:29 UTC.

As a non-programming, non-developing lurker should I just ignore this, file it against Gimp (since I can't tell where it really belongs) with as much description as possible, mention it somewhere else .... ?

Regards ... Alec -- buralex-gmail

Øyvind Kolås
2007-09-15 17:43:00 UTC (about 17 years ago)

Gimp 2.4.0 rc2 access violation in WinXP - what to do?

On 9/15/07, buralex@gmail.com wrote:

I have several times received an AV crash when double-clicking on a file to open it.
>From what I've gathered lurking, this is more likely to be a GTK+ problem than a GIMP problem but with 2.4.0 final presumably just around the corner I thought I shouldn't just ignore it.

This problem has been addressed and fixed in SVN, a new pre-release with this crasher fixed should appear soon.

/Øyvind K.