Search Issue Tracker
Not Reproducible
Votes
0
Found in
4.2.0f4
Issue ID
557999
Regression
No
Profiler won't work with Windows 64bit application
When building a Windows 64bit application, the profiler will never connect to the executable. This only works when building a 32bit application. To be precise: Autoconnect does not work, nor does the build show up in the "active profiler" selection screen.
To reproduce:
Hint: make sure to check "run in background" in player settings
1: Click File -> Build Settings
2: Select PC, Mac, Linux Standalone
3: Choose Windows and x86_64 from the dropdowns
4: Check "development build" and "autoconnect to profiler"
5: Click build&run and notice the profiler window. No autoconnect is taking place and the application does not show up in the "active profiler" selection
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Sprites lose their reference in Scene and Game view when changing Texture2D Import Settings
- “Assemblies” and “Areas” tabs disappears after switching to Scene tab and back in the Assemblies filter window
- Huge memory allocations when TMP dynamically adds glyphs from AssetBundle fonts
- “Redefinition of 'LOD_FADE_CROSSFADE'" shader errors thrown when opening SpeedTree9_URP.shadergraph in Universal 3D Template
- NullReferenceException is thrown and the window is broken when opening the "Active Scenario" window in Multiplayer Center
Add comment