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

Exporting eats up memory, Openshot 2.2.0, Windows 10 64-bit #361

Closed
theelectricsoul opened this Issue Oct 1, 2016 · 10 comments

Comments

Projects
None yet
5 participants
@theelectricsoul

theelectricsoul commented Oct 1, 2016

As soon as I export to a video file, you see the memory usage climb fast until memory ist eaten up. I have 16 GB of RAM. My Video ist 60 GB big.

@JtLively JtLively added the bug label Feb 25, 2017

@JtLively

This comment has been minimized.

Show comment
Hide comment
@JtLively

JtLively Feb 25, 2017

Collaborator

Have you had this same issue with newer versions?
Are you still having this issue?
What export settings are you using?

Collaborator

JtLively commented Feb 25, 2017

Have you had this same issue with newer versions?
Are you still having this issue?
What export settings are you using?

@jreynojustin

This comment has been minimized.

Show comment
Hide comment
@jreynojustin

jreynojustin Feb 28, 2017

Collaborator

OpenShot is now in Version 2.2 if you are still noticing issues in the latest version please re-open this issue letting us know.

Collaborator

jreynojustin commented Feb 28, 2017

OpenShot is now in Version 2.2 if you are still noticing issues in the latest version please re-open this issue letting us know.

@theelectricsoul

This comment has been minimized.

Show comment
Hide comment
@theelectricsoul

theelectricsoul Mar 1, 2017

Same issue.
https://youtu.be/UJpETFrFOHQ

Screenshot OS version used

Cutting and playing the file with OS 2.2.0 is also jerky. Should I open a issue for that?

theelectricsoul commented Mar 1, 2017

Same issue.
https://youtu.be/UJpETFrFOHQ

Screenshot OS version used

Cutting and playing the file with OS 2.2.0 is also jerky. Should I open a issue for that?

@theelectricsoul

This comment has been minimized.

Show comment
Hide comment

theelectricsoul commented Mar 1, 2017

@jreynojustin

This comment has been minimized.

Show comment
Hide comment
@jreynojustin

jreynojustin Mar 1, 2017

Collaborator

Nope I'll just re-open this one and change the version number. Thanks for providing that additional information!

Collaborator

jreynojustin commented Mar 1, 2017

Nope I'll just re-open this one and change the version number. Thanks for providing that additional information!

@jreynojustin jreynojustin reopened this Mar 1, 2017

@jreynojustin jreynojustin changed the title from Exporting eats up memory, Openshot 2.1.0, Windows 10 64-bit to Exporting eats up memory, Openshot 2.2.0, Windows 10 64-bit Mar 1, 2017

@Wintch

This comment has been minimized.

Show comment
Hide comment
@Wintch

Wintch Mar 22, 2017

Same here on:
windows 7 64bit Ultimate SP1 16gb RAM

I can export in FullHD, 4k eats all the RAM and crashes.
Happens with both Ogg and h264, and on all 3 quality settings
This largely depends on the length of the output video. Something about 3min will reproduce the glitch
Happens on stable and OpenShot-v2.2.0-65-g5a9712d-49-615-x86_64.exe versions
Launch.exe eats 10gb+ of RAM on my setup with 4k export, at about 30% of 3min video
With 2.5k resolution at about 50% of the same footage the same amount of RAM is gone
FullHD will get to 60% probably, then CPU usage will drop because you're swapping
Openshot Cache - 4gb on disk or 2gb on RAM, same results

32gb+ of RAM and SSD swapping could do it with 2.5k, but i can't imagine the beast you'll need for an 4k export without CPU performance penalty.

Wintch commented Mar 22, 2017

Same here on:
windows 7 64bit Ultimate SP1 16gb RAM

I can export in FullHD, 4k eats all the RAM and crashes.
Happens with both Ogg and h264, and on all 3 quality settings
This largely depends on the length of the output video. Something about 3min will reproduce the glitch
Happens on stable and OpenShot-v2.2.0-65-g5a9712d-49-615-x86_64.exe versions
Launch.exe eats 10gb+ of RAM on my setup with 4k export, at about 30% of 3min video
With 2.5k resolution at about 50% of the same footage the same amount of RAM is gone
FullHD will get to 60% probably, then CPU usage will drop because you're swapping
Openshot Cache - 4gb on disk or 2gb on RAM, same results

32gb+ of RAM and SSD swapping could do it with 2.5k, but i can't imagine the beast you'll need for an 4k export without CPU performance penalty.

@DylanC

This comment has been minimized.

Show comment
Hide comment
@DylanC

DylanC Sep 22, 2017

Collaborator

@theelectricsoul - Is this still an issue on v2.4?

Collaborator

DylanC commented Sep 22, 2017

@theelectricsoul - Is this still an issue on v2.4?

@theelectricsoul

This comment has been minimized.

Show comment
Hide comment
@theelectricsoul

theelectricsoul Sep 28, 2017

I've tested the memory hog issue. Looking good. :) Great.... thanks a lot

theelectricsoul commented Sep 28, 2017

I've tested the memory hog issue. Looking good. :) Great.... thanks a lot

@theelectricsoul

This comment has been minimized.

Show comment
Hide comment
@theelectricsoul

theelectricsoul Sep 28, 2017

Playing the file inside OS is still jerky but in sync. The playback is fluent with the audio, but the picture is jumpy . Jumps around every 500ms.

theelectricsoul commented Sep 28, 2017

Playing the file inside OS is still jerky but in sync. The playback is fluent with the audio, but the picture is jumpy . Jumps around every 500ms.

@DylanC

This comment has been minimized.

Show comment
Hide comment
@DylanC

DylanC Oct 9, 2017

Collaborator

@theelectricsoul - I'm closing this based on the feedback the memory issue is resolved. For the other issue you can comment on an existing similar ticket or log a new ticket. Thanks.

Collaborator

DylanC commented Oct 9, 2017

@theelectricsoul - I'm closing this based on the feedback the memory issue is resolved. For the other issue you can comment on an existing similar ticket or log a new ticket. Thanks.

@DylanC DylanC closed this Oct 9, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment