inkscape crashes during pdf import

Bug #305741 reported by Stefan Seefeld on 2008-12-06
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Inkscape
High
Unassigned

Bug Description

inkscape crashes when I attempt to import the attached pdf file. I'm using version 0.46, on Fedora 9 (x86_64).
Thanks,
          Stefan

Alvin Penner (apenner) wrote :

cannot reproduce this problem on Win32 Inkscape 0.46 from April 1

I can confirm that it works on Win32, i.e. it appears to be a platform-specific bug.

stanley (matthieulesaec) wrote :

I work on windows xp sp2, inkscape 0.46.

I tried to open an unprotected pdf document. unsuccessfully :(
The window "Microsoft Visual C++ Runtime Library" appears and says
"
    Runtime Error!
    Program C:\Program Files\Inkscape\inkscape.exe

    This application has requested the Runtime to terminate it in an unusual way.
    PLease contact the application's support team for more information
"

Thanx

Alvin Penner (apenner) wrote :

running Win32 build 20655, I was able to load this file. However, when I tried to zoom in, it brought my computer to its knees.

Task Manager showed two instances of Inkscape, both of them "Not Responding", and memory usage was about 60 Megabytes and climbing, at which point I aborted Inkscape.

stanley (matthieulesaec) wrote :

Thanx for testing.

This means my file is too big ?

A friend was able to open it on Adobe Illustrator (MACOSX 10.5, CS3) so it is openable.

My system is XP sp3
My hardware
intel core 2 CPU T56000 @ 1.83 Ghz
987 MHz, O,99 RAM

it s not enough power so that could be why it crashed down ?
hem, please where can i know wich build i have exactly ?

Alvin Penner (apenner) wrote :

you can find out which version by clicking on the menu item Help | About.
For example, the latest stable release may report something like : Inkscape 0.46, built Apr 1 2008

As to the memory usage, that is an Inkscape problem, not the fault of the file. This file loads normally into Adobe Reader.

theAdib (theadib) wrote :

Stanley, running Ubuntu and latest Inkscape-devel rev20670 it consumes 1.1GB RAM. So your memory is not sufficient.

Stefan, running latest Inkscape-devel there is a warning that pango can not find the font referenced in the pdf.
 WARNING **: Schrift ohne zugehörige Schriftfamilie wird ignoriert, damit Pango nicht abstürzt
However running Inkscape-0.46 it shows the pdf with no error nor warning.
Could you test using a daily build?

Adib.

vonHalenbach (lustik) wrote :

This bug could be related to the font-matching-bug. If the font is missing, inkscape tries to find a replacement. maybe it fails sometimes and because of this, inkscape crashes.

stanley (matthieulesaec) wrote :

Thanx all.

My build is 0,46 april 12008.

The font used seems to be Conduit SC-Extra Light (found with http://new.myfonts.com/WhatTheFont/ ). It's installed on my labtop because i can read the pdf on adobe reader. So i guess it s not the reason inkscape crashes, or inkscape itself cannot recognize the font ?

I would have guessed swap memory or equivalent can compensate my lack of RAM, can't it ?

Hm, it should not crash.
Stefan, can you provide a backtrace?
Adib.
---
On Fri, Feb 13, 2009 at 10:39 AM, stanley <email address hidden> wrote:
> Thanx all.
>
> My build is 0,46 april 12008.
>
> The font used seems to be Conduit SC-Extra Light (found with
> http://new.myfonts.com/WhatTheFont/ ). It's installed on my labtop
> because i can read the pdf on adobe reader. So i guess it s not the
> reason inkscape crashes, or inkscape itself cannot recognize the font ?
>
> I would have guessed swap memory or equivalent can compensate my lack of
> RAM, can't it ?
>
> --
> inkscape crashes during pdf import
> https://bugs.launchpad.net/bugs/305741
> You received this bug notification because you are a member of Inkscape
> Bug Team, which is subscribed to Inkscape.
>

This is what gdb tells me:

...
(no debugging symbols found)

Program received signal SIGSEGV, Segmentation fault.
0x000000359b6bb6f9 in Gfx8BitFont::getNextChar () from /usr/lib64/libpoppler.so.3

Sorry, forgot to mention: I find no traces of it trying to use a substitute font. The first message I get is the dialog telling me that the application just crashed. And on stdout I get "Emergency save activated!
 ..."

Thanks,

theAdib (theadib) wrote :

guess this is a poppler issue. I posted a bug-report there https://bugs.freedesktop.org/show_bug.cgi?id=20108
Let's wait if they accept.
Adib.

for windows go to http://inkscape.modevia.com/win32/?M=D get the files for symbols and debug.

I use these for debugging on windows

I can not reproduce this on my windows xp sp2, windows xp sp3, or vista.

Now I also can not reproduce it in Ubuntu 8.04.2, 8.10; 86 or 86_64 ppc. Debian 4 86 86_64 or ppc. Fedora 9 or 10. I will try it Solaris, Open Solaris, and Mac OS X

On the Fedora 9 10 it was on 86, 86_64 on solaris, Open Solaris, Mac OSX. open fine I opened file no errors. in solaris in dtrace in container and others I stressed to the max zooming in. Opened and no problems

bbyak (buliabyak) wrote :

please attach the font, maybe installing it will make this reproducible

What font ?

theAdib (theadib) wrote :

According to the replay from poppler team this is not an poppler issue.
At least on poppler 0.10.4 . Which version do we use?

---
http://bugs.freedesktop.org/show_bug.cgi?id=20108

--- Comment #1 from Albert Astals Cid <email address hidden> 2009-02-25 14:35:50 PST ---
The file opens perfectly on poppler 0.10.4 test programs so if it crashes it
must be something the inkscape guys (not sure if you are of them) are doing
wrong, that or either you are on an old poppler version.

If you are using poppler 0.10.4 and are a inkscape programmer and it still
crashes, reopen the bug and point me to the poppler using code in inkscape and
post a full bt.

If above conditions are not met, find someone that can meet them.

TheAdib,

I use use the latest. poppler 0.10.4 and poppler-data-0.2.1.tar.gz I will try to revert to an older one to see if it happens maybe the fact that I use the new version is why I don't get the flaw. I will try some break points and see if I can get it to error. Then see what fixes it if I find a fix I will create a patch for everyone if it is just update then I will be able to tell you.

I am not a developer on Inkscape. I don't believe I have commit access anyway, but if I get patches I will submit here for you all to check out after testing.

Best Regards,
Leo

su_v (suv-lp) wrote :

Could this be the same issue as in the more recent reports
Bug #394472: Wrong characters in imported PDF
Bug #369861: Unable to open previously imported pdf file ?

steps:
1) open 2nd test file <http://launchpadlibrarian.net/22546261/Sch%C3%A9ma%20%C3%A9olien%20-%20Avifaune.pdf> with inkscape.
2) save as svg
3) reopen in inkscape fails (no crash)

