Memory leak may happen after calling `Bump::dealloc`.

[RinChanNOWWW]

impl Bump {
    #[inline]
    unsafe fn dealloc(&self, ptr: NonNull<u8>, layout: Layout) {
        // If the pointer is the last allocation we made, we can reuse the bytes,
        // otherwise they are simply leaked -- at least until somebody calls reset().
        if self.is_last_allocation(ptr) {
            let ptr = NonNull::new_unchecked(ptr.as_ptr().add(layout.size()));
            self.current_chunk_footer.get().as_ref().ptr.set(ptr);
        }
    }
}

Setting self.current_chunk_footer directly will lose the control of the memory in ptr..ptr.add(layout.size()).

When calling dealloc_chunk_list in drop, we cannot find the memory between ptr..ptr.add(layout.size()).

[fitzgen]

I don't believe this is a leak:

• The dealloc method is generally a no-op, since bump allocators don't support general deallocation.
• The one thing they can handle is LIFO deallocation, which is what this is handling.
• bumpalo only has a special case for LIFO deallocation within the current chunk, not across chunks.
• ptr..ptr.add(layout.size()) is within the current chunk.
• dealloc_chunk_list deallocates whole chunks at a time.
• Deallocating the chunk will also deallocate ptr..ptr.add(layout.size()).

[RinChanNOWWW]

Thank you. I misunderstood the implementation.