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

[Workflows] Potential memory leak #6399

Closed
olitomlinson opened this issue May 24, 2023 · 0 comments
Closed

[Workflows] Potential memory leak #6399

olitomlinson opened this issue May 24, 2023 · 0 comments
Assignees
@cgillum
Labels
kind/bug Something isn't working
Milestone
v1.11

Comments

@olitomlinson
Copy link

olitomlinson commented May 24, 2023 •
edited
Loading

cc @yaron2 @cgillum

As per discord, Memory hits between 300-400mb and never releases after all workflows have completed.

my local environment

  • Mac OS - M1
  • Docker Desktop 4.19.0 (106363)

Can reproduce this on the following dapr sidecar versions

1.11.0-rc.3
(not tried earlier versions)

client libraries

<PackageReference Include="Dapr.Client" Version="1.10.0" />
<PackageReference Include="Dapr.Workflow" Version="1.10.0" />`

Repro steps

  1. pull repo https://github.com/olitomlinson/dapr-workflow-examples
  2. docker compose build
  3. docker compose up
  4. Use insomnia/postman/whatever :
    POST http://localhost:5112/start?count=2000&async=true<- make this request just once to start 2000 workflows
  5. Takes approx 20 minutes to start and complete all workflows.
  6. Observe the dapr sidecar consume lots of memory, most of which doesn't get released
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@cgillum cgillum

Labels
kind/bug Something isn't working
Projects
None yet
Milestone
v1.11
Development

No branches or pull requests
3 participants
@artursouza @cgillum @olitomlinson