Skip to content

Memory leak while facing high pressure workload #782

Closed

Description

@iosmanthus

Bug Report

1. Describe the bug

266043:2024-03-28 15:43:06,739 5959 [pool-14-thread-670] ERROR org.tikv.shade.io.netty.util.ResourceLeakDetector  - LEAK: ByteBuf.release() was not called before it's garbage-collected. See https://netty.io/wiki/reference-counted-objects.html for more information.

2. Minimal reproduction step (Required)

Run https://github.com/iosmanthus/client-java-bench with the following commands:

java -cp target/client-java-bench-1.0-SNAPSHOT-jar-with-dependencies.jar -Dio.netty.leakDetection.level=paranoid Bench -pd 127.0.0.1:2379 -prefix test -type flow -threads 1000 -duration 3600 -timeout 400 -report ./report.json -log test.log

3. What did you see instead (Required)

266043:2024-03-28 15:43:06,739 5959 [pool-14-thread-670] ERROR org.tikv.shade.io.netty.util.ResourceLeakDetector  - LEAK: ByteBuf.release() was not called before it's garbage-collected. See https://netty.io/wiki/reference-counted-objects.html for more information.

4. What did you expect to see? (Required)

No memory leak log

5. What are your Java Client and TiKV versions? (Required)

  • Client Java: master
  • TiKV: v6.5.3

Activity

  1. added a commit that references this issue on Mar 28, 2024
    ca8a622
  2. added a commit that references this issue on Jun 3, 2024
    cfe12d0
  3. added a commit that references this issue on Jun 4, 2024
    700fad0
  4. added 2 commits that reference this issue on Apr 18, 2025
    49642a3
    93ba656
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    type/bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions