Coder Social home page Coder Social logo

Comments (10)

finbarrtimbers avatar finbarrtimbers commented on June 2, 2024 1

Memory leak appears to have been fixed- thanks for the quick patch!

from jelly-bean-world.

asaparov avatar asaparov commented on June 2, 2024

Thanks for the report! I'll look into this and see if I can find the memory leak.

I think your current workflow is fine for episodic experiments. JBW was designed specifically for the never-ending/continual setting so we didn't do much testing for episodic use-cases.

from jelly-bean-world.

finbarrtimbers avatar finbarrtimbers commented on June 2, 2024

That makes sense. This would be difficult to find in the continual setting, as as it's only 12MiB.

from jelly-bean-world.

asaparov avatar asaparov commented on June 2, 2024

I just pushed a commit that fixes one memory leak. It was a subtle bug where we were creating a cyclic reference where C++ would reference the callback functions in the Simulator object, and the callbacks and Simulator object reference each other. So the Simulator object would never be garbage collected, even if there were no references to it from Python.

You might need to force garbage collection after each episode if you want to make sure that memory usage stays constant, otherwise it seems to garbage collect every ~10 episodes in my tests.

from jelly-bean-world.

asaparov avatar asaparov commented on June 2, 2024

Let me know if this change fixes the issue in your setup.

from jelly-bean-world.

finbarrtimbers avatar finbarrtimbers commented on June 2, 2024

from jelly-bean-world.

sophistz avatar sophistz commented on June 2, 2024

Hi, I think with the updated simulator.py and simulator.cpp, the "jbw-v1" environment is not returning correct reward value. Can you please double check this?

from jelly-bean-world.

asaparov avatar asaparov commented on June 2, 2024

Oh weird. Thanks for letting me know. I'll look into it.

from jelly-bean-world.

asaparov avatar asaparov commented on June 2, 2024

@sophistz I found an bug that I had created in fixing the memory leak. 😅 I just pushed some changes that will hopefully fix it.

from jelly-bean-world.

sophistz avatar sophistz commented on June 2, 2024

@asaparov Thanks. The code works now!

from jelly-bean-world.

Related Issues (14)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.