![]() ![]() ![]() I could click on Conversion > Stop Conversion drop-down arrow > Pause Conversion to stop the program until I told it to resume work. When I told it to export a video, its menu would add a Conversion option. To produce an output video of about 350MB from input files totaling 4.7GB, with no other significant programs running, VSDC chewed up more than 55GB of RAM and still crashed.Ī straightforward way to halt excess RAM consumption was to pause VSDC. To confirm that, I returned to this project later, as described below, after adding another 32GB, for a total of 64GB RAM. A s one would expect, VSDC seemed to be able to start its exporting operation immediately, when it had eaten only a few hundred MB of RAM it was not requiring gigabytes before it could get to work. Regrettably, that did not seem to be the situation. That would assume that VSDC was not a memory sieve – that, in other words, it was not wasting RAM, it was only seeking the amount needed to perform the job. There were a few blunt, obvious ways to try to manage the situation. No such luck with exporting: that had to proceed, so I really did need a fix for the RAM issue at that point. I had also encountered RAM-related problems when attempting to Preview this project in VSDC, but I found that I could stop the Preview and proceed with whatever I was doing. In the present case, the RAM-intensive project was exporting – that is, producing an output video. Moo0 showed that, when I told VSDC to do something RAM-intensive, free RAM would shrink rapidly, to the point where VSDC would finally crash, sometimes destabilizing other programs and even the system as a whole. I could also have used Win-R > taskmgr > Performance tab > Memory, optionally clicking Open Resource Monitor at the bottom > Memory tab, but I liked Moo0 better. Initially, to monitor the situation, I was u sing Moo0 System Monitor to track free RAM. ![]() This post describes my efforts to restrict VSDC’s RAM hunger so that it could complete the project. This Windows 10 Pro desktop system contained an Intel i5-13500 with 32GB RAM, but that didn’t seem to be enough for VSDC. As described in another post, I was using VSDC Video Editor 8.3.9 for a project involving 4,500 screenshots. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |