Search Issue Tracker
Won't Fix
Fixed in 2018.3
Votes
0
Found in
2018.2.5f1
Issue ID
1087371
Regression
No
Linking Go code causes Garbage Collector to fail on Linux
To reproduce:
1) Open attached project
2) Open System Monitor (or another app for tracking memory usage)
3) Build and run for Linux
4) Leave it for a while
Notice that memory steadily climbs, roughly half an MB a second
Not reproduced in Windows 10 (memory stays the same all the time)
Reproduced in 2018.2.10f1
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
- Dynamic Clipping works poorly with large scenes / terrains with the pivot point is near
- [UWP] Deploying wrong architecture through device portal ends up running a different app
- [MacOS] Standalone build contains .meta files inside native plugin bundles
- Progressive lightmapper leaks memory upon subsequent scene switches and bakes
- [AssetBundle] "The referenced script (Unknown) on this Behaviour is missing!" errors when loading object from Asset Bundle
Resolution Note (fix version 2019.1):
Not supporting Go plugins in Unity. Suggest golang not modify signal dispositions at start, which confuses bdwgc and results in heap corruption.