majialoong opened a new issue, #10912: URL: https://github.com/apache/rocketmq/issues/10912
### Before Creating the Bug Report - [x] I found a bug, not just asking a question, which should be created in [GitHub Discussions](https://github.com/apache/rocketmq/discussions). - [x] I have searched the [GitHub Issues](https://github.com/apache/rocketmq/issues) and [GitHub Discussions](https://github.com/apache/rocketmq/discussions) of this repository and believe that this is not a duplicate. - [x] I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ. ### Runtime platform environment All ### RocketMQ version develop ### JDK Version All ### Describe the Bug `PopConsumerRocksdbStore.scanExpiredRecords()` creates two RocksDB Slice objects for iterator bounds without closing them, causing native memory leaks. ### Steps to Reproduce 1. Start a broker with POP consumption enabled. 2. Continuously trigger POP revive scanning. 3. Observe the broker process’s native memory usage over time. ### What Did You Expect to See? The lower-bound and upper-bound Slice objects should be closed after each scan, keeping native memory usage stable. ### What Did You See Instead? Each scan leaks two native Slice objects. Repeated revive scans may cause native memory usage to grow continuously. ### Additional Context _No response_ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
