Home / Forums / Understanding IDisposable, Finalizers, and SafeHandle in C# [Discussion #3]

UnreliableCode Community

Developer Research, Reverse Engineering & Coding Community

Subforums Leaderboard Log In to Post
Tutorial

Understanding IDisposable, Finalizers, and SafeHandle in C# [Discussion #3]

ShaderGuru
HLSL & GLSL Shader Dev
MEMBER
Rep: 219
Join Date: May 2024
Posts: 6
Thanks: 62
3y ago · Apr 19, 2023 8:39 PM
#1
A guide on implementing the standard Dispose pattern. When you manage unmanaged OS resources (like native file handles or pointers), derive from SafeHandle instead of writing manual finalizers!
ShaderGuru · HLSL & GLSL Shader Dev
Post-processing shaders, stencil buffer tricks, and screen-s...
The following users thanked ShaderGuru for this post:
MemoryLeaker
C++ Enthusiast
VIP
Rep: 182
Join Date: Sep 2022
Posts: 6
Thanks: 20
3y ago · Apr 19, 2023 11:08 PM
#2
Manual finalizers force the object into the finalizer queue, delaying GC collection to Gen2. SafeHandle encapsulates native cleanup safely without finalizer penalties on the parent class.
MemoryLeaker · C++ Enthusiast
Always remembering to delete my heap pointers... most of the...
GenericGuru
Templates & Generics
MEMBER
Rep: 154
Join Date: Apr 2023
Posts: 8
Thanks: 35
3y ago · Apr 20, 2023 12:08 AM
#3
Always suppress finalization with GC.SuppressFinalize(this) inside Dispose() if you have a custom cleanup routine.
GenericGuru · Templates & Generics
Curiously Recurring Template Pattern (CRTP), C++ concepts, a...