UUM-105139
Fixed in 6000.1.8f1Mentioned in 42 Unity 6 release notes.
First fixed in 6000.1.8f1 (Jun 18, 2025); relisted in 24 later releases.
| Version | Section | Risk | Impact | Note |
|---|---|---|---|---|
| 6000.3.0f1 | Fixes Mono | Fix | Fixed GC Handle leak that would happen every time a new function pointer was returned for a managed delegate. | |
| 6000.3.0b10 | Fixes Mono | Fix | Fixed GC Handle leak that would happen every time a new function pointer was returned for a managed delegate. | |
| 6000.3.0b9 | Fixes Mono | Fix | Fixed GC Handle leak that would happen every time a new function pointer was returned for a managed delegate. | |
| 6000.3.0b8 | Fixes Mono | Fix | Fixed GC Handle leak that would happen every time a new function pointer was returned for a managed delegate. | |
| 6000.3.0b7 | Fixes Mono | Fix | Fixed GC Handle leak that would happen every time a new function pointer was returned for a managed delegate. | |
| 6000.3.0b6 | Fixes Mono | Fix | Fixed GC Handle leak that would happen every time a new function pointer was returned for a managed delegate. | |
| 6000.3.0b5 | Fixes Mono | Fix | Fixed GC Handle leak that would happen every time a new function pointer was returned for a managed delegate. | |
| 6000.3.0b3 | Fixes Mono | Fix | Fixed GC Handle leak that would happen every time a new function pointer was returned for a managed delegate. | |
| 6000.3.0b2 | Fixes Mono | Fix | Fixed GC Handle leak that would happen every time a new function pointer was returned for a managed delegate. | |
| 6000.3.0b1 | Fixes Mono | Fix | Fixed GC Handle leak that would happen every time a new function pointer was returned for a managed delegate. | |
| 6000.3.0a5 | Fixes Mono | Fix | Fixed GC Handle leak that would happen every time a new function pointer was returned for a managed delegate. | |
| 6000.2.0f1 | Fixes Mono | Fix | Fixed GC Handle leak that would happen every time a new function pointer was returned for a managed delegate. | |
| 6000.2.0b13 | Fixes Mono | Fix | Fixed GC Handle leak that would happen every time a new function pointer was returned for a managed delegate. | |
| 6000.2.0b12 | Fixes Mono | Fix | Fixed GC Handle leak that would happen every time a new function pointer was returned for a managed delegate. | |
| 6000.2.0b11 | Fixes Mono | Fix | Fixed GC Handle leak that would happen every time a new function pointer was returned for a managed delegate. | |
| 6000.3.0a3 | Fixes Mono | Fix | Fixed GC Handle leak that would happen every time a new function pointer was returned for a managed delegate. | |
| 6000.3.0a2 | Fixes Mono | Fix | Fixed GC Handle leak that would happen every time a new function pointer was returned for a managed delegate. | |
| 6000.2.0b10 | Fixes Mono | Fix | Fixed GC Handle leak that would happen every time a new function pointer was returned for a managed delegate. | |
| 6000.2.0b9 | Fixes Mono | Fix | Fixed GC Handle leak that would happen every time a new function pointer was returned for a managed delegate. | |
| 6000.2.0b8 | Fixes Mono | Fix | Fixed GC Handle leak that would happen every time a new function pointer was returned for a managed delegate. | |
| 6000.0.52f1 | Fixes Mono | Fix | Fixed GC Handle leak that would happen every time a new function pointer was returned for a managed delegate. | |
| 6000.2.0b7 | Fixes Mono | Fix | Fixed GC Handle leak that would happen every time a new function pointer was returned for a managed delegate. | |
| 6000.2.0b6 | Fixes Mono | Fix | Fixed GC Handle leak that would happen every time a new function pointer was returned for a managed delegate. | |
| 6000.2.0b6 | Fixes Mono | Fix | Fixed GC Handle leak that would happen every time a new function pointer was returned for a managed delegate. | |
| 6000.1.8f1 | Fixes Mono | Fix | Fixed GC Handle leak that would happen every time a new function pointer was returned for a managed delegate. | |
| 6000.1.7f1 | Known Issues Mono | Caution | Known issue | UnmanagedReadOrWrite objects are not disposed off when GZipStream is used in the "using" statement |
| 6000.0.51f1 | Known Issues Mono | Caution | Known issue | UnmanagedReadOrWrite objects are not disposed off when GZipStream is used in the "using" statement |
| 6000.2.0b5 | Known Issues Mono | Caution | Known issue | Fixed GC Handle leak that would happen every time a new function pointer was returned for a managed delegate. (UUM-105139) Fixed in 6000.2.0b6. |
| 6000.1.6f1 | Known Issues Mono | Caution | Known issue | UnmanagedReadOrWrite objects are not disposed off when GZipStream is used in the "using" statement |
| 6000.2.0b4 | Known Issues Mono | Caution | Known issue | UnmanagedReadOrWrite objects are not disposed off when GZipStream is used in the "using" statement |
| 6000.2.0b3 | Known Issues Mono | Caution | Known issue | UnmanagedReadOrWrite objects are not disposed off when GZipStream is used in the "using" statement |
| 6000.0.50f1 | Known Issues Mono | Caution | Known issue | UnmanagedReadOrWrite objects are not disposed off when GZipStream is used in the "using" statement |
| 6000.1.5f1 | Known Issues Mono | Caution | Known issue | UnmanagedReadOrWrite objects are not disposed off when GZipStream is used in the "using" statement |
| 6000.1.4f1 | Known Issues Mono | Caution | Known issue | UnmanagedReadOrWrite objects are not disposed off when GZipStream is used in the "using" statement |
| 6000.2.0b2 | Known Issues Mono | Caution | Known issue | UnmanagedReadOrWrite objects are not disposed off when GZipStream is used in the "using" statement |
| 6000.2.0b1 | Known Issues Mono | Caution | Known issue | UnmanagedReadOrWrite objects are not disposed off when GZipStream is used in the "using" statement |
| 6000.2.0a10 | Known Issues Mono | Caution | Known issue | UnmanagedReadOrWrite objects are not disposed off when GZipStream is used in the "using" statement |
| 6000.2.0a9 | Known Issues Mono | Caution | Known issue | UnmanagedReadOrWrite objects are not disposed off when GZipStream is used in the "using" statement |
| 6000.2.0a8 | Known Issues Mono | Caution | Known issue | UnmanagedReadOrWrite objects are not disposed off when GZipStream is used in the "using" statement |
| 6000.2.0a6 | Known Issues Mono | Caution | Known issue | UnmanagedReadOrWrite objects are not disposed off when GZipStream is used in the "using" statement |
| 6000.2.0a4 | Known Issues Mono | Caution | Known issue | UnmanagedReadOrWrite objects are not disposed off when GZipStream is used in the "using" statement |
| 6000.2.0a1 | Known Issues Mono | Caution | Known issue | UnmanagedReadOrWrite objects are not disposed off when GZipStream is used in the "using" statement |