mirror of
https://github.com/NickeManarin/ScreenToGif.git
synced 2026-04-26 07:35:54 +03:00
[GH-ISSUE #139] Importing from MP4 & Extreme Memory Usage #121
Labels
No labels
copy cats
duplicated
future feature
pull-request
⬜ Accepted
⬜ Completed
⬜ Help Wanted 💪
⬜ In Progress
⬜ Missing Details
⬜ Pending
⬜ Waiting For Answer ⏳
🆕 feature preview
🔷 Bug 🐛
🔷 Out Of Scope
🔷 Out Of Scope
🔷 Question
🔷Enhancement
🔷Enhancement
🔷Invalid / External
🔷Knowledge Base
🔷Won't Fix
🕑 High
🕑 High
🕑 High
🕕 Medium
🕙 Low
🕛 Critical
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ScreenToGif#121
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @changbowen on GitHub (May 17, 2017).
Original GitHub issue: https://github.com/NickeManarin/ScreenToGif/issues/139
Originally assigned to: @NickeManarin on GitHub.
First of all thanks for the great app.
Something I find is that when importing an mp4 file (720p), if i set scale to 25%, and set the start and end time, then start importing, the program would consume over 6 out of 8GB of RAM and OS starts to write to the page file like crazy.
After loading, under Statistics the size shows something really large like 5124 * 6841.
Bug?
And some of the imported frames shares the same content. When played the gif looks as if some frames are dropped.
Also I tried using the feedback directly from the app but it prompts me that I'm running from source code which I'm not.
@NickeManarin commented on GitHub (May 17, 2017):
OHHHHH, sorry for that. :/
The scaling and the feedback bugs are fixed. About the memory usage, I'm not able to fix it yet.
Thank you.