I wonder if SharedBuffer is kept while low-memory handler is invoked. To examine the current state, we would like to have a break-down mechanism for SharedBuffer.