From 26d15fc35eca73f175967eaa4f671e9c4ac3cca6 Mon Sep 17 00:00:00 2001
From: Silvan Sievers <silvan.sievers@unibas.ch>
Date: Fri, 13 Oct 2023 11:13:14 +0200
Subject: [PATCH] link to issue

---
 src/search/state_registry.cc | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/src/search/state_registry.cc b/src/search/state_registry.cc
index ff79594ca4..22a874856b 100644
--- a/src/search/state_registry.cc
+++ b/src/search/state_registry.cc
@@ -73,7 +73,8 @@ State StateRegistry::get_successor_state(const State &predecessor, const Operato
     /*
       TODO: ideally, we would not modify state_data_pool here and in
       insert_id_or_pop_state, but only at one place, to avoid errors like
-      buffer becoming a dangling pointer.
+      buffer becoming a dangling pointer. This used to be a bug before being
+      fixed in https://issues.fast-downward.org/issue1115.
     */
     state_data_pool.push_back(predecessor.get_buffer());
     PackedStateBin *buffer = state_data_pool[state_data_pool.size() - 1];