Home/ Questions/Q 3982380
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-20T05:31:16+00:00

Coming from WinForms/WPF I’ve learned the hard way that not remembering to unhook event

  • 0

Coming from WinForms/WPF I’ve learned the hard way that not remembering to unhook event handlers can lead to memory leaks.

Does this apply to Webapps too? It seems like when the request ends, everything (non-static) should be eligible for garbage collection. Is that true?

I remember jumping through all sorts of hoops to ensure that events got unhooked when an object goes out of scope, especially with multi-threading going on to ensure a responsive UI. Is all of that still necessarily in a webapp or is that one of the luxuries of working with a (mostly) RESTful model?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I don’t think you need to worry about unhooking events. You are correct that everything non-static gets queued up for garbage collection. The main thing to worry about is cleaning up unmanaged code. Make sure you wrap everything implementing IDisposable in a using{} block (or manually call Dispose() on it).

    • 0