Insufficient memory to continue the execution of the program when trying to initialize array of InkCanvas in UWP

Question

Here is my code:

    public sealed partial class MainPage : Page
{
    InkCanvas[] arrInkCanvas = null;
    public MainPage()
    {
        this.InitializeComponent();

        int i = 0;

        arrInkCanvas = new InkCanvas[1000];
        try
        {
            for (i = 0; i < 1000; i++)
            {                    
                arrInkCanvas[i] = new InkCanvas();
            }
        }
        catch (Exception ex)
        {

        }
    }
}

When i run this code in WPF app there's no problem , but in UWP it throws exception : "Insufficient memory to continue the execution of the program."

Is it bugs or something can anyone tells me ?

Thanks.

I'd say the problem is pretty clear: trying to create 1000 new `InkCanvas` objects goes beyond the device's memory. — Camilo Terevinto, Dec 13 '15 at 16:38
Im running this app on my computer, exception break when i = 128 and the memory consuming was 50MB, i dont think the problem was device's memory. — meobeo173, Dec 13 '15 at 16:44
What's the device's memory? I imagine you are using a virtual device with 512mb, maybe that's the issue. Researching... — Camilo Terevinto, Dec 13 '15 at 16:46
See [MemoryManager](https://msdn.microsoft.com/en-us/library/windows.system.memorymanager.aspx) — Camilo Terevinto, Dec 13 '15 at 16:52
Im running on local machine, and there's no problem when loading bunch of images with 1GB memory consumed. — meobeo173, Dec 13 '15 at 16:53
Over 1GB is not possible since the UWP blocks you before 1GB. — Camilo Terevinto, Dec 13 '15 at 16:57

score 2 · Answer 1 · answered Dec 14 '15 at 06:56

Windows OS will balance the memory located to the application based on RAM and OS configuration. You can check your app's memory configuration by MemoryManager (just as cFrozenDeath said) in following way:

 public MainPage()
 {
     this.InitializeComponent();

     var AppUsageLevel = MemoryManager.AppMemoryUsageLevel;
     var AppMemoryLimit = MemoryManager.AppMemoryUsageLimit;
  }

From my test, your app does run out of memory. You can do a simple test: In the for loop each time you new InkCanvas(), you can call MemoryManager.AppMemoryUsage and compare it with the MemoryManager.AppMemoryUsageLimit.

Could you let me know if you have any specific reason for creating UIElment in such a way? Win10 1.586 does provide a new API, TrySetAppMemoryUsageLimit, to set the app's memory limitation. However, based on internal discussion, this API only works for very limited scenario right now, such as VOIP application on mobile device. And the sample code and document for this API are not quite ready.

score 0 · Answer 2 · edited Aug 23 '16 at 12:38

Looking into it, there is another post which looks similar, which suggests the limit might be at 128... which could be a limitation "by design"

If that is consistent - I have not tried it - why not creating a InkCanvas pool and reusing the InkCanvas once they are not in use? Unless you need them concurrently... Also that would add speed as you would avoid recreating the inkcanvas and just reuse them.

So far, the code could remain consistent and you can enlarge the pool when the issue/limitation is fixed..

Insufficient memory to continue the execution of the program when trying to initialize array of InkCanvas in UWP

2 Answers2

Linked