View Issue Details

IDProjectCategoryView StatusLast Update
0003383NoesisGUIStudiopublic2024-06-13 16:14
Reporterdstewart Assigned Todfranjic  
PrioritynormalSeveritycrash 
Status resolvedResolutionfixed 
Product VersionStudio_Alpha 
Target VersionStudio_Alpha 
Summary0003383: Studio Crashes During Certain Anchor Point Repositionings
Description

Manipulating SVG Paths via adjusting the position of their anchor points, can cause Studio to crash.

In the attached video, you will notice that it took quite a bit of fiddling around with the shapes to get it to crash, but I have had this occur with as little as two anchor point repositionings within a shape.

Dump and Video Attached.

Steps To Reproduce

Repro Steps:

(Note that you will need an SVG asset available to complete the steps below. For the purpose of reproducing this crash, a slightly more complex SVG shape is better)

1) Create Page
2) Right-Click on the Page's Root Grid, and from the Context Menu, select Edit-->Import SVG.
3) Select an SVG, which will import it to the Page.
4) Navigate to the Animations Panel and create a new Storyboard. Upon the creation, the Timeline will appear, and you will be entered into Storyboard 'Edit' mode.
5) Select the Path Selection (Shortcut [A] ), and click on any anchor point in the SVG Path.
6) Click and Drag the anchor point in any direction.

Observe how the Anchor point has successfully been moved.

7) Click and Drag further anchor points in all sorts of positions, including some outward away from the shape, and some inward 'inside' of the shape (the 'inward' repositioning appear to be the most reliable way to crash)

Observe Studio crashing.

Expected Results: Multiple anchor points can have their positions changed in a Storyboard without crashing the application.

Attached Files
20240611_081744.dmp (102,070 bytes)
PlatformAny

Activities

dfranjic

dfranjic

2024-06-13 16:14

developer   ~0009703

This was happening when animating first point of a figure. Studio expected the animated position to be stored in a <LineSegment/> itself, but it's rather stored in the parent <PathFigure/> node, causing a mix up and a crash. It should be working now.

Issue History

Date Modified Username Field Change
2024-06-11 14:24 dstewart New Issue
2024-06-11 14:24 dstewart File Added: 20240611_081744.dmp
2024-06-11 14:24 dstewart File Added: PathManipulationCrash.mp4
2024-06-11 14:39 dfranjic Assigned To => dfranjic
2024-06-11 14:39 dfranjic Status new => assigned
2024-06-12 10:55 jsantos Target Version => Studio_Alpha
2024-06-13 16:14 dfranjic Status assigned => resolved
2024-06-13 16:14 dfranjic Resolution open => fixed
2024-06-13 16:14 dfranjic Note Added: 0009703