Skip to content

Commit 93533d2

Browse files
authored
Update webview-reset.md
1 parent bde48e6 commit 93533d2

1 file changed

Lines changed: 4 additions & 4 deletions

File tree

support/dynamics-365/field-service/mobile-app/webview-reset.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Helps resolve WebView reset issues in the Dynamics 365 Field Servic
44
author: JonBaker007
55
ms.author: jobaker
66
ms.reviewer: puneet-singh1
7-
ms.date: 07/09/2025
7+
ms.date: 07/10/2025
88
ms.custom: sap:Mobile Application\Application is throwing errors
99
---
1010
# Troubleshoot WebView reset in Dynamics 365 Field Service mobile app
@@ -13,13 +13,13 @@ This article helps you troubleshoot and resolve issues in the [Dynamics 365 Fiel
1313

1414
## What is a WebView reset?
1515

16-
A WebView reset in the Dynamics 365 Field Service mobile app typically indicates that the app module is consuming too much memory. This is often triggered by activities that cause memory pressure on the WebView process. [Model-driven applications in Power Apps](/power-apps/maker/model-driven-apps/model-driven-app-overview), such as Dynamics 365 Field Service, run as web applications inside a WebView on the mobile client. As a result, they're subject to the memory management policies of the mobile operating system.
16+
A WebView reset in the Dynamics 365 Field Service mobile app typically indicates that the app module consumes too much memory. It's often triggered by activities that cause memory pressure on the WebView process. [Model-driven applications in Power Apps](/power-apps/maker/model-driven-apps/model-driven-app-overview), such as Dynamics 365 Field Service, run as web applications inside a WebView on the mobile client. As a result, they're subject to the memory management policies of the mobile operating system.
1717

1818
## Root cause
1919

2020
A WebView reset occurs when the mobile operating system terminates an application process that exceeds its memory limits. The threshold for "too much memory" varies by device and operating system, so the issue might not always be reproducible.
2121

22-
- **iOS:** The WebView reset error occurs only on iOS because WebViews run in separate processes that can be terminated independently from the main app. If the WebView process exceeds the operating system memory threshold, it's terminated. The app detects this, restarts the WebView, and displays a reset message to the user.
22+
- **iOS:** The WebView reset error occurs only on iOS because WebViews run in separate processes that can be terminated independently from the main app. If the WebView process exceeds the operating system memory threshold, it's terminated. The app detects this issue, restarts the WebView, and displays a reset message to the user.
2323
- **Android:** The WebView runs within the main application process. If memory limits are exceeded, the entire app process is terminated, resulting in a crash.
2424
- **Desktop browsers:** WebView resets don't occur, but memory pressure can still be investigated using browser tools.
2525

@@ -41,7 +41,7 @@ There are two main causes of memory pressure:
4141

4242
2. Memory leaks
4343

44-
A memory leak occurs when memory allocated within the WebView process isn't released because of lingering references, such as event listeners or objects that aren't properly cleaned up. This prevents the garbage collector from reclaiming the memory, causing memory usage to gradually increase over time. For example, adding event listeners to the window object in JavaScript without removing them when navigating away can lead to leaks. If WebView resets occur randomly and aren't tied to a specific action, it's likely due to a memory leak from previous activities.
44+
A memory leak occurs when memory allocated within the WebView process isn't released because of lingering references, such as event listeners or objects that aren't properly cleaned up. This issue prevents the garbage collector from reclaiming the memory, causing memory usage to gradually increase over time. For example, adding event listeners to the window object in JavaScript without removing them when navigating away can lead to leaks. If WebView resets occur randomly and aren't tied to a specific action, it's likely due to a memory leak from previous activities.
4545

4646
## Troubleshooting memory pressure
4747

0 commit comments

Comments
 (0)