[roll] Roll fuchsia [flutter] Fix View lifetime & raciness

FuchsiaViewsService.createView() should only ever be called once during
a platform view's lifetime. Since it was gated on the async
"view connected" event it could easily be called multiple times,
and in a racy way.

Similarly, the FuchsiaViewsService.destroy() should only ever be called
once during a platform view's lifetime.

connect/disconnect events should be bracketed by the create() and
destroy() calls.  A connect or disconnect event can only occur once in a
view's lifetime.  Once a view is disconnected, nothing can be done with
it other than relasing the resources with dispose().

This CL fixes these lifetime bugs so a platform view moves through a
well-defined lifetime of:
create->connected->update->disconnected->destroyed

Test: fx test --host fuchsia_scenic_flutter_unittests
Original-Bug: b/195794362
Original-Bug: 82998

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/574521
Original-Revision: 5353335d972f891c4eada4b61b30fa6bc4e29e19
GitOrigin-RevId: 580eb08c129779f4263a58be6a391d2946a2840e
Change-Id: I8045ba7eca56c3ee93765fffdae589420e3988b4
1 file changed
tree: c15a7a4d0a16ff876869f2d48b083084bb159609
  1. garnet/
  2. infra/
  3. peridot/
  4. third_party/
  5. topaz/
  6. zircon/
  7. firmware
  8. flower
  9. jiri.lock
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. test_durations
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.

Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance via the IRC channel #fuchsia on Freenode.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.