Note: This documentation is applicable exclusively to North America. If your app is not being distributed in North America, please contact Partner_Mgmt@sky.uk.
The memory monitor tool is used to validate how much memory your X1 Application is using. Your X1 App must not exceed the memory cap of 190MB of RAM.
Example Use Cases
- Understand how close your application is to the device limit.
- Gain insight into performance issues with your application.
- Track when JavaScript garbage collection occurs.
- Monitor CPU usage of your application.
Accessing Memory Monitor
Memory Monitor overlay is enabled as part of the Remote Web Inspector and is available for web apps running on WPE browser. The overlay can be shown/hidden by pressing Key UP + Key DOWN + 3 + 6 + 8 on your remote, or pressing CTRL+Alt+S using a keyboard connected to your X1 Platform Development Device, when a WPE application is in the foreground.
Using Memory Monitor
This Memory Monitor shows the resource usage of web processes by the WPE application in the foreground. The following is a brief explanation of what each field in the overlay represents:
- CPU - CPU used by the application
- Memory - Memory usage (RSS - shared)
- External - external memory allocated by web core, usually just 0
- GC Heap - memory allocated by JS heap
- GC Owned - extra memory allocated by WebCore and owned by JSC heap (array buffers etc)
- Eden GC - time in seconds to next GC in Eden space (time is adjusted on allocations)
- Full GC - time in seconds to next full GC (time is adjusted on allocations)
- Graphics Memory - Percentage of graphics memory currently used by system. This is NOT the graphics memory usage by the foreground application, so to find the actual usage of the application, you need to collect the usage before or immediately after launching the app and check the usage for peak value during the application usage.