[UWP]资源泄漏与CoreApplication :: CreateNewView [英] [UWP] Resource leaks with CoreApplication::CreateNewView

查看:74
本文介绍了[UWP]资源泄漏与CoreApplication :: CreateNewView的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述


我正在开发一个使用CoreApplication :: CreateNewView()创建的多视图应用程序。我注意到在50次api调用之后,此API被阻止,应用程序被移动到"已暂停"状态。状态无限期。


我尝试了一个非常简单的应用程序,注意不要泄漏任何对象,这种行为可以重现。我知道用户一次不会打开50个窗口,但如果在整个应用程序生命周期中打开并且
关闭50个视图,也会发生这种情况,这很可能会发生。


我是否应采取任何特殊措施以使观点不计入50次观看限制?

解决方案

你好
iohanson ,


欢迎使用通用Windows应用论坛。


实际上您的问题超出了论坛范围,请打开a
支持机票  
以便我们在这种情况下更好地了解并帮助您。


祝你好运,


百里


Hi,

I'm working on a multi-view application created wih CoreApplication::CreateNewView(). I noticed that after 50 api calls, this API is blocked and the application is moved to a "Suspended" state indefinitely.

I tried with a very simple application, paying attention not to leak any object and this behavior can be reproduced. I know that users will not have 50 windows open at one time, but this also happens if during the entire application life cycle you open and close 50 views, which is likely to happen.

Is there any special action I should take in order to make views not to count against the 50 views limit?

解决方案

Hello iohanson,

Welcome to the universal windows app forum.

Actually your issue is beyond the forum scope, please open a support ticket  so that we can understand and help you better in this case.

Best regards,

Barry


这篇关于[UWP]资源泄漏与CoreApplication :: CreateNewView的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