Fill with color leads to a crash

Bug #179640 reported by vonHalenbach
12
Affects Status Importance Assigned to Milestone
Inkscape
Fix Released
Medium
Unassigned

Bug Description

I did fill a rectangle with the new color fill tool. Then a crash happened.

stefan@cipy:/media/ibm/inkscape$ /media/ibm/inkscape/src/inkscape

(inkscape:14851): GLib-GObject-WARNING **: value "-99" of type `gint' is invalid or out of range for property `floatx' of type `gint'
Killed

This is not the first time this happened, so i set the severity to critical.
A backtrace and a stacktrace will follow.

Tags: crash
vonHalenbach (lustik)
Changed in inkscape:
importance: Undecided → Critical
milestone: none → 0.46
status: New → Confirmed
Revision history for this message
vonHalenbach (lustik) wrote :

SVN rev. 16888 on Kubuntu 7.04

This warning line does not every time make inkscape crash. I had this line too with SVN 16763 where it was just put on the console without a crash. It is documented in another bug report, where another issue has happened.

The memory needs to be quite used/full to make this happen. So it is not so easy, to provoke.

Revision history for this message
vonHalenbach (lustik) wrote :

Here are the last 2000 lines of the backtrace from the crash. The complete backtrace is 3.7 MB big.

Revision history for this message
vonHalenbach (lustik) wrote :

I attach the file, in which the crash happened. You could hopefully provoke the crash yourself, if you use the bucket fill tool on many of those white rectangles.

Revision history for this message
Bryce Harrington (bryce) wrote :

btw, that backtrace is actually an strace.

If you can get a backtrace that would be helpful. I was unable to produce a crash with the file, although I did have fun coloring it in.

Revision history for this message
Bryce Harrington (bryce) wrote :

It's interesting that the error says value "-99". This makes me wonder if perhaps there is a preference setting or something? Could it be something in your ~/.inkscape/ preferences?

It also mentions floatx. I see that this value is used in libgdl/gdl-dock-item.c and gdl-dock.c. I wonder if perhaps you had the dock open to a particular dialog when the crash occurred?

Changed in inkscape:
status: Confirmed → Incomplete
Revision history for this message
Dread Knight (dread.knight) wrote :

I could not reproduce this bug.

Revision history for this message
vonHalenbach (lustik) wrote :

:) Nice to hear, that you had fun with the new tool. Yes, i did provide only a strace, because i get no core file when this issue happens. The last line is "killed" so it seems the program is making suecide. Maybe it is only bound to my pc/configuration. I have no clue why this happens only on my computer. It should be quite often for people who use the bucket fill tool. Normally i am able to fill only about two thirds of such a window with this tool until inkscape gets automatically killed. Do i have not enough memory? I have 313 MB Ram and 415 MB swap.

stefan@cipy:~/.inkscape$ free -m
                 total used free shared buffers cached
Mem: 313 307 6 0 11 110
-/+ buffers/cache: 185 128
Swap: 415 33 381

If no one else can confirm it, i agree to close it as invalid.

Revision history for this message
Bryce Harrington (bryce) wrote :

I'm dropping the milestone and priority on this, since while it's an issue, it sounds it may occur in limited situations. It certainly seems plausible that it could be a memory issue, and that avenue ought to be explored more. It looks like while your physical memory is almost completely in use, you've still got plenty of swap, so it probably is not a memory exhaustion issue.

It may be worthwhile to boot a different kernel (and/or distro) on the same hardware and see if the issue can be reproduced using the same version of Inkscape. If so, then it would be also useful to test on a different machine with a similar memory configuration (e.g., boot with the mem=313M kernel option).

Changed in inkscape:
importance: Critical → Medium
milestone: 0.46 → none
Changed in inkscape:
status: Incomplete → Fix Released
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.