684780 - ###!!! ABORT: unexpected path mismatch: 'startParams.mPath == endParams.mPath', file SVGMotionSMILType.cpp, line 465

Status: RESOLVED DUPLICATE of bug 1343357

(Core :: SVG, defect)

Description

[Daniel Holbert [:dholbert]]

Attachment: testcase 1 (Triggers fatal abort in debug builds)

STR: Load attached testcase in debug build

ACTUAL RESULTS: abort due to ABORT_IF_FALSE failure:
{
###!!! ABORT: unexpected path mismatch: 'startParams.mPath == endParams.mPath', file content/svg/content/src/SVGMotionSMILType.cpp, line 465
}

(Seems harmless in opt builds, though.)

Comment 1

[Daniel Holbert [:dholbert]]

Attachment: testcase 2 (Triggers fatal abort in debug builds)

This testcase adds a 'rotate' attribute to one of the two animations involved, which makes us trigger another ABORT_IF_FALSE one line earlier:
{
###!!! ABORT: unexpected angle mismatch: 'startSeg.mRotateType == endSeg.mRotateType && startSeg.mRotateAngle == endSeg.mRotateAngle', file content/svg/content/src/SVGMotionSMILType.cpp, line 463
}

Basically, these ABORT_IF_FALSEs are checking that the from-val & to-val that we're interpolating between came from the same <animateMotion> element.  In the attached testcases, however, that assumption is violated -- the 'to' animation uses the current state of the animation sandwich as its from-val, which ends up being a value generated by a different <animateMotion>.

Comment 2

[Daniel Holbert [:dholbert]]

(Despite this being ABORT_IF_FALSE, I'm pretty confident that this bug is non-scary -- it just means we end up animating along the wrong path or using the wrong rotation angle.)

Comment 3

[Daniel Holbert [:dholbert]]

I believe this will be addressed in bug 1343357.