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

RIDE consumes too much memory when a big suite is opened. #53

Closed
robotframework-ride opened this issue Jun 2, 2015 · 2 comments
Closed
Assignees
Labels
bug Malfunctions that should be fixed to comply with the expected behavior prio-critical Critical to RIDE functionality
Milestone

Comments

@robotframework-ride
Copy link

Originally submitted to Google Code by @yanne on 29 Sep 2008

It seems that RIDE will consume all available memory when a big suite is
opened. This is caused by creating editors for all suites during the
creation of UI. This should be changed so that the same SuiteEditor
instance is used for all suites, it is just repopulated on demand.

@robotframework-ride
Copy link
Author

Originally submitted to Google Code by @yanne on 29 Sep 2008

Proposed fix implemented in r45-r48.
It is being currently tested

@robotframework-ride robotframework-ride added this to the 0.9.1 milestone Jun 2, 2015
@robotframework-ride robotframework-ride added bug Malfunctions that should be fixed to comply with the expected behavior prio-critical Critical to RIDE functionality labels Jun 2, 2015
@robotframework-ride
Copy link
Author

Originally submitted to Google Code by @yanne on 30 Sep 2008

Fixed in r46, r47

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Malfunctions that should be fixed to comply with the expected behavior prio-critical Critical to RIDE functionality
Projects
None yet
Development

No branches or pull requests

2 participants