Closed devmil closed 2 years ago
Mind telling your Windows version?
Mind telling your Windows version?
It is macOS 12.3.1 running on an M1 Pro (14 inch). It doesn't matter if I run the arm or x86 variant. The win32 package is only complaining during compilation.
Hello,
I am the maintainer of the macOS port of this library. No, this behavior is neither intended nor known.
I'll look into this issue and see whether I can reproduce it myself.
Alright. First of all, trying to run the example project in Flutter 3 produces the following error on my end:
Error: 'Size' is imported from both 'dart:ffi' and 'dart:ui'.
This error can be fixed by upgrading bitsdojo_window
from ^0.1.1+1
to ^0.1.2
, a version that, as of writing, came out 11 hours ago. Did you perform this upgrade yourself, or did it somehow compile fine on your end without this change?
That said, I was able to reproduce the issue. The performance profiler looks even worse on my end than on yours and the app hovers at around 15 - 20 % CPU usage on my M1 MacBook Air:
Unfortunately, I am currently unsure how to fix this issue. I am relying on high-level Swift functions to achieve the transparency effect, which makes it difficult to assess the performance impact of the library.
Sorry, I missed to mention that I'm using a locally patched version of bitsdojo_window. That's really sad. Any idea what might trigger Flutter to do this?
Not at the moment, though I did notice that this behavior doesn't change when the transparency effect is inactive (neither when the window is unfocused, nor when the effect is disabled entirely). Perhaps this has something to do with the view controller that is initialized in the MainFlutterWindow.swift
file, then?
I'll have to look deeper into this.
I tried some things and it seems that as soon as I remove the TitlebarSafeArea
Widget the problem seems to diappear.
I will dig deeper...
fixed now on master
Hi, When using flutter_acrylic I see a continuous frame creation and a CPU load of ~10% even if no rebuild happens. The moment I remove flutter_acrylic the issue is gone.
I can also reproduce this with the example app from this repository.
Is this intended / needed / known?
PS I had to do
flutter pub upgrade
in order to get rid of some problems in the win32 package in combination with Flutter 3