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

Very high memory consumption after delete of languages with pending commits #3015

Closed
surli opened this issue Sep 12, 2019 · 2 comments
Closed
Labels
question This is more a question for the support than an issue. wontfix Nobody will work on this.

Comments

@surli
Copy link
Contributor

surli commented Sep 12, 2019

Describe the bug
Yesterday a new user started to translate using zh_Hans which is an unsupported language in our platform (in favor of zh). We decided to delete the language from the django admin, hoping that it would also perform a deletion of the translations.

Starting there we got apparently several issues, a new zh_HANS appeared in the admin, and at that moment celery-weblate service was down. So we decided to start it again, and to delete also zh_HANS. Then we experienced a global decrease of performance on weblate: apparently it performed a global check over the components.

Now after the check it seems that zh_HANS appeared again, but also that our memory consumption is now very very high: we managed until then to run weblate on a machine with 3Go of RAM, but apparently we now got our services OOM killed, even after increasing it to 4Go of RAM.

Note that we still have a pull request opened with 25 commits, and that this VCS is linked by 75 components. I guess deleted the languages before fixing the commits led to a weird state in Weblate, which caused the memory issue, but not sure what we should have done in such condition.

@nijel
Copy link
Member

nijel commented Sep 13, 2019

Deleting the language in the Django admin interface will lead to collecting all related objects in memory, what can lead to huge memory consumption. That's one of reasons why we're going to stop using it (see #2363). I don't think that Python will ever release once allocated memory back to the system.

@nijel nijel added the question This is more a question for the support than an issue. label Sep 13, 2019
@stale
Copy link

stale bot commented Sep 23, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix Nobody will work on this. label Sep 23, 2019
@stale stale bot closed this as completed Sep 27, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question This is more a question for the support than an issue. wontfix Nobody will work on this.
Projects
None yet
Development

No branches or pull requests

2 participants