When the desktop_multi_window plugin is used in combination with the window_manager plugin on MacOS, then resources are not freed, when closing a window. The reason for that is the FlutterWindow extension:
which overrides the windowWillClose and windowShouldClose members. However, the window_manager plugin does the same by extending the NSWindowDelegate protocol. Since extensions cannot replace existing implementations the FlutterWindow extension has no effect, so that the delegate?.onClose() function never gets called leaving the whole isolate responsible for the closed window im memory.
When the desktop_multi_window plugin is used in combination with the window_manager plugin on MacOS, then resources are not freed, when closing a window. The reason for that is the FlutterWindow extension:
which overrides the
windowWillClose
andwindowShouldClose
members. However, the window_manager plugin does the same by extending theNSWindowDelegate
protocol. Since extensions cannot replace existing implementations theFlutterWindow
extension has no effect, so that thedelegate?.onClose()
function never gets called leaving the whole isolate responsible for the closed window im memory.Version: