Deep Profiler not respecting Command line memory allocation over-ride.

CONTEXT:

There is a bug in Unity's Deep profiling system which is causing Integer overflow when a Memory allocation value is assigned via Hub's Command Line argument.

The ticket for which is opened here:
[Internal link]

Above bug has a cascading Halo affect on WebGL Platform:

When assigning a mem-allocation value via the Hub's command line, after a project is "built to run" with Deep profiling (dev build) enabled, the end output completely (attached to browser) fails to respect the original command line value assigned via Hub.

Example here:

---

 Steps to Repo:

1. Open empty project (like BiRP 2D) with a command line argument of:
-profiler-maxusedmemory 20000000

2. Attach the provided Profiler debug script to any in-scene game object like the camera, switch to WebGL Platform and Hit play.

3. Observe the console debug log O/P stating the value to be "Profiler Memory allocation: 20000000"

4. On the Console window, remove the check box which says "Clear on build" and "Clear on Play"

5. Build to run in Dev mode with Attached profiler, with following settings:

6. Once the default browser opens, press CTRL+SHIFT+I (on chrome/firefox) or equivalent to open dev console, wait for project to complete load.

7. Observe the console log in the browser, its should state a value like "Profiler Memory allocation: 16777216"

**

---

The following cases are same as ones for Deep Profiling ticket and should be dealt with:

> -profiler-maxusedmemory should be limited to Int32.maxValue as per C# documentation.

> Edge case:  where Profiler.maxUsedMemory can be set to 0, and its allowed. But this value gets' over-ridden in WebGL magically.

> Profiler.maxUsedMemory can be set to -1;
> Documentation should be updated to reflect above fixes.

Note: The bug does not happen if  Profiler.maxUsedMemory is set in C# above the magical stated value of 1 and Int32.MaxValue.

**

---

Other side effects/Instablity caused due to this bug:

> In a project once deep profile reaches insufficient memory,  the Editor console spams with :

1.  Change of state for unknown Category ID %d

2. Unknown macro:
   Unknown macro: { Unknown macro}
   }

3. Unknown macro:
   Unknown macro: { Unknown macro}
   }

> There is a 30-40% chance that the tab does not even load, the Chrome popup saying "do you want to wait/kill" shows up. I am not able to reliably  repo this aspect.

> There is a chance where the Profiler just wont even auto-connect (can't get to repo this reliably either, but it happens).

---

Regression note: This bug was found in 2023.2.0a21 and I backtracked to 2020.3.48f1 (viz. LTS at the time or writing) and its happening there too. I don't know how long back since this bug has existed beyond LTS.

This may be happening since 2019 as the thread states here
There is a forum thread related to same issue here started in 2019