Make Dart VM aware of growing size/weight of Canvas

[dnfield]

For example, when we draw an image to a canvas, we should inform the VM that the canvas' allocation size is now higher to include the image.

We'll be able to do this once https://dart-review.googlesource.com/c/sdk/+/149245 lands

/cc @chinmaygarde @liyuqian @rmacnak-google

[chinmaygarde]

Does the framework hold references to Canvases directly very often? My expectation was that pictures were the long lived heavyweight objects.

[dnfield]

No, I think we can lower the priority on this until we have a user who needs it or some convincing evidence that it's needed.

[dnfield]

Now that we properly dispose Canvas/Picture objects this is not necessary.

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.