diff --git a/docs/runtime/known_issues.md b/docs/runtime/known_issues.md
index a16238e15a50edcedbd0cc583522c4f49f510944..1e6b3c7b18bf2d314979c2fec31fd7e343e67397 100644
--- a/docs/runtime/known_issues.md
+++ b/docs/runtime/known_issues.md
@@ -20,4 +20,6 @@ The current implementation of Reowolf has the following known issues:
 
 - Reserved memory for ports will grow without bounds: Ports can be given away from one component to another by creating a component, or by sending a message containing them. The component sending those ports cannot remove them from its own memory if there are still other references to the transferred port in its memory. This is because we want to throw a reasonable error if that transferred port is used by the original owner. Hence we need to keep some information about that transferred port in the sending component's memory. The solution is to have reference counting for the ports, but this is not implemented.
 
+- An extra to the above statements: when transferring ports to a new component, the memory that remembers the state of that port is removed from the component that is creating the new one. Hence using old references to that port within the creating component's PDL code results in a crash.
+
 - Some control algorithms are not robust under multithreading. Mainly error handling when in sync mode (because there needs to be a revision where we keep track of which components are still reachable by another component). And complicated scenarios where ports are transferred.
\ No newline at end of file