Project

General

Profile

Bug #1148

Memory leak

Added by Luke Murphey over 8 years ago. Updated over 8 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Start date:
01/09/2016
Due date:
% Done:

100%


memory_use.png View (33.9 KB) Luke Murphey, 01/13/2016 07:09 AM

History

#1 Updated by Luke Murphey over 8 years ago

  • Target version set to 2.3.1

#3 Updated by Luke Murphey over 8 years ago

I'm profiling this with the Unix app:

source=top PID=2683 | timechart max(RES) as memory

#4 Updated by Luke Murphey over 8 years ago

Memory doesn't recover much when the show is stopped.

#8 Updated by Luke Murphey over 8 years ago

  • Status changed from New to In Progress

#9 Updated by Luke Murphey over 8 years ago

Things to look into:
  1. Identify places where the the parent injects code into the other frame
    1. wireUpSlideFrameControls()
    2. nprogress
  2. See if running in a new window fixes the problem

#10 Updated by Luke Murphey over 8 years ago

Including the purge code, the overlay controls and removing the nprogress seems to fix the memory issue.

#11 Updated by Luke Murphey over 8 years ago

The progress indicator seems to be ok, it appears to be an issue with the overlay controls.

#12 Updated by Luke Murphey over 8 years ago

Unbinding this.slideshow_window.document seems to fix the problem.

#13 Updated by Luke Murphey over 8 years ago

#14 Updated by Luke Murphey over 8 years ago

  • Status changed from In Progress to Closed
  • % Done changed from 0 to 100

Also available in: Atom PDF