[trunk] crash in gradient dialog

Bug #1392668 reported by Alexey
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Inkscape
Invalid
High
Unassigned
0.92.x
Invalid
High
Unassigned

Bug Description

Inkscape --version Inkscape 0.91+devel r (Nov 13 2014) 1:0.48+devel+13707+48~ubuntu14.04.1
Runing on Linux 3.13.0-40-generic Ubuntu 14.04.1 LTS

Steps to reproduce:

1) Create any shapes.
2) Change fill to linear gradient.
3) Create a duplicate gradient.
4) Mouse click little below gradient name(white space).
5) Press PageDown(Object-Lower hotkey) key.
6) Crash.

Terminal output:
Gtk:ERROR:/build/buildd/gtk+2.0-2.24.23/gtk/gtkrbtree.c:967:_gtk_rbtree_node_find_offset: assertion failed: (node->left)

Emergency save activated!

Emergency save document locations:
  /home/allkhor/New document 1.2014_11_14_16_17_15.0.svg
Emergency save completed. Inkscape will close now.

Edit: Try Inscape 0.91 Pre2 for Windows 8.1 crash reproduce.

Alexey (allkhor)
description: updated
Revision history for this message
Alexey (allkhor) wrote :
Revision history for this message
Alvin Penner (apenner) wrote :

confirmed on Windows XP, Inkscape rev 13646

crash message is:

**
Gtk:ERROR:gtkrbtree.c:967:_gtk_rbtree_node_find_offset: assertion failed: (node->left)

I was not able to obtain a backtrace

Changed in inkscape:
status: New → Confirmed
Revision history for this message
jazzynico (jazzynico) wrote :

Also reproduced on CrunchBang Waldorf, Inkscape 0.91.x revision 13638.
Not reproducible with 0.48.5 (different gradient dialog).

Changed in inkscape:
status: Confirmed → Triaged
tags: added: regression
Revision history for this message
jazzynico (jazzynico) wrote :

GDB backtrace attached (not very useful apparently).

Changed in inkscape:
milestone: none → 0.91.1
Revision history for this message
su_v (suv-lp) wrote :

Reproduced on OS X 10.7.5 with Inkscape 0.91+devel r13708 and 0.91pre2 r13638.

Based on the backtraces created locally this possibly is related an upstream problem similar to [1]. Reproduced with Inkscape trunk using
- GTK+/X11 2.24.13, GTK+/Quartz 2.24.17
- GTK+/X11, GTK+/Quartz 2.24.25
- GTK+/X11 3.4.4, GTK+/Quartz 3.6.4
- GTK+/X11, GTK+/Quartz 3.14.5

Attaching backtrace from Inkscape trunk r13702 using GTK+/X11 2.24.25 installed with debug symbols.

[1] GNOME bugzilla report for GTK3:
https://bugzilla.gnome.org/show_bug.cgi?id=706366

su_v (suv-lp)
Changed in inkscape:
importance: Undecided → High
Revision history for this message
su_v (suv-lp) wrote :

No longer reproduced with Inkscape 0.91+devel rev >= 14345 (the gradient list is updated as soon as the user clicks into the list, and page up/down does not trigger a crash anymore).

Rev 14345 was part of the fix for bug #1417173, and backported to the stable release branch in rev 13812.

Feel free to reopen if the same type of crash can still be triggered (maybe with different steps to reproduce).

Changed in inkscape:
status: Triaged → Fix Committed
Revision history for this message
Alexey (allkhor) wrote :

Reproduced on inkscape-trunk (1:0.91.0+devel+14389+60~ubuntu14.04.1).

Alexey (allkhor)
Changed in inkscape:
status: Fix Committed → New
su_v (suv-lp)
Changed in inkscape:
milestone: 0.91.1 → 0.92
Revision history for this message
Alvin Penner (apenner) wrote :

- crash reproduced on Windows XP, Inkscape rev 14391
- not sure if this is precisely the same bug, but probably related.

- open the attached file which already has a duplicate gradient defined in it.
- open the Fill & Stroke dialog, select the ellipse object
- click on the first gradient, # 4167
- hit PageDown button and get attached crash message

Gtk:ERROR:gtkrbtree.c:967:_gtk_rbtree_node_find_offset: assertion failed: (node->left)

the second gradient was produced as a duplicate of the first by using the + button. It is important to save this file before clicking on anything, in order to produce the crash. Clicking on the second gradient will normally cause it to disappear, so it needs to be saved before attempting to use the gradient.

Changed in inkscape:
status: New → Confirmed
Revision history for this message
Mc (mc...) wrote :

another way to trigger it :

1) Create any shapes.
2) Change fill to linear gradient.
3) Mouse click little below gradient name(white space).
4) Press "a" (it will write an "a" , for whatever reason)
5) Mouse click little below gradient name(white space). this will put the focus there, with *no gradient selected*
6) Hit PageDown, or PageUp : Crash.

Revision history for this message
su_v (suv-lp) wrote :

On 2015-10-03 02:31 (+0200), Mc wrote:
> 4) Press "a" (it will write an "a" , for whatever reason)

type-ahead find (in treeviews and lists AFAIK) - a Gtk+ feature.

Revision history for this message
su_v (suv-lp) wrote :

Variation of crash with swatch list (Fill & Stroke) linked as duplicate (to be verified separately once we have a fix):
* Bug #1437933 “crash after pressing page down in swatch manager”
   https://bugs.launchpad.net/inkscape/+bug/1437933

jazzynico (jazzynico)
Changed in inkscape:
status: Confirmed → Triaged
Revision history for this message
Alexey (allkhor) wrote :

Inkscape Trunk 0.91.0+devel+15109, crash reproduced on Xubuntu 16.04 x64

jazzynico (jazzynico)
Changed in inkscape:
milestone: 0.92 → 0.92.1
jazzynico (jazzynico)
Changed in inkscape:
milestone: 0.92.1 → 0.93
Revision history for this message
Qantas94Heavy (qantas94heavy) wrote :

Cannot reproduce using steps in description on Inkscape 0.92.4, openSUSE TW 20190301.

Changed in inkscape:
status: Triaged → Incomplete
Revision history for this message
Qantas94Heavy (qantas94heavy) wrote :

Now I can reproduce the crash, I needed an additional PgUp after the last step before it would crash.

Reproduced on 0.92.4 and 1.0alpha (75da9ac4ea, 2019-04-12).

Changed in inkscape:
status: Incomplete → Opinion
status: Opinion → Triaged
Revision history for this message
Qantas94Heavy (qantas94heavy) wrote :

Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here.

Please feel free to file new bugs about the issues you're seeing at http://inkscape.org/report.

Moved to: https://gitlab.com/inkscape/inbox/issues/374
Closed by: https://gitlab.com/Qantas94Heavy

Changed in inkscape:
status: Triaged → Invalid
tags: added: bug-migration
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.