Open onuralpszr opened 2 years ago
kdynamicwallpaperbuilder spends most of the time encoding image data. At quick glance, libavif provides no realtime feedback. It needs more investigation, maybe I overlooked the relevant APIs.
What I'd like to understand is why kdynamicwallpaperbuilder is such a resource hog and takes way too long to finish. I'm running it on an i3-7020U with 12 GB of RAM and the process already took 85% of CPU according to System Monitor and 7.5GB of RAM. All I did was pick a heic image from a dynamic wallpaper website for Mac OS and it stays like this for what seems like forever. Gwenview says it's nine images of about 6000x6000 each. Is it expected to take too long for those images?
It would be nice to have a "Progress Indicator" so we can know how much is left or stuck. ,