- Home /
How should auto profiler appear in WebGL build?
I have WebGL build out of memory on loading screen at 256MB or 512MB. It runs in local host fine but not when deployed to GIthub Pages.
So now I made new development build, with autoconnect profiler, what is supposed to happen in this case? Is the profiler supposed to start within the Unity Editor when the WebGL build is played? Mine just still stops near the end of loading bar, I can see stack trace errors in the Javascript console, but am I supposed to do something to make the profiler start?
I have the new build running in Chrome local host, and Unity Editor open with the project itself, and nothing happens in profiler window.
Tx any suggestions.
Your answer
Follow this Question
Related Questions
How to profile a WebGL app using the unity profiler tool? 0 Answers
Why does "Clear" under Render.OpaqueGeometry spike every few frames in WebGL? 0 Answers
WaitForTargetFPS slowing WebGL to unacceptable levels 1 Answer
Unable to connect profiler to WebGL 2 Answers
Why does Unity Windows build use up more memory than WebGL? 0 Answers