Crash: Microsoft Visual C++ Runtime Library

Bug #656733 reported by iglooo101
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Inkscape
Fix Released
High
Unassigned

Bug Description

Crash: Microsoft Visual C++ Runtime Library

Tags: color crash
Revision history for this message
iglooo101 (iglooo101) wrote :
Revision history for this message
iglooo101 (iglooo101) wrote :

Ink: 48
O/S: vista 32

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

> short video showing the error messages after Inkscape crashed, apparently while the paint bucket tool was used

Did the crash happen when you wanted to fill another area? If so, which part of the drawing did you click on?
Or did it happen while you were increasing the amount of blur (58.6 %) of the just created path (5900 nodes)?
Or did another action trigger the crash (changing zoom, switching tool, changing fill color, …)?

<off-topic>A minimum amount of context information about a crash, using one or two sentences, would really be appreciated and help with bug triage.</off-topic>

tags: added: color crash
Changed in inkscape:
importance: Undecided → High
Revision history for this message
iglooo101 (iglooo101) wrote :

@ #3
>Did the crash happen when you wanted to fill another area? If so, which part of the drawing did you click on?
>Or did it happen while you were increasing the amount of blur (58.6 %)
I cannot tell 100% which of these 2 has caused the crash because I have done both BUCKET and BLUR..
But, it might be "while you were increasing the amount of blur" because that was my last thing I have done.
The crash did not come suddenly.
I felt like that the application was slowing down .
Then the crash has happened

Revision history for this message
Pablo Trabajos (pajarico) wrote :

Using the bucket tool at high zoom level over the blurred area causes a crash when memory usage reaches 1,327,000 KB.

But without proper context it's impossible to say if it is the same problem.

Revision history for this message
Pablo Trabajos (pajarico) wrote :

Tweaking the blur didn't cause a crash for me.
0.48 r9983 and win 7.

Revision history for this message
jazzynico (jazzynico) wrote :

Reproduced on Windows 7, Inkscape 0.48.4.

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

Error message:
terminate called after throwing an instance of 'std::bad_alloc'
  what(): std::bad_alloc

No gdb trace (always a bit tricky on Windows).

Revision history for this message
jazzynico (jazzynico) wrote :

Not reproduced with trunk revision 12006.
The memory consumption is about 10 times lower, and the same actions with the bucket on the blured area doesn't trigger the crash.

Changed in inkscape:
milestone: none → 0.49
status: Triaged → Fix Committed
Bryce Harrington (bryce)
Changed in inkscape:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

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