Correct possible error on Rasterizer Caches
There was a weird bug that could happen if the object died directly and the cache address wasn't stored.
This commit is contained in:
		 Fernando Sahmkow
					Fernando Sahmkow
				
			
				
					committed by
					
						 FernandoS27
						FernandoS27
					
				
			
			
				
	
			
			
			 FernandoS27
						FernandoS27
					
				
			
						parent
						
							c63e68c480
						
					
				
				
					commit
					3a08c3207b
				
			| @@ -147,8 +147,9 @@ protected: | ||||
|  | ||||
|         object->SetIsRegistered(false); | ||||
|         rasterizer.UpdatePagesCachedCount(object->GetCpuAddr(), object->GetSizeInBytes(), -1); | ||||
|         const CacheAddr addr = object->GetCacheAddr(); | ||||
|         interval_cache.subtract({GetInterval(object), ObjectSet{object}}); | ||||
|         map_cache.erase(object->GetCacheAddr()); | ||||
|         map_cache.erase(addr); | ||||
|     } | ||||
|  | ||||
|     /// Returns a ticks counter used for tracking when cached objects were last modified | ||||
|   | ||||
		Reference in New Issue
	
	Block a user