Popovers
Popovers copied to clipboard
After replacing the version, the cpu usage soared,
!上传截屏2022-05-04 00.13.12.png... The source of the problem to be detected
使用最新1.3.2版本
Bound preference ElementPreferenceKey tried to update multiple times per frame. Bound preference ContentFrameReaderPreferenceKey tried to update multiple times per frame. Bound preference ContentFrameReaderPreferenceKey tried to update multiple times per frame. Bound preference ContentFrameReaderPreferenceKey tried to update multiple times per frame. Bound preference ContentFrameReaderPreferenceKey tried to update multiple times per frame. Bound preference ContentFrameReaderPreferenceKey tried to update multiple times per frame. Bound preference ContentFrameReaderPreferenceKey tried to update multiple times per frame. Bound preference ContentFrameReaderPreferenceKey tried to update multiple times per frame. Bound preference ContentFrameReaderPreferenceKey tried to update multiple times per frame. Bound preference ContentFrameReaderPreferenceKey tried to update multiple times per frame. Bound preference ContentFrameReaderPreferenceKey tried to update multiple times per frame. Bound preference ContentFrameReaderPreferenceKey tried to update multiple times per frame. Bound preference ContentFrameReaderPreferenceKey tried to update multiple times per frame.
I can't open the png, could you upload it again?
After closing the popover, the window still occupies the cpu
My interaction is in the page, some of them occupy more than 90% of the CPU, and the page is seriously stuck.
Huh. Is your app running on iOS? Try making a minimal reproducible example so I can reproduce
https://user-images.githubusercontent.com/74945717/167072910-ce0e72df-f9cb-4c8a-8211-9852d9a89a8a.MP4
That looks really weird. So it was working fine back in v1.3.1, but broke in v1.3.2? I didn't change the code much. The problem is probably here though: .onValueChange(of: transaction?.animation) { _, _ in
.
I'll take a look next week (got a bunch of exams right now...) but feel free to investigate or make a PR yourself if you want.
Development is tight, I first return to the system components, there is time to study the reasons
The height of the encapsulated component with uikit's UItextKit creates a refresh conflict in LazyVStask's container, causing rendering to bounce