shmop_close doesn't delete the memory segment, it just detaches from it.
If you have created the block and need to delete it you must call shmop_delete **BEFORE** calling shmop_close (for reasons outlined in shmop_delete help page notes).
(PHP 4 >= 4.0.4, PHP 5, PHP 7, PHP 8)
shmop_close — Chiusura di un blocco di memoria condivisa
Si utilizza la funzione shmop_close() per chiudere un segmento di memoria condivisa.
La funzione shmop_close() ha un solo parametro, shmid, che è l'identificativo del blocco di memoria condivisa creato da shmop_open().
Example #1 Chiusura di un blocco di memoria condivisa
<?php
shmop_close($shm_id);
?>
In questo esempio si chiude il blocco di memoria condivisa identificata da $shm_id.
shmop_close doesn't delete the memory segment, it just detaches from it.
If you have created the block and need to delete it you must call shmop_delete **BEFORE** calling shmop_close (for reasons outlined in shmop_delete help page notes).As explained on this page, PHP 8.0.0 expects a Shmop instance instead of a resource. According to bug #81098 this change means that the Shmop closes itself when the script completes so there is no need to close it with shmop_close.
Using function_exists('shmop_close') will return true but calling shmop_close will throw a deprecation error.
The documentation explains the change in 8.0.0 expects the expected argument changed without mentioning it'll just throw a deprecation error.