From 94fea5c38cf9ad4cf1342597fcc93c23ab2272e7 Mon Sep 17 00:00:00 2001
From: Robert Beckebans <robert.beckebans@gmail.com>
Date: Sun, 29 May 2022 12:14:26 +0200
Subject: [PATCH] Possible FBO mem leak fix #664

---
 neo/renderer/NVRHI/Framebuffer_NVRHI.cpp | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/neo/renderer/NVRHI/Framebuffer_NVRHI.cpp b/neo/renderer/NVRHI/Framebuffer_NVRHI.cpp
index 4c0b2316..9f55e066 100644
--- a/neo/renderer/NVRHI/Framebuffer_NVRHI.cpp
+++ b/neo/renderer/NVRHI/Framebuffer_NVRHI.cpp
@@ -75,6 +75,7 @@ Framebuffer::Framebuffer( const char* name, const nvrhi::FramebufferDesc& desc )
 
 Framebuffer::~Framebuffer()
 {
+	apiObject.Reset();
 }
 
 void Framebuffer::Init()
@@ -101,7 +102,7 @@ void Framebuffer::ResizeFramebuffers()
 	tr.backend.ClearCaches();
 
 	// RB: FIXME I think allocating new Framebuffers lead to a memory leak
-	//framebuffers.DeleteContents( true );
+	framebuffers.DeleteContents( true );
 
 	uint32_t backBufferCount = deviceManager->GetBackBufferCount();
 	globalFramebuffers.swapFramebuffers.Resize( backBufferCount );