Skip to content

Commit fbe779c

Browse files
committed
Metadata for profiling article
1 parent 8f70c1e commit fbe779c

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/profiling/troubleshoot-profiler-errors.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Troubleshoot profiling errors
33
description: Troubleshoot profiling errors, including no data in filters, slow results, and source information unavailable, and follow error message guidance to fix issues.
4-
ms.date: 06/28/2023
4+
ms.date: 08/19/2025
55
ms.topic: how-to
66
author: mikejo5000
77
ms.author: mikejo
@@ -74,7 +74,7 @@ After a long memory profiling session, any attempt to analyze the result is met
7474
There was a mismatch between the snapshot information captured by the memory tool and that of the collection agent. This result means that the memory tool wasn't able to find the heap state file for a native snapshot. Or, this result the memory tool couldn't match the GC start time of the snapshot to the one registered in the *diagsession* file to retrieve the GCStats.
7575

7676
**How to fix**
77-
This issue was due to a bug in the tool that was fixed in 17.3. Upgrading to a later version should solve the issue. If the issue is still persistent after upgrading, create a feedback ticket and attach to the ticket:
77+
This issue was due to a bug in the tool that was fixed in Visual Studio 2022 version 17.3. Upgrading to a later version should solve the issue. If the issue is still persistent after upgrading, create a feedback ticket and attach to the ticket:
7878

7979
- The *diagsession* file
8080
- A minidump of Visual Studio

0 commit comments

Comments
 (0)