Inkscape crashes when opening files 0.91

[Mike Gallagher]

I am reporting a bug with the inkscape 0.91 software. when we open up a inkscape drawing (svg.) we are getting a major error which closes the inkscape application. inkscape 0.91 will not open svg. pages and we are getting inkscape encountered an internal error and will close now message. This seems to be happening on some drawings and not others.

SVG Drawings are here
https://drive.google.com/drive/folders/0BxBSGlqXeZHYNVZhQjhWS2Fzbzg?usp=sharing

Screenshot of error message is here
https://drive.google.com/open?id=0BxBSGlqXeZHYSG44ckJJZUhOTkE

Ticket
Question #577239

[TylerDurden (8thrule)]

Cannot reproduce with Inkscape 0.92.1 r15371, Win 8.1, 64 bit.

All files open here ok.

TD

[Mike Gallagher (mike-gallagher)]

OS used is windows 7

[Mike Gallagher (mike-gallagher)]

Inkscape 0.91 32 bit install.

[Brynn (brynn4inks-deactivatedaccount)]

All opening ok for me too. Inkscape 0.92.1, 64-bit, exe installer, windows 7 Pro, 64-bit

However, using 0.91, 32-bit, they will not open (encountered error, will close now).

I don't have the right kind of knowledge to figure out why this is happening. But if you can upgrade, it sounds like that might solve the problem for you.

[jazzynico (jazzynico)]

Crash reproduced on Windows 7 Inkscape 0.91, with the following trace:
----
Program received signal SIGSEGV, Segmentation fault.
0x008830de in GetDest(SPObject*, Shape**) ()
----

But not reproduced with 0.92.1 and lp:inkscape rev. 15616.
Probably fixed rev. 13700 (http://bazaar.launchpad.net/~inkscape.dev/inkscape/0.92.x/revision/13700#src/sp-flowregion.cpp).

[Mike Gallagher (mike-gallagher)]

Can you tell me what line of code is crashing 0.91? Out of several PC's that I have here, the only one that is affected is one that is used in the following system specs:
PC - Dell Optiplex 7020
I5 - 4590 CPU 3.30 GHz
Mem - 8GB
64 Bit Operating System
No touchscreen.
Graphics card: Intel HD Graphics 4600

[jazzynico (jazzynico)]

The patch from rev. 13700 was not designed to fix your bug specifically, but rather to refactor some old code. So it's a bit difficult to tell which line *exactly* fixed it.