I tried both 'Replace PDF Fonts' options when importing: both failed to load as svg and produced the same error & console msgs.

console msg:

/Volumes/blue/img/Inkscape/test/bug/305741-Avifaune-LeWitt.svg:32491: parser error : Input is not proper UTF-8, indicate encoding !
Bytes: 0xBF 0xE9 0x0D 0xAC
               id="tspan22342">��
                               ^

tested with Inkscape 0.46+devel r21714, OS X 10.5.7

su_v (suv-lp) wrote :

changing $LANG (before importing the pdf file) from "en_US.UTF-8" to "fr_FR.UTF-8" (assumption based on the filename/content) in the launch script: inkscape saves a svg file (PDF Fonts replaced on import) that produces additional console msgs when reopening fails:

hundreds of 'parser errors : PCDATA invalid Char value 12':
/Volumes/blue/img/Inkscape/test/bug/305741-Avifaune-fr_FR.UTF-8-LeWitt.svg:32496: parser error : PCDATA invalid Char value 12
               id="tspan22344">

</tspan><tspan
                               ^
[…]
/Volumes/blue/img/Inkscape/test/bug/305741-Avifaune-fr_FR.UTF-8-LeWitt.svg:33569: parser error : PCDATA invalid Char value 12
               id="tspan22908">

</tspan></text>
                                        ^

su_v (suv-lp) wrote :

crash not reproduced with Inkscape 0.47+devel r9106 on OS X 10.5.8 (poppler 0.12.1), however I get these console messages after opening 'image.pdf' in Inkscape:

Error: profile is unsuitable for input
Error: Can't create transform
Error: profile is unsuitable for input
Error: Can't create transform

@Stefan - do you still get a crash when opening 'image.pdf' in the current stable version (Inkscape 0.47)?

---
LeWitt:bug suv$ pdfinfo image.pdf
Title: radartutorialpart4.pdf
Author: stefan
Creator: Adobe Acrobat 8.0
Producer: GPL Ghostscript 8.63
CreationDate: Sat Dec 6 09:51:27 2008
ModDate: Sat Dec 6 09:51:27 2008
Tagged: no
Pages: 1
Encrypted: no
Page size: 612 x 792 pts (letter)
File size: 31826 bytes
Optimized: no
PDF version: 1.4
LeWitt:bug suv$

Changed in inkscape:
status: New → Incomplete
jazzynico (jazzynico) on 2010-09-09
Changed in inkscape:
importance: Undecided → High
ScislaC (scislac) wrote :

Closing as won't fix since there are no stable distros currently using that old version of poppler any longer. If you feel this was closed in error, please feel free to reopen it and explain why.

Changed in inkscape:
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Related blueprints

Remote bug watches

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