Opening SVG causes Inkscape to stop responding

[Jeff M]

Opening the attached SVG causes Inkscape to stop responding. Sometimes you can manage to unlock the group or flip it before Inkscape stops.

Version: 0.91 (64bit)
also in Version: 0.46 ? (I found it here then upgraded)

=====
OS: Windows 7

[su_v (suv-lp)]

Please add information about OS/platform to the bug description, thank you.

[su_v (suv-lp)]

On 2015-08-14 16:13 (+0200), Jeff M wrote:
> Sometimes you can manage to unlock the group or flip it before
> Inkscape stops.

Please also provide more details how the file is opened in Inskcape 0.91, and what steps are then attempted to be applied.

The provided test case file (Inkscape SVG file which had been last edited/saved with Inkscape 0.44) does not contain any groups (or layers): all paths are directly in the top-level SVG root. There is no layer or group which could be unlocked.

[Jeff M (f-jeff)]

OS: Windows 7

Drag and Drop into new document OR double clicking to open, or opening the file causes Inkscape to loose it's way. I tried rebooting my computer, but still happens.

Selecting the object and unlocking the group appears to work, then Inkscape stops responding.

Having tested the file again, forcing Inkscape closed and restarting Inkscape, Inkscape now refuses to draw on new documents.

How does Inkscape handle memory? It is possible that the problem is isolated to my machine since I appear to have intermittent RAM problems.

[su_v (suv-lp)]

On 2015-08-14 17:11 (+0200), Jeff M wrote:
> OS: Windows 7

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

[su_v (suv-lp)]

Not reproduced based on the available information with Inkscape 0.91 r13725 on OS X 10.7.5: the file can be edited without issues, be it by opening it directly (no groups, all objects (5 paths) are directly in SVG root), or after having it imported into a new document (this will import the drawing as group into the current layer; ungrouping it and selecting/editing individual objects (paths) works as expected).

[Jeff M (f-jeff)]

64 bit

If Inkscape is using direct / raw memory access, then the problem is likely mine alone. Please close the bug report then.

Thanks