openshot.bugs team mailing list archive

[Jonathan Thomas <Jonathan.Oomph@xxxxxxxxx>]

Thanks for the detailed bug report.  However, it would be helpful to
have a simpler way to reproduce this.  I have a hunch that this is more
related to using FLV than all the other steps.  Can you retry these
steps using other formats / codecs of videos, and see if you have the
same results?  Thanks!

** Changed in: openshot
       Status: Triaged => Incomplete

-- 
You received this bug notification because you are a member of OpenShot
Bugs, which is subscribed to OpenShot Video Editor.
https://bugs.launchpad.net/bugs/877175

Title:
  Severe Memory Leak

Status in OpenShot Video Editor:
  Incomplete

Bug description:
  1. Create a new project.
  2. Add 7 videos, each 10 minutes long (in FLV format).
  3. Drag the first video into Track 1.
  4. Create two images (same dimensions as the videos: 860x507.
  5. Crop the video at various places.
  6. Drag an image into Track 2.
  7. Make transitions into the second track, for the image.
  8. Make six cuts at the same location in Track 1.
  9. Move the right-hand side of the cut video.
  10. Start trying to delete the small slices of video that remain.

  At this point, try to use OpenShot as normal: resize clips, move
  clips, etc.

  Expected Results

  OpenShot continues as normal.

  Actual Results

  OpenShot eats through memory like a hog at a pie-eating contest. CPU
  melts. RAM vacates the city. Earth starts to melt.

  See attached capture of 'top' showing OpenShot chewing through 10 GB
  virtual  memory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/openshot/+bug/877175/+subscriptions