We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
After closing the applications using ICP the /dev/shm has all the files SHMEM there.
` __IPC_SHM____AC_CONN__myq IPC_SHM____CA_CONN __IPC_SHM____QU_CONN__64__16__myq __IPC_SHM___waiter_cond___CC_CONN__myq __IPC_SHM___waiter_cond___RD_CONN__myq __IPC_SHM___waiter_cond___WT_CONN__myq __IPC_SHM___waiter_lock___CC_CONN__myq __IPC_SHM___waiter_lock___RD_CONN__myq __IPC_SHM___waiter_lock___WT_CONN__myq
__IPC_SHM___waiter_lock___RD_CONN__ocean __IPC_SHM___waiter_lock___WT_CONN__ocean `
The text was updated successfully, but these errors were encountered:
What is your use case like?
Sorry, something went wrong.
我遇到过你这个问题。主要是应用程序退出的时候没有析构你自己创建出来的ipc sender或者ipc reader。比如你将ipc sender定义为全局变量的时候。程序突然退出。那么这些文件是会存在在哪里的。
No branches or pull requests
After closing the applications using ICP the /dev/shm has all the files SHMEM there.
`
__IPC_SHM____AC_CONN__myq
IPC_SHM____CA_CONN
__IPC_SHM____QU_CONN__64__16__myq
__IPC_SHM___waiter_cond___CC_CONN__myq
__IPC_SHM___waiter_cond___RD_CONN__myq
__IPC_SHM___waiter_cond___WT_CONN__myq
__IPC_SHM___waiter_lock___CC_CONN__myq
__IPC_SHM___waiter_lock___RD_CONN__myq
__IPC_SHM___waiter_lock___WT_CONN__myq
__IPC_SHM___waiter_lock___RD_CONN__ocean
__IPC_SHM___waiter_lock___WT_CONN__ocean
`
The text was updated successfully, but these errors were encountered: