Power Profiler v3.5.4 - Error loading large *.ppk file(s)

When trying to load a stored PPK in the application an error occurs.

Environment:
Windows 10 Business
22H2
19045.2728
Windows Feature Experience Pack 120.2212.4190.0
Power Profiler v3.5.4
nRF Connect 4.0.1
32GB RAM



Log:

13:07:19.185
Using nrf-device-lib-js version: 0.6.5
13:07:19.186
Using nrf-device-lib version: 0.14.7
13:07:19.186
Using nrfjprog DLL version: 10.19.1
13:07:19.186
Using JLink version: JLink_V7.80c
13:07:36.595
Restoring state from D:\ppk-20221229T194459-data-logger.ppk
13:07:58.416
Error loading from D:\ppk-20221229T194459-data-logger.ppk

From my understanding of my colleagues, this issue does not exist when using the linux version in a virtual machine.
This was acceptable at the time we did run into this issue but isn't anymore.
Because of company policies I don't rule out that this is related to limitations set on my pc but because smaller (a few MB) PPK files do open without any issue I still want to know if this is an known\reported issue.

Environment
Parents
  • Hi

    This is a known issue first discovered a couple of months back in this ticket, and unfortunately we haven't been able to find a fix for Windows machines as of yet, so if you need to view these larger .ppk files you will need a Linux or MacOS machine for the time being. We recommend limiting the memory to < 1000MB when doing power profiling on Windows machines. You can see the estimated RAM required under the sampling parameters in the Power Profiler app when setting up a measurement scenario:

    As stated in the ticket I linked to, the fix should be documented in the changelog when we have a version fixing this ready.

    Best regards,

    Simon

Reply
  • Hi

    This is a known issue first discovered a couple of months back in this ticket, and unfortunately we haven't been able to find a fix for Windows machines as of yet, so if you need to view these larger .ppk files you will need a Linux or MacOS machine for the time being. We recommend limiting the memory to < 1000MB when doing power profiling on Windows machines. You can see the estimated RAM required under the sampling parameters in the Power Profiler app when setting up a measurement scenario:

    As stated in the ticket I linked to, the fix should be documented in the changelog when we have a version fixing this ready.

    Best regards,

    Simon

Children
No Data
Related