Hi,

Like a few other posters recently, I'm having frequent crashes that seem to relate to thumbnails.

In my case it happens exclusively when I try to import new files. As soon as I click 'local files' in the Log tab, immediate crash.

I've tried ensuring other applications are closed to avoid low memory issues, but that doesn't seem to help. I've also tried disabling timeline thumbs, but only done that now so I can't tell what effect that has yet.

Attached are two OS crash logs, both from tonight, with same behaviour. Also attached most relevant Lightworks logs

best,
Scott

Hello,


Is this just a bug report addressing Editshare development or are you asking for currently known workarounds?

Sorry, yes, asking for workarounds.

First, I'm not with Editshare, just a user of the software. There are multiple bug reports dealing with the problem. It appears to happen currently mainly on OSX systems.

One of your Lightworks logs show 1.3 GB of free memory out of 16 GB, whatever this is caused by. That's not enough for stable operations. Furthermore, it appears that you use a lot of clips with inter-frame compression (long GOP). This kind of material puts high load on the computer when creating thumbnails and analyzing files, and of course, also when editing.

Saying all that, based on my current knowledge of the problem, I think the most reliable and straight forward workaround is falling back to Lightworks V14.5.

Thanks Hugly. The memory issue is frustrating, seems like even when I free up memory before opening lightworks (and close most other applications), it still drops below 4gb available memory. I'll have to look into that.

Re. falling back to lightworks 14.5, I have a couple of questions.
- will projects made in 2020 open on 14.5?
- will installing 14.5 overwrite my 'lightworks' folder, and recent projects list?

Lightworks keeps program and user data strictly separated. Installing a different version or uninstalling the current doesn't affect user data. You can even install multiple versions sided by side on OSX and Windows and work on the same projects. I switch between V14.0., V14.5 and 2020.1 quite frequently without trouble.

To move to the absolutely safe side, you can make a copy of the user folder 'Lightworks', which contains all project data, media links and settings, prior to installing V14.5. You'll find it in your home directory: "/Users/<current user>/Lightworks"

I'm using a different operating system, but I think you should investigate first:

mugloch wrote:

I've switched between V14.5 and V2020.1 during the beta testing period without any issues.

The projects folder is in a separate location on your computer.

Thanks Hugly, Schrauber, and briandrys!

How does OSX manage inactive RAM, where closed programs, data etc. are buffered (cache in RAM, not on the drive)? Is it marked as available memory, as in Win 10, which is automatically and immediately available for active program when needed?

Do you use an Intel GPU- which uses video memory from shared RAM? If so, how does OSX or the graphics drivers manage the memory allocated for the GPU? Can you monitor the memory currently used by the GPU? Is the memory currently not used by the GPU automatically freed up for programs?

Please let us know if switching to V14.5 fixes the issue.