04-15-2019, 02:42 AM
Klaus,
Sorry it's taken me so long to get back to you. I restored your library and loaded up MobileSheets and it's using 78.3 MB with 0% CPU, so I'm really not sure what's going on. Do you have a huge amount of music under your Windows 10 music folder? MobileSheets does scan all of that... I probably should change that to only scan after the connection to the companion is established. Having said that, I copied about 6 GB of files to the music folder, and while it did result in a small amount of cpu usage at startup, it then settled down and the memory is only at 82.8 MB.
From what I've read the runtime broker can be shared among multiple store applications or other things running in the background. Do you have other store applications running on your box? If you look at all processes while MobileSheets is closed, is the runtime broker still up? Looking at the "other fixes" section of https://www.ghacks.net/2017/04/06/what-i...-cpu-load/ it has a few suggestions that seem interesting.
Mike
Sorry it's taken me so long to get back to you. I restored your library and loaded up MobileSheets and it's using 78.3 MB with 0% CPU, so I'm really not sure what's going on. Do you have a huge amount of music under your Windows 10 music folder? MobileSheets does scan all of that... I probably should change that to only scan after the connection to the companion is established. Having said that, I copied about 6 GB of files to the music folder, and while it did result in a small amount of cpu usage at startup, it then settled down and the memory is only at 82.8 MB.
From what I've read the runtime broker can be shared among multiple store applications or other things running in the background. Do you have other store applications running on your box? If you look at all processes while MobileSheets is closed, is the runtime broker still up? Looking at the "other fixes" section of https://www.ghacks.net/2017/04/06/what-i...-cpu-load/ it has a few suggestions that seem interesting.
Mike