Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom

KinesisProducer is not correctly destroying callbackCompletionExecuto… #225

Merged
merged 1 commit into from
Nov 8, 2018
Merged

KinesisProducer is not correctly destroying callbackCompletionExecuto… #225

merged 1 commit into from
Nov 8, 2018

Commits on Sep 28, 2018

  1. KinesisProducer is not correctly destroying callbackCompletionExecutor … 

    …awslabs#224

When destroying KinesisProducer instances, destroy method is not shutting down callbackCompletionExecutor. This makes Daemon child object to still be alive occupying 8MB of heap memory each one.

Creating and destroying lots of KinesisProducer instances will result in a Heap Out Of Memory exception.
    @xbcratos
    xbcratos committed Sep 28, 2018
    Configuration menu
    Copy the full SHA
    e153a09 View commit details
    Browse the repository at this point in the history