WIN: assert when doing stamping during move

Bug #166106 reported by ScislaC
2
Affects Status Importance Assigned to Milestone
Inkscape
Fix Released
Critical
Peter Moulder

Bug Description

1) Create object (Square, Spiral, Ellispse, Star, Text,
Path... any object)
2) Click-hold on object and hit Spacebar to duplicate
3) Move mouse (which moves shape, since you are still
click-holding)

The following gets spit into the log.
---
** (inkscape.exe:1060): CRITICAL **: file seltrans.cpp:
line 301 (void sp_sel_trans_grab(SPSelTrans*, const
NR::Point&, gdouble, gdouble, gboolean)):
assertion`seltrans->stamp_cache == NULL' failed
---

Win32 11/29 build

Tags: win32
Revision history for this message
Vellum (vellum) wrote :

Confirmed for 0.40 win release 1 dec.
vellum

Revision history for this message
Peter Moulder (pjrm) wrote :

Can't reproduce with Linux/Gnu with current CVS.

In current CVS at least, stamp_cache isn't read or written
other than in seltrans.cpp. Its transitions between NULL
and non-NULL are as follows: it's set unconditionally to
NULL in the constructor and at the end of
sp_sel_trans_ungrab; it's set to non-NULL in
sp_sel_trans_stamp; and the end of sp_sel_trans_grabs
asserts that it's NULL.

v1.1 of seltrans.c has the same transitions, so I don't know
of any expert we can consult as to what's supposed to
happen, i.e. why it was believed that it should be NULL at
the end of sp_sel_trans_grab.

Can you get a backtrace for this? There are a number of
call paths to sp_sel_trans_grab.

(I.e. run `gdb inkscape.exe', then enter `break g_log',
then `commands
backtrace
end' (on three lines as given here) and then `run' and
reproduce the problem.)

One place that sp_sel_trans_stamp is called is when space is
pressed (sp_seltrans_handle_event).

Does the same problem occur with 0.39 or earlier? Does it
occur with sodipodi?

Revision history for this message
Vellum (vellum) wrote :

win2000 build 16/1/05

I cannot reproduce this problem. Tried circles, spirals,
rectangles and stars.

vellum

Revision history for this message
Robo210-users (robo210-users) wrote :

This appears to be fixed by the 1-17-05 build.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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