Repository navigation
[Problem/Bug]: Power Apps App and Microsoft Teams Desktop Client (WebView2) - Possible Memory Leak #5662
Description
What happened?
We have a Power Apps App that runs within a Microsoft Teams environment. When the App is access from within Teams, memory is gradually consumed by a WebView2 process (msedgewebview2.exe) until Teams' auditActiveAppsMemory function appears to remove the App from the Teams UI frame, returning the below error from within the Teams desktop client:
[MemoryError::APP_OUT_OF_MEMORY]
Slot name:MAIN
Session ID:xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx
2026-08-03T15:27:09.194Z
The App within Teams generally crashes within ~1-2 minutes of accessing it, and the App has been observed running under the "WebView2 Subframe" and "Renderer" WebView2 processes.
There are what appear to be two viable workarounds:
- Opening the linked Power Apps app as a tab in a new window from within the Teams desktop client; or
- Accessing it from Teams for the web (https://teams.microsoft.com/v2/).
Relevant logs from Teams desktop client:
2026-08-03T15:27:09.174Z Inf PlatformAppsManagementService: removeApp: Removing app xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx with frame UUID xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx
2026-08-03T15:27:09.143Z Inf PlatformAppsManagementService: auditActiveAppsMemory: Triggering high memory event for largest active app xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx
2026-08-03T15:30:32.513Z Inf CID[xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx] useShowServicesUnavailable: useShowServicesUnavailable::showServiceOutageBadge=false&servicesUnavailableIconClass=undefined&hasDismissed=false
2026-08-03T15:27:24.175Z Inf CID[xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx] AppCaching: PlatformCacheManagementService: remove app on timeout: [xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx, tab::xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx, /providers/Microsoft.PowerApps/apps/xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx]
2026-08-03T15:27:09.214Z Inf CID[xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx] useRegisterSearchListener: Successfully reset MetaOsAppSearchHandlerState in cache
2026-08-03T15:27:09.201Z Inf CID[xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx] AppCaching resolver: removeSharedPlatformCachedApps: cached app list updated, writing query
2026-08-03T15:27:09.190Z Inf CID[xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx] Core Rendering Layer, Phased Rendering Framework – main Slot, PreCache App Render Mode: PhaseStateMachine instance id: 15, correlationId: PreCache-main-xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx, currentPhase: COMPLETE, Disposing with incomplete signals in phase CRITICAL. Signals platform_app_container_rendered,platform_app_frame_rendered,platform_app_frame_content_rendered were not received
2026-08-03T15:27:09.189Z Inf CID[xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx] AppCaching: CacheableAppHostIframe: useUpdateFrameStyles hideFrame: setPersistedAppContentProps to false for cacheable-iframe:xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx
2026-08-03T15:27:09.189Z Inf CID[xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx] Core Layout Persistence, PersistedAppContentContextProvider: Remove persisted app content for id: cacheable-iframe:xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx
2026-08-03T15:27:09.189Z Inf CID[xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx] AppCaching: CacheableAppHostIframe: removePersistedAppContent cacheable-iframe:xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx
2026-08-03T15:27:09.189Z Inf CID[xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx] AppCaching: PlatformCacheManagementService: shouldTriggerUnload for non-existent App [xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx, tab::xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx, /providers/Microsoft.PowerApps/apps/xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx]
2026-08-03T15:27:09.188Z Inf CID[xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx] HostedWebContentWithMetaOSInner: This hosted component has unmounted; appSessionId: xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx, appLaunchId: xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx
2026-08-03T15:27:09.187Z Inf CID[xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx] useSubscribeAppDevicePermissionRequests: ContentsId xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx, appId xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx: Unsubscribing from device permission requests
2026-08-03T15:27:09.187Z Inf CID[xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx] AppCaching: DevicePermissionSubscription: run iframe disposer cleanup, appId xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx, appSessionId xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx, platformFrameUuid b47590ce-8f6d-44f8-ad06-745f4f874f1a
2026-08-03T15:27:09.179Z Inf CID[xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx] useTaskCleanupHook: Running registered cleanup tasks count:2
2026-08-03T15:27:09.179Z Inf CID[xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx] HostedWebContentEntry: This hosted component has unmounted; appSessionId: xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx
2026-08-03T15:27:09.178Z Inf CID[xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx] AppCaching: useUpdateActivityStatusOfCachedApp: Cleanup Phase: Cached app not found , appId : xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx
2026-08-03T15:27:09.174Z Inf CID[xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx] Core Layout Persistence, PersistedAppContentContextProvider: Removing persisted app content with id: cacheable-iframe:xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx
2026-08-03T15:27:09.174Z Inf CID[xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx] Core Layout Persistence, PersistedAppContentContextProvider: Remove persisted app content for id: cacheable-iframe:xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx
2026-08-03T15:27:09.174Z Inf CID[xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx] AppCaching: AppManagementCache: disposeItem: removePersistedAppContent xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx with elementId cacheable-iframe:xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx
2026-08-03T15:27:09.173Z Inf CID[xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx] AppCaching: PlatformCacheManagementService: handleUnloading for App: [xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx, tab::xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx, /providers/Microsoft.PowerApps/apps/xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx].
2026-08-03T15:27:09.173Z Inf CID[xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx] AppCaching: PlatformCacheManagementService: setAppState loaded, unloading: [xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx, tab::xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx, /providers/Microsoft.PowerApps/apps/xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx], appSessionId: xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx
2026-08-03T15:27:09.173Z Inf CID[xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx] AppCaching: PlatformCacheManagementService: shouldTriggerUnload for App returns: [xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx, tab::xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx, /providers/Microsoft.PowerApps/apps/xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx] true, appSessionId: xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx, app unmounting started.
2026-08-03T15:27:09.173Z Inf CID[xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx] AppCaching: PlatformCacheManagementService: dispose
2026-08-03T15:27:09.168Z Err CID[xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx] SlotErrorBoundary: slotName: main, componentStack:
at https://teams.public.onecdn.static.microsoft/teams-modular-packages/hashed-assets/async-entry-47ff400edb25f1e1.js:1276:226400
at https://teams.public.onecdn.static.microsoft/teams-modular-packages/hashed-assets/async-entry-47ff400edb25f1e1.js:1276:229046
at Uu (https://teams.public.onecdn.static.microsoft/teams-modular-packages/hashed-assets/async-entry-47ff400edb25f1e1.js:29:27364)
at https://te...
2026-08-03T15:27:09.143Z Inf CID[xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx] AppCaching: PlatformCacheManagementService: Triggering high memory event for active app: xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx
Importance
Important. My app's user experience is significantly compromised.
Runtime Channel
Stable release (WebView2 Runtime)
Runtime Version
150.0.4078.105
SDK Version
No response
Framework
Other
Operating System
Windows 11
OS Version
25H2
Repro steps
- Open Microsoft Teams desktop client
- Navigate to Team channel containing tab link to Power Apps app
- Access App from tab link
- Wait approximately ~1-2 minutes
- Error is displayed within the Teams desktop client UI: [MemoryError::APP_OUT_OF_MEMORY]
Repros in Edge Browser
No, issue does not reproduce in the corresponding Edge version
Regression
No, this never worked
Last working version (if regression)
No response
Activity
muira commentedon Aug 9, 2026
Same here! PowerApps for Teams app with dataverse.. my app is not hugely complex, not data heavy, delegation issues avoided or managed, there's no endless collecting, the code is clean.. good to hear it's not just me, let me know if there's anything you'd like me to check
cajunclay commentedon Aug 13, 2026
I'm still having the same problem! Haven't found a fix for it, unfortunately.
cajunclay commentedon Aug 20, 2026
muira , terminating Teams, deleting the the EBWebView cache folder under: AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams, and relaunching Teams appeared to fix the issue (at the moment).
muira commentedon Aug 20, 2026
Hi clay, I'll try that thank you.. fyi a colleague who is on a pilot of the latest version of Teams has never seen the issue, which may be a clue also.. I'll see if I can get version numbers and post them here
cajunclay commentedon Sep 17, 2026
Hey, Muira! I take it back - the issue has come back, even after deleting that cache folder :/
simonhess93 commentedon Sep 22, 2026
Many of our users have noticed the same behaviour with different Power Apps in Teams. I also haven't found a fix for it yet.
alikanta333 commentedon Oct 15, 2026
Same issue here. Did anyone try these methods? Did any of them helped?
1. Increase or Restore Windows Virtual Memory (Page File)
WebView2 can trigger an "out of memory" state even if your computer has plenty of free, physical RAM. This happens if the Windows Virtual Memory page file is disabled, too small, or corrupted.
1. Press Win + R, type sysdm.cpl, and press Enter.
2. Go to the Advanced tab, and click Settings under the Performance section.
3. Go to the Advanced tab in the new window, and click Change under Virtual memory.
4. Look at the checkbox for "Automatically manage paging file size for all drives":
• If it is unchecked: Check the box to let Windows dynamically handle memory allocation.
• If it is checked but failing: Uncheck it, select Custom size, and allocate a larger explicit size. Rule of thumb: Set the Initial size to 1.5 times your physical RAM, and Maximum size to 3 times your physical RAM (in megabytes).
5. Click Set, then OK, and restart your PC.
2. Exclude WebView2 from Local Antivirus / DLP Scans
Security tools often lock down background subprocesses. In corporate environments, aggressive endpoint antivirus or Data Loss Prevention (DLP) agents continuously scan msedgewebview2.exe subframes as they process web scripts. This monitoring loops memory data until it leaks into a crash.
• The Fix: Work with your IT Administrator to add an exclusion rule in your security software for the Microsoft Edge WebView2 directory and the Teams desktop client (ms-teams.exe).
3. Check for 32-bit Architecture Bottlenecks
Ensure your organization hasn't accidentally deployed a 32-bit version of Teams or its underlying tools onto your machine. 32-bit processes are hard-capped at a maximum of 4GB of addressable memory space. If a WebView2 subframe attempts to cross that boundary, it will immediately crash, regardless of how simple the Power App is.
• Check Settings > About in Teams to confirm you are running the x64 (64-bit) version.
4. Toggle the Teams Hardware Acceleration
Corrupted graphics drivers can cause WebView2 rendering subframes to leak memory.
1. Open Teams Settings.
2. Navigate to the General or Advanced tab.
3. Toggle the option for Hardware Acceleration (if available in your specific tenant build). Turning it off forces the app to rely on software rendering, which can temporarily bypass a buggy device driver leak.
Scoff123 commentedon Oct 16, 2026
We're seeing the same issue and have reproduced it with a blank canvas app (a single text label, no data sources, no interaction), so it doesn't appear to depend on app content.
Environment:
To reproduce:
WebView2 Subframe: https://powerapps.com/in Task ManagerTeams main window measurements:
APP_OUT_OF_MEMORYLogs at the moment of removal, the same as the original report:
PlatformAppsManagementService: auditActiveAppsMemory: Triggering high memory event for largest active appfollowed within ~10 ms by
SlotErrorBoundary: slotName: main. No other custom apps were open in Teams.Observations:
MAINslot, which would explain why the pop-out works as a workaround.EvilAntEater commentedon Oct 16, 2026
Same results as Scott (@Scoff123), can replicate with blank canvas..
CalebTHBEV commentedon Oct 19, 2026
I have the exact same issues. Currently asking the users to open in the browser or use the pop out window.
Have tried everything to reduce memory usage within apps and nothing has worked.
StevenW-N3i commentedon Oct 21, 2026
We are experiencing the same issue across Windows and MacOS devices. Clearing Teams cache is providing some temporary relief for end users but the issue does keep returning.