Reproduction steps:

1. Open the attached project “IN-88602”
2. Navigate to File → Build Settings…
3. Select WebGL Platform
4. Enable “Development Build” option
5. Build the Player (not Build&Run)
7. Navigate to the project folder using Finder for macOS/File Explorer for Windows
8. Open the build folder in Terminal for macOS/cmd for Windows by right clicking on the build folder and selecting the option “New Terminal at Folder“ for MacOS or “Open in Terminal“ for Windows
9. In the Terminal execute command “ipconfig getifaddr en0“ to get your IP if wired connection is used, or “ipconfig getifaddr en1” to get your local IP Address if connected through a Wifi. For Windows, in the CMD execute command “ipconfig“, search for IPV4 field to find your local IP Address.
10. In the Terminal/cmd execute following command: “python3 -m http.server portnumber“, “portnumber“ can be any 4-5 long numeric value. For example 60281 (ensure that Python is installed)
11. Open the Player in the browser by typing “yourIP:60281” in the Address bar
12. Open the Memory Profiler in Editor by navigating Window → Analysis → Memory Profiler
13. Click on the “Editor“ dropdown, select option <Enter IP>
14. Enter “yourIP:60281” in the field, click “Connect“
15. Click on the “Capture new Snapshot“, agree to take Snapshot
16. Observe the result

Expected result: The Memory Profiler takes the memory snapshot of the WebGL Player
Actual result: The memory snapshot procedure stops and hangs on status “Importing assets“ or “Taking capture…“, memory snapshot is not taken

Reproducible in: 1.0.0 (2022.3.11f1), 1.1.3 (2022.3.52f1, 6000.0.28f1 6000.1.0a5)
Could not test with: 2021.3.46f1 (Memory Profiler package is not available)

Reproducible on: macOS 14.6.1 (M1 Pro), Windows 11
Not reproducible on: No other environments tested

Note:

* Tested with: Google Chrome (Version 131.0.6778.70), Firefox (Version 132.0.2)
* Cannot reproduce when building and running the player using “Build&Run“ without “Autoconnect Profiler” option enabled, it is not possible to connect to the Player that way.
* The Memory Profiler manages to take a memory snapshot only when “Autoconnect Profiler” option is enable. This way, the snapshot can be taken if Building the Player and running it manually or Building & Running
* Can be reproduced in a new project (see internal notes)