Memory Profiler 1.1.0-pre.1 Released

Unity Engine
,
1

Good day everyone,

We have released version 1.1.0-pre.1 of the Memory Profiler package. It contains bug fixes and performance improvements for issues reported since the 1.1.0-exp.1 release . See below for details. For all changes since the 1.0 release, please check 1.1.0-exp.1 forum post .

Changes
Added

  • Added metadata support for AudioClip and Shader objects.
  • Added thumbnailing for screenshots to improve startup speed.

Fixed

  • Fixed an empty MonoBehaviour entry displayed in the Unity Objects table when ‘Show Potential Duplicates’ was checked and there are no potential duplicate MonoBehaviours.
  • Fixed Summary view tracking of Graphics memory on Switch.
  • Fixed the Summary breakdown bar’s total label overlapping with its legend when using small window sizes.
  • Fixed not showing negative values when comparing snapshots in Summary View.
  • Fixed an ArgumentNullException for a parameter named e in MemoryBreakdownLegendViewController.GatherColumnReferences.
  • Fixed Selection Details foldouts so that they retain their expansion status for the duration of an Editor session and do not change on every selection change.
  • Fixed screenshots remained after deleting snapshots.
  • Fixed situations where the highlighted element in tables did not reflect the displayed selection but could not be clicked to show its details in the selection, particularly when the selected row item would change due to search filtering the table, switching back to a previously visited view.
  • Fixed leaks of native UnsafeUtility.Malloc(Persistent) allocations that occurred when the Editor recompiled code while a snapshot was open.
  • Fixed leaks of Persistent NativeArray allocations via the Snapshot FileReader occurring with every (attempted) opening of a snapshot.
  • Fixed Unity Objects View was not showing graphics resources for snapshots made with Unity 2022.1 and older.
  • Added a tooltip for graphics items in All of Memory Table in “Resident” and “Allocated and Resident” views for a better explanation of why some elements are grayed out
  • Removed not-actionable console warning for iOS captures about reported overlapping Native Objects allocations
  • Fixed error if you try to open a snapshot while capturing
  • Fixed error reported if you try to change table view mode with dropdown while the view is still loading
  • Fixed snapshot renaming issues in situations when a warning or error dialog is shown

Changed

  • We marked IComparableItemData deprecated as it was accidentally exposed as public.
2 Likes
2

1.1.0-pre.1 does not work with WebGL. It does not show Unity objects.1.0.0 on WebGL does not have this issue.

3

Hey,
To clarify: the same snapshot, loaded into version 1.0.0 of the package, shows these objects, but loaded into 1.1.0-pre.1 does not show these?
Could you please use your Editor’s menu option Help > Report A Bug to file a bug report for this? Ideally with the project attached, though if that’s not possible, at least with such a snapshot attached. If there is no project attached, please also make sure to post the Issue ID (just the “IN-XXXX” number, not the link) into this thread, so that I can look at it and confirm if no project is needed? (otherwise our QA might reject it for lacking a repro project before it reaches our team).

4

It does not matter which version captured the snapshot. They open fine with 1.0.0, but fail to open correctly with a pre-release version. Attached screenshot.
9174239--1277363--upload_2023-7-27_2-19-44.png

Reported a bug. https://unity3d.atlassian.net/servicedesk/customer/portal/2/IN-49247

1 Like
5

Thank you for the bug report!
A fix for this issue will ship with the next version of the package.

6

I apologize if this has been addressed elsewhere, I’m trying out the 1.1.0-pre.1 package for the first time today:

I’m seeing the error message “Detailed breakdown of resident allocations is not available. This snapshot was taken with a Unity version 2021.2 or older*.*” when hovering over the grayed-out combobox at the top of the Unity Objects and All Of Memory tabs. I’m seeing this error in the Unity 2023.1.5 editor for captures taken from a iOS device using either the 2023.1.5 or 2021.3.17 editor. Is this a supported configuration, or am I missing a requirement?

Thanks!

7

Yes, that’s a mistake that was already fixed for the next update. It should say 2022.2/3 or older or rather what it was changed to now, as a positive statement, that it is available from Unity versions 2023.1 or newer, 2023.1.0a10+ to be precise.

1 Like