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.

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

Memory leak in the latest ML.NET 1.3.1 #4134

Closed
SnakyBeaky opened this issue Aug 20, 2019 · 1 comment · Fixed by #4223
Closed

Memory leak in the latest ML.NET 1.3.1 #4134

SnakyBeaky opened this issue Aug 20, 2019 · 1 comment · Fixed by #4223
Assignees

Comments

@SnakyBeaky
Copy link
Contributor

System information

  • OS version/distro: Windows 10 Pro 10.0.17763
  • .NET Version (eg., dotnet --info): .NET Core 2.2.203 e5bab63eca

Issue

  • What did you do? Update the NuGet references to Microsoft.ML.* from 1.2.0 to 1.3.1.
  • What happened? Memory leaking
  • What did you expect? Same behaviour as before

Source code / logs

The pipeline consists of a ValueToKey mapping, loading image, resizing and extracting pixels, input them into an tensorflow inception model and finally a LbfgsMaximumEntropy trainer.

This is a run training several models in 1.2.0:
image

The same exact code, running in 1.3.1:
image

Object count and heap size are more or less stable, my guess is something related to the tensorflow model not being cleared up.
image

@codemzs
Copy link
Member

codemzs commented Aug 20, 2019

Thanks! Looking at this.

@codemzs codemzs self-assigned this Aug 20, 2019
@codemzs codemzs assigned KsenijaS and unassigned codemzs Sep 6, 2019
@ghost ghost locked as resolved and limited conversation to collaborators Mar 20, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants