Search Issue Tracker
Fixed in 2019.1.X
Votes
0
Found in
2018.3.0a1
2018.3.2f1
Issue ID
1118833
Regression
Yes
Building an application generates WinPixEventRuntime.dll when "Development Build" is unchecked and "Architecture" is "x86_64"
How to reproduce:
1. Create a new Unity project
2. Navigate to File -> Build Settings... -> make sure "Development Build" is unchecked and "Architecture" is "x86_64"
3. Build an application
4. After the Building is complete, observe the Build location folder
Expected result: the WinPixEventRuntime.dll file is not found
Actual result: the WinPixEventRuntime.dll file is found even though the "Development Build" is unchecked
Reproducible with: 2018.3.3f2, 2019.1.0a14, 2019.2.0a2
Not reproducible with: 2017.4.19f1
Comments (2)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- UI becomes unresponsive when using AppUI Navigation and Event System is attached
- PlayerPrefs get corrupted when a minimized fullscreen Player is closed through the Taskbar
- "To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations." warning is printed when JobTempMemoryLeakValidation switch is enabled
- Main Thread stalling when loading Audio Source asset asynchronously while preloading another Audio Source asset
- Material artifacts occur in the Material Preview window when baked lighting is applied to scenes
Mafutta
Aug 28, 2021 23:55
still in 2020.x
Bip901
Aug 05, 2019 10:59
Are there any temporary workarounds for this issue? I'm working on a huge project so I have to freeze on version 2018.3.0f2 (64-bit).