Closed Bug 1239889 Opened 9 years ago Closed 9 years ago

KeyframeEffectReadOnly constructor crashes when the target element does not have the parent?

Categories

(Core :: DOM: Animation, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla47
Tracking Status
firefox46 --- affected
firefox47 --- fixed

People

(Reporter: hiro, Assigned: birtles)

References

Details

Attachments

(2 files)

Below codes leads the crash. var div = document.createElement('div'); var effect = new KeyframeEffectReadOnly(div, { opacity: [0, 1] }); 0:04.34 #01: BuildAnimationPropertyListFromPropertyIndexedKeyframes (/home/ikezoe/mozilla-central/dom/animation/KeyframeEffect.cpp:1566) 0:04.34 #02: mozilla::dom::KeyframeEffectReadOnly::Constructor(mozilla::dom::GlobalObject const&, mozilla::dom::Element*, mozilla::dom::Optional<JS::Handle<JSObject*> > const&, mozilla::dom::UnrestrictedDoubleOrKeyframeEffectOptions const&, mozilla::ErrorResult&) (/home/ikezoe/mozilla-central/dom/animation/KeyframeEffect.cpp:1732) 0:04.40 #03: downcast<mozilla::dom::KeyframeEffectReadOnly> (/home/ikezoe/mozilla-central/obj-firefox/dist/include/mozilla/AlreadyAddRefed.h:138)
Attached patch Automation test for the crash (deleted) — Splinter Review
I did not paste the most important line. 0:02.12 Assertion failure: aTargetElement->GetCurrentDoc() (we should only be able to actively animate nodes that are in a document), at /home/ikezoe/mozilla-central/layout/style/StyleAnimationValue.cpp:2596
Blocks: 1245000
This is likely the cause for bug 1245735 so I think we need to fix this soon. I spoke to Cameron about what is going on and I think the basic problem is that we are computing values in the KeyframeEffectReadOnly constructor. We really should be storing specified values and only computing them when needed since the computed values will change if mTarget is changed or bound to a different part of the tree. It's probably too expensive to re-compute those every on every frame so we'd need to recompute them every time mTarget changed or BindToTree was called on it. That's a fair bit of work, however. So, what we can do as an interim step is simply throw if the target element does not have a current doc like we do if mTarget is null. We *could* just use the style context from the owner doc but that's going to be wrong in some cases.
Assignee: nobody → bbirtles
Status: NEW → ASSIGNED
Filed bug 1245748 for doing the work described in comment 3.
I was thinking of using attachment 8708153 [details] [diff] [review] as the test case and writing a more thoroughgoing test when we fix bug 1245748
Attachment #8715651 - Flags: review?(cam)
Attachment #8715651 - Flags: review?(cam) → review+
Comment on attachment 8708153 [details] [diff] [review] Automation test for the crash Hi Hiro, I hope you don't mind if I land this test along with the fix.
Attachment #8708153 - Flags: review+
Sure!
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla47
Depends on: 1252599
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: