View Issue Details

Jump to NotesJump to History
This bug affects 1 person(s).
 4
IDProjectCategoryView StatusDate SubmittedLast Update
16232Bug reports_ Unknownpublic2020-05-06 00:342020-08-28 11:30
Reporterymca Assigned Toollehar  
PrioritynoneSeverityblock 
Status closedResolutionnot fixable 
Product Version4.2.1 
Summary16232: Memory leak?
Description

I use chrome 80.0.3987.132.
I'm not sure but I think that after I made changes to the "simple options",
then chrome got bigger to around 1 giga in memory.
It happened after a couple of previews of my survey.
Did anyone came across this?
I'll investigate it more from my end.

TagsNo tags attached.
Attached Files
image_2020-05-06_01-28-24.png (73,193 bytes)   
image_2020-05-06_01-28-24.png (73,193 bytes)   
Bug heat4
Complete LimeSurvey version number (& build)Version 4.2.1+200428
I will donate to the project if issue is resolvedNo
Browser
Database type & versionsame
Server OS (if known)
Webserver software & version (if known)
PHP Versionsame

Users monitoring this issue

There are no users monitoring this issue.

Activities

ollehar

ollehar

2020-05-06 11:44

administrator   ~57571

Did the memory get freed when you closed the tab?
ymca

ymca

2020-05-06 16:40

reporter   ~57598

If you mean by closing chrome it is not appearing in the task manager then,
yes I didn't need to "end task"
ollehar

ollehar

2020-05-08 10:07

administrator   ~57626

Closing Chrome completely does not tell us if LimeSurvey or another page caused the issue. Please try again, but only close the tab containing the LimeSurvey application.
ymca

ymca

2020-07-28 23:37

reporter   ~59144

Again had a large memory.
Closed some tabs and left 3 open.
1st backend of LS
2nd frontpage of LS
3rd https://community.limesurvey.org/release/4-3-6/

Then saw mem was 600+
Closed 1st+2nd and saw it was the same.
Waited a couple of minutes and then it showed me 430~
Chrome 83.0.4103.116 (Official Build) (64-bit)
ollehar

ollehar

2020-08-21 16:58

administrator   ~59577

Last edited: 2020-08-21 16:59

100 MB per tab is not unusual. Browsers are configured to eat memory as long as it's available.

Issue History

Date Modified Username Field Change
2020-05-06 00:34 ymca New Issue
2020-05-06 00:34 ymca File Added: image_2020-05-06_01-28-24.png
2020-05-06 11:44 ollehar Note Added: 57571
2020-05-06 14:44 cdorin Status new => feedback
2020-05-06 14:44 cdorin Description Updated
2020-05-06 16:40 ymca Note Added: 57598
2020-05-06 16:40 ymca Status feedback => new
2020-05-08 10:07 ollehar Note Added: 57626
2020-05-08 10:07 ollehar Status new => feedback
2020-07-28 23:37 ymca Note Added: 59144
2020-07-28 23:37 ymca Status feedback => new
2020-08-21 16:58 ollehar Note Added: 59577
2020-08-21 16:59 ollehar Note Edited: 59577
2020-08-28 11:30 ollehar Assigned To => ollehar
2020-08-28 11:30 ollehar Status new => closed
2020-08-28 11:30 ollehar Resolution open => not fixable