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

fix: Fix Huge Memory consumption in WebDav Access - EXO-68314 #308

Merged
merged 1 commit into from
Dec 16, 2023

Conversation

boubaker
Copy link
Member

Prior to this change, when accessing webdav and getting a property or check it, the jcr:data content is parsed as string and added in properties list. This change will make the property value lazily loaded only when really needed and not when building the Property object.

Prior to this change, when accessing webdav and getting a property or check it, the jcr:data content is parsed as string and added in properties list. This change will make the property value lazily loaded only when really needed and not when building the Property object.
@boubaker boubaker marked this pull request as ready for review December 16, 2023 14:14
@boubaker boubaker enabled auto-merge (squash) December 16, 2023 14:43
@Jihed525 Jihed525 changed the title fix: Fix Huge Memory consumption in WebDav Access fix: Fix Huge Memory consumption in WebDav Access - EXO-68314 Dec 16, 2023
@boubaker boubaker disabled auto-merge December 16, 2023 14:50
@boubaker boubaker enabled auto-merge (squash) December 16, 2023 14:50
@boubaker boubaker merged commit 6132294 into develop Dec 16, 2023
4 of 5 checks passed
@boubaker boubaker deleted the fix-oom-webdav branch December 16, 2023 14:53
Jihed525 pushed a commit that referenced this pull request Dec 16, 2023
Prior to this change, when accessing webdav and getting a property or check it, the jcr:data content is parsed as string and added in properties list. This change will make the property value lazily loaded only when really needed and not when building the Property object.

(cherry picked from commit 6132294)
Jihed525 added a commit that referenced this pull request Dec 16, 2023
…310)

Prior to this change, when accessing webdav and getting a property or check it, the jcr:data content is parsed as string and added in properties list. This change will make the property value lazily loaded only when really needed and not when building the Property object.

(cherry picked from commit 6132294)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants