Out of memory #4583
Comments
|
You might want to reduce number of processes running inside the container, see https://docs.weblate.org/en/latest/admin/install/docker.html#container-settings |
|
This issue looks like a support question. We try to answer these reasonably fast, but in case you are looking for faster resolution, please consider purchasing support subscription and make Weblate stronger. |
nijel
added a commit
that referenced
this issue
Sep 24, 2020
|
This method did a little help with Weblate's freezing problem. However, Weblate continues to freezes after a few requests because CPU usage is always high(After trying to translate the translation). I also share a few other error logs I can catch below. My settings-override.py, REQUIRE_LOGIN = False
INSTALLED_APPS = [
# "o_customization",
# Weblate apps on top to override Django locales and templates
"weblate.addons",
"weblate.auth",
"weblate.checks",
"weblate.formats",
"weblate.glossary",
"weblate.machinery",
"weblate.trans",
"weblate.lang",
"weblate.langdata",
"weblate.memory",
"weblate.screenshots",
"weblate.fonts",
"weblate.accounts",
"weblate.utils",
"weblate.vcs",
"weblate.wladmin",
"weblate",
# Optional: Git exporter
"weblate.gitexport",
# Standard Django modules
"django.contrib.auth",
"django.contrib.contenttypes",
"django.contrib.sessions",
"django.contrib.messages",
"django.contrib.staticfiles",
"django.contrib.admin.apps.SimpleAdminConfig",
"django.contrib.admindocs",
"django.contrib.sitemaps",
"django.contrib.humanize",
# Third party Django modules
"social_django",
"crispy_forms",
"compressor",
"rest_framework",
"rest_framework.authtoken",
"django_filters",
]
REST_FRAMEWORK = {
# Use Django's standard `django.contrib.auth` permissions,
# or allow read-only access for unauthenticated users.
"DEFAULT_PERMISSION_CLASSES": [
# Require authentication for login required sites
"rest_framework.permissions.IsAuthenticated"
if REQUIRE_LOGIN
else "rest_framework.permissions.IsAuthenticatedOrReadOnly"
],
"DEFAULT_AUTHENTICATION_CLASSES": (
"rest_framework.authentication.TokenAuthentication",
"weblate.api.authentication.BearerAuthentication",
"rest_framework.authentication.SessionAuthentication",
),
"DEFAULT_THROTTLE_CLASSES": (
"weblate.api.throttling.UserRateThrottle",
"weblate.api.throttling.AnonRateThrottle",
),
"DEFAULT_THROTTLE_RATES": {"anon": "100/day", "user": "25000/hour"},
"DEFAULT_PAGINATION_CLASS": ("rest_framework.pagination.PageNumberPagination"),
"PAGE_SIZE": 500,
"VIEW_DESCRIPTION_FUNCTION": "weblate.api.views.get_view_description",
"UNAUTHENTICATED_USER": "weblate.auth.models.get_anonymous",
}
CHECK_LIST += (
# "o_customization.checks.PunctuationSpacingCheckO",
)
AUTOFIX_LIST += (
# "weblate.trans.autofixes.chars.ReplaceTrailingDotsWithEllipsis",
# "o_customization.autofix.PunctuationSpacingAutoFixO"
) |
|
It still seems to be out of memory issues. Can you look at individual processes how much of them is there and which consume the memory? |
|
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. |
nijel
added
bug
|
I've identified memory issue in https://github.com/WeblateOrg/translation-finder/, it is fixed in the 2.4 release and Weblate 4.3.1 will require that. |
|
Thank you for your report, the issue you have reported has just been fixed.
|
|
EDIT: Updated to bleeding edge 4.3.1 and so far so good! Workers are not going down anymore. Would this issue explain Weblate 4.3 going down after a while and all workers constantly restarting? That doesn't seem normal and this last release has been somewhat buggy.
|
|
Quite likely - there is a memory limit set for the workers and with the leak it is more likely it will reach it. |
|
@nijel I am running on a shared hosting environment with limited RAM per user (1.5 GB). I understand that Weblate states 3GB as minimal requirement but I hope to be able to run Weblate nonetheless. The requirements seem to be quite high for just a small website. But those tasks still seem to consume up to 142MB per task, as long as I am interpreting these numbers correctly. Is it normal that these tasks require so much RAM even though Weblate is completely idle / freshly set up? Even when Weblate is running with This is my celery configuration for supervisord: EDIT: I just see that the |
|
@bilalcorbacioglu Is it really necessary to post each of your posts to multiple places? Posting unrelated questions to issues that have been resolved years ago is not really helping anybody. See #10251 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the bug
Hello,
We've been getting an "Out of Memory" error periodically since we update to Weblate 4.2.2. Especially when we edit some components, For example;
Source: And that is the end of our story.
Target: Voilà, c'est la fin de l'histoire. -> Voilà, c’est la fin de l’histoire.
Source: Touch a button!
Target: Touche un bouton ! -> Touche un bouton/u202f!
Screenshots
Before click "Save"
After Click "Save"
Server configuration and status
The text was updated successfully, but these errors were encountered: