Snapshot fails in build - Encountered Invalid Memory Region signal

Unity Engine
1

Hi when i try to take an memory snapshot for an build (window and android) im encountering following error:

Editor.log

MemoryCapture: Header Serialization : 0 ms
MemoryCapture: Metadata Serialization : 0 ms
MemoryCapture: Capture flags Serialization : 0 ms
MemoryCapture: Managed Heaps : 329 ms
MemoryCapture: Managed Stacks : 0 ms
MemoryCapture: Managed Metadata : 102 ms
MemoryCapture: GC Handles : 0 ms
MemoryCapture: Native Types : 0 ms
MemoryCapture: Native Objects : 7 ms
MemoryCapture: Runtime Information Serialization : 0 ms
MemoryCapture: Native Allocation Header : 0 ms
MemoryCapture: Native Allocation Labels : 0 ms
MemoryCapture: Native Root References : 0 ms
Encountered Invalid Memory Region signal
(Filename: C:\buildslave\unity\build\Modules/Profiler/Runtime/MemorySnapshotProcess.cpp Line: 1340)

Any idea whats going on?

2

im using latest 2019 version and packagemanager 0.2.6preview

3

Heya! Looking into that right now, are the players also built with latest 2019.4?

Edit:
Tested on latest 19.4 and everything works as expected. Are you trying to snapshot older version builds?

4

Having the same issue here. Attempting to take a memory snapshot of a remote Linux player from a Windows machine, both 2019.4.8f1. Managed Objects capture fine but Native ones fail in the logs with

MemoryCapture: Header Serialization : 163 ms
MemoryCapture: Metadata Serialization : 0 ms
MemoryCapture: Capture flags Serialization : 0 ms
MemoryCapture: Managed Heaps : 4354 ms
MemoryCapture: Managed Stacks : 0 ms
MemoryCapture: Managed Metadata : 126 ms
MemoryCapture: GC Handles : 61 ms
MemoryCapture: Native Types : 0 ms
MemoryCapture: Native Objects : 2084 ms
MemoryCapture: Runtime Information Serialization : 0 ms
MemoryCapture: Native Allocation Header : 0 ms
MemoryCapture: Native Allocation Labels : 0 ms
MemoryCapture: Native Root References : 0 ms
Encountered Invalid Memory Region signal
(Filename: C:\buildslave\unity\build\Modules/Profiler/Runtime/MemorySnapshotProcess.cpp Line: 1301)

MemoryCapture: Failed processing of Native Memory Region
MemoryCapture: Failed processing of Native Allocation Footer
MemoryCapture took: 6788 ms

Additionally, the Memory Profiler UI gets stuck showing a progress bar that never goes away, giving the illusion it’s still doing something.

5

2019.4.8 got hit by a regression. Iirc the fix for that one landed on 2019.4.10, but in case that it wasn’t that, the higher the patch release version the more likely it’s fixed.

1 Like