Under multiple engines, destroying the page will not trigger dispose #136885
Description
Is there an existing issue for this?
- I have searched the existing issues
- I have read the guide to filing a bug
Use case
Flutter (Channel stable, 3.13.1）
Under multiple engines, destroying the page will not trigger dispose
It can be reproduced in the official 'multiple_flutters' demo.
Proposal
I found that when using multiple engines, if the FlutterViewController is destroyed, it will directly destroy the engine and channel, and the dispose in the Flutter page will not be triggered. Is there any way to change this problem? Because if dispose is not triggered, we will have a lot of inconvenience.