|
|
DescriptionImplicit prefinalizer registration.
Switch to implicit registration of prefinalizers along with removing
the ability to dynamically unregister a prefinalizer; the latter
being an unused feature.
The requirement to manually register a prefinalizer has proven to be
a chore and a source of bugs. Case in point: HTMLCanvasElement
currently declares a prefinalizer, but doesn't register it. Simplify
the programming model by automatically registering prefinalizers.
R=haraken
BUG=673645
Committed: https://crrev.com/bc86f5fb6fa58808c4d7937b6279e89d977b6b69
Cr-Commit-Position: refs/heads/master@{#438110}
Patch Set 1 #Patch Set 2 : fix HTMLCanvasElement prefinalizer #Patch Set 3 : recast registration class #Patch Set 4 : recast registration class #
Messages
Total messages: 37 (25 generated)
The CQ bit was checked by sigbjornf@opera.com to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: chromeos_daisy_chromium_compile_only_ng on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/chromeos_daisy_...)
Description was changed from ========== Implicit prefinalizer registration. Switch to implicit registration of prefinalizers along with removing the ability to dynamically unregister a prefinalizer. It has not proven to have uses. R= BUG= ========== to ========== Implicit prefinalizer registration. Switch to implicit registration of prefinalizers along with removing the ability to dynamically unregister a prefinalizer; the latter being an unused feature. The requirement to manually register a prefinalizer has proven to be a chore and a source of bugs. Case in point: HTMLCanvasElement currently declares a prefinalizer, but doesn't register it. Simplify the programming model by automatically registering prefinalizers. R= BUG= ==========
The CQ bit was checked by sigbjornf@opera.com to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was checked by sigbjornf@opera.com to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was checked by sigbjornf@opera.com to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: linux_android_rel_ng on master.tryserver.chromium.android (JOB_FAILED, https://build.chromium.org/p/tryserver.chromium.android/builders/linux_androi...)
sigbjornf@opera.com changed reviewers: + junov@chromium.org, kbr@chromium.org, oilpan-reviews@chromium.org
please take a look. The prefinalizer for HTMLCanvasElement is enabled here. i.e., r399587 wasn't effective. Which sort of motivates this change, we're taxing developers unnecessarily by having to remember this manual registration step. ( I'd be happy to split out the canvas change and land a (short-lived) registerPreFinalizer() call in its ctor first, if considered preferable. )
haraken@chromium.org changed reviewers: + haraken@chromium.org
LGTM
Description was changed from ========== Implicit prefinalizer registration. Switch to implicit registration of prefinalizers along with removing the ability to dynamically unregister a prefinalizer; the latter being an unused feature. The requirement to manually register a prefinalizer has proven to be a chore and a source of bugs. Case in point: HTMLCanvasElement currently declares a prefinalizer, but doesn't register it. Simplify the programming model by automatically registering prefinalizers. R= BUG= ========== to ========== Implicit prefinalizer registration. Switch to implicit registration of prefinalizers along with removing the ability to dynamically unregister a prefinalizer; the latter being an unused feature. The requirement to manually register a prefinalizer has proven to be a chore and a source of bugs. Case in point: HTMLCanvasElement currently declares a prefinalizer, but doesn't register it. Simplify the programming model by automatically registering prefinalizers. R=haraken BUG= ==========
The CQ bit was checked by sigbjornf@opera.com
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by sigbjornf@opera.com
Out of the 40+ classes that use prefinalizers, Animation is an outlier. It conditionally registers its prefinalizer at run-time. I need to determine how (and if) to handle that instance with this model.
lgtm
On 2016/12/12 07:37:41, sof wrote: > Out of the 40+ classes that use prefinalizers, Animation is an outlier. It > conditionally registers its prefinalizer at run-time. > > I need to determine how (and if) to handle that instance with this model. Will land https://codereview.chromium.org/2570503002/ first, so that we don't register more prefinalizers than necessary.
The CQ bit was checked by sigbjornf@opera.com
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: linux_chromium_chromeos_ozone_rel_ng on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...) linux_chromium_rel_ng on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
Looks fine. I would suggest you file a bug about this and reference it from both of these CLs so that in case they provoke flaky crashes there's a central place to track them.
Description was changed from ========== Implicit prefinalizer registration. Switch to implicit registration of prefinalizers along with removing the ability to dynamically unregister a prefinalizer; the latter being an unused feature. The requirement to manually register a prefinalizer has proven to be a chore and a source of bugs. Case in point: HTMLCanvasElement currently declares a prefinalizer, but doesn't register it. Simplify the programming model by automatically registering prefinalizers. R=haraken BUG= ========== to ========== Implicit prefinalizer registration. Switch to implicit registration of prefinalizers along with removing the ability to dynamically unregister a prefinalizer; the latter being an unused feature. The requirement to manually register a prefinalizer has proven to be a chore and a source of bugs. Case in point: HTMLCanvasElement currently declares a prefinalizer, but doesn't register it. Simplify the programming model by automatically registering prefinalizers. R=haraken BUG=673645 ==========
The CQ bit was checked by sigbjornf@opera.com
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
CQ is committing da patch. Bot data: {"patchset_id": 60001, "attempt_start_ts": 1481610726465510, "parent_rev": "2d7abb78d11d16d614265216e8bab6b3fde28672", "commit_rev": "41de4dc7a580071571d90a9e3524f2e4968ac436"}
Message was sent while issue was closed.
Description was changed from ========== Implicit prefinalizer registration. Switch to implicit registration of prefinalizers along with removing the ability to dynamically unregister a prefinalizer; the latter being an unused feature. The requirement to manually register a prefinalizer has proven to be a chore and a source of bugs. Case in point: HTMLCanvasElement currently declares a prefinalizer, but doesn't register it. Simplify the programming model by automatically registering prefinalizers. R=haraken BUG=673645 ========== to ========== Implicit prefinalizer registration. Switch to implicit registration of prefinalizers along with removing the ability to dynamically unregister a prefinalizer; the latter being an unused feature. The requirement to manually register a prefinalizer has proven to be a chore and a source of bugs. Case in point: HTMLCanvasElement currently declares a prefinalizer, but doesn't register it. Simplify the programming model by automatically registering prefinalizers. R=haraken BUG=673645 Review-Url: https://codereview.chromium.org/2565983002 ==========
Message was sent while issue was closed.
Committed patchset #4 (id:60001)
Message was sent while issue was closed.
Description was changed from ========== Implicit prefinalizer registration. Switch to implicit registration of prefinalizers along with removing the ability to dynamically unregister a prefinalizer; the latter being an unused feature. The requirement to manually register a prefinalizer has proven to be a chore and a source of bugs. Case in point: HTMLCanvasElement currently declares a prefinalizer, but doesn't register it. Simplify the programming model by automatically registering prefinalizers. R=haraken BUG=673645 Review-Url: https://codereview.chromium.org/2565983002 ========== to ========== Implicit prefinalizer registration. Switch to implicit registration of prefinalizers along with removing the ability to dynamically unregister a prefinalizer; the latter being an unused feature. The requirement to manually register a prefinalizer has proven to be a chore and a source of bugs. Case in point: HTMLCanvasElement currently declares a prefinalizer, but doesn't register it. Simplify the programming model by automatically registering prefinalizers. R=haraken BUG=673645 Committed: https://crrev.com/bc86f5fb6fa58808c4d7937b6279e89d977b6b69 Cr-Commit-Position: refs/heads/master@{#438110} ==========
Message was sent while issue was closed.
Patchset 4 (id:??) landed as https://crrev.com/bc86f5fb6fa58808c4d7937b6279e89d977b6b69 Cr-Commit-Position: refs/heads/master@{#438110} |