Trace Pixel Art crashes on large image

[mezastel]

I am running Inkscape 0.91 on Windows and am trying to trace large pixel art images. The confirmation dialog pops up, but when I click OK, Inkscape just crashes.

[su_v (suv-lp)]

Which installer did you use for Inkscape 0.91 - 32bit or 64bit?

To allow further investigation of the reported issue, please attach a test case (Inkscape SVG file, or one of the pixel art images which produce the reported crash), and provide details about
- bitmap image import settings
- settings for 'Trace Bitmap' (or 'Trace Pixel Art') [1]

--
[1] it is not clear from the description which trace method you used - 'pixel art' and 'large' are somewhat opposite terms.

[mezastel (dmitrinesteruk)]

I am using a 64-bit version of Inkscape.

I attach a test image. I am using the tool Path|Trace Pixel Art with the settings 1.000, 5, 4 and 1.000 and the output is B-spline curves.

[jazzynico (jazzynico)]

Tested on WIndows XP (32bit) with Inkscape 0.91 and trunk rev. 14274.

Inkscape doesn't crash, but hangs (I had to kill the application after 25 minutes or so).

[mezastel (dmitrinesteruk)]

Well, if it's a performance problem, I'd be interested to hear whether it
has a possible fix (e.g., Xeon Phi or CUDA based).

On 5 August 2015 at 15:51, jazzynico <email address hidden> wrote:

> Tested on WIndows XP (32bit) with Inkscape 0.91 and trunk rev. 14274.
>
> Inkscape doesn't crash, but hangs (I had to kill the application after
> 25 minutes or so).
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1480419
>
> Title:
> Trace Pixel Art crashes on large image
>
> Status in Inkscape:
> New
>
> Bug description:
> I am running Inkscape 0.91 on Windows and am trying to trace large
> pixel art images. The confirmation dialog pops up, but when I click
> OK, Inkscape just crashes.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/inkscape/+bug/1480419/+subscriptions
>

--
Dmitri Nesteruk
<email address hidden>
skype: dmitri.nesteruk

[su_v (suv-lp)]

@vinipsmaker - any chance you could comment?

[Vinipsmaker (vinipsmaker)]

@suv:

Leave bugs in my code to me. I don't want to steal development time from you guys. I mean, I don't want you guys have less time to work on the rest of Inkscape because you're trying to fix bugs in my code.

The first thing is that I cannot test on Windows. I managed to reproduce the bug in Linux, though.

Strangely, the CLI version of depixelize won't crash on the same image. I need to do other tasks now, but I may be able to look further in this issue at the weekend.

[Abhisek Maiti (mail2abhisek-maiti)]

The bug is not fixed. Facing the same issue under Linux x64. GDB trace as follows:

Starting program: /usr/bin/inkscape
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x7fffe4ecf700 (LWP 3980)]
[New Thread 0x7fffe46ce700 (LWP 3981)]
[New Thread 0x7fffe3ecd700 (LWP 3982)]
[New Thread 0x7fffe1d25700 (LWP 3983)]
[New Thread 0x7fffd6a3f700 (LWP 3984)]
[New Thread 0x7fffd5a3c700 (LWP 3985)]
[Thread 0x7fffd5a3c700 (LWP 3985) exited]
[New Thread 0x7fffd5a3c700 (LWP 3987)]
The program 'inkscape' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadDrawable (invalid Pixmap or Window parameter)'.
  (Details: serial 27601 error_code 9 request_code 71 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
[Thread 0x7fffd5a3c700 (LWP 3987) exited]
[Thread 0x7fffd6a3f700 (LWP 3984) exited]
[Thread 0x7fffe1d25700 (LWP 3983) exited]
[Thread 0x7fffe3ecd700 (LWP 3982) exited]
[Thread 0x7fffe46ce700 (LWP 3981) exited]
[Thread 0x7fffe4ecf700 (LWP 3980) exited]
[Inferior 1 (process 3976) exited with code 01]

[[e-mail] (faranta)]

Any ETA on this bug? I see it's been three years so maybe it's time to quit and find a workaround or something.

I just discovered this after trying to convert a tiny fraction of an image on Windows using the default settings (attached).

[Val Henschen (sweetpearose)]

October 2019. This is still an issue. Is there a status?

[localalex (localalex-b)]

December, still crashes with a warning of a large image. However, the image i am using isn't particularly large or complex, 800 by 650 px. reducing pixel count does not help either, still crash inkscape..