Bug #1148
Memory leak
Start date:
01/09/2016
Due date:
% Done:
100%
History
#1 Updated by Luke Murphey almost 9 years ago
- Target version set to 2.3.1
#3 Updated by Luke Murphey almost 9 years ago
I'm profiling this with the Unix app:
source=top PID=2683 | timechart max(RES) as memory
#4 Updated by Luke Murphey almost 9 years ago
Memory doesn't recover much when the show is stopped.
#5 Updated by Luke Murphey almost 9 years ago
This may indicate the root cause: http://stackoverflow.com/questions/12128458/iframes-and-memory-management-in-javascript
#6 Updated by Luke Murphey almost 9 years ago
The techniques in the first link failed. Trying these: http://stackoverflow.com/questions/8407946/is-it-possible-to-use-iframes-in-ie-without-memory-leaks
#8 Updated by Luke Murphey almost 9 years ago
- Status changed from New to In Progress
#9 Updated by Luke Murphey almost 9 years ago
Things to look into:
- Identify places where the the parent injects code into the other frame
- wireUpSlideFrameControls()
- nprogress
- See if running in a new window fixes the problem
#10 Updated by Luke Murphey almost 9 years ago
Including the purge code, the overlay controls and removing the nprogress seems to fix the memory issue.
#11 Updated by Luke Murphey almost 9 years ago
The progress indicator seems to be ok, it appears to be an issue with the overlay controls.
#12 Updated by Luke Murphey almost 9 years ago
Unbinding this.slideshow_window.document seems to fix the problem.
#14 Updated by Luke Murphey almost 9 years ago
- Status changed from In Progress to Closed
- % Done changed from 0 to 100