View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0000630Cinelerra-GG[All Projects] Bugpublic2023-01-29 09:452023-02-03 15:38
Reporterfary54 Assigned ToPhyllisSmith  
PrioritynormalSeveritycrashReproducibilityalways
Status closedResolutionfixed 
PlatformX86_64OSDebianOS Version10.4
Product Version 
Target VersionFixed in Version 
Summary0000630: "Background rendering" makes the pc crash
DescriptionHello to all,

Having used the background rendering on a project of more than an hour I was surprised by the crash of my pc.
After rebooting and analysis I deduced the following:
- Having 126 Gb of ram memory I preferred to put the /tmp directory in ram rather than on the sd drive (ram being faster and thus I relieve my sd drive).
- When, in cinGG, you stop the rendering function in the background and then restart it, it does not delete the old /tmp/brender files. As a result, the ram memory keeps filling up and eventually crashes the PC.
- Because of the large number of /tmp/brender files created, it is impossible to delete them via the graphical file manager. The only possibility is to restart the pc to empty the /tmp directory.

In order to avoid a new crash or a reboot of the pc, the simplest solution I found is to add to CinGG this shell command that deletes all /tmp/brender files -> find /tmp/brender* -delete

Now, at any time, I just need to disable background rendering (MAG+G), run this shell command and then re-enable background rendering (MAG+G). If this is not clear, I can make you a video.

This is not the discovery of the year but I think it would be important to either:
- to add this shell command (or another one) directly into CinGG as I did.
- to mention it in the manual.

Of course, with my configuration, it's the memory that ends up saturated, but the result would be the same on a sd or dd drive.

Have a nice weekend.
TagsNo tags attached.

Activities

PhyllisSmith

PhyllisSmith

2023-02-03 15:38

manager   ~0005393

Done.
fary54

fary54

2023-02-01 07:11

reporter   ~0005386

@PhyllisSmith
Ok, well noted.
Many thanks for your efficiency.
PhyllisSmith

PhyllisSmith

2023-02-01 00:20

manager   ~0005385

@fary54
Your recommended solution is in this month's AppImage release. As noted in the releasenotes.pdf, it will only show up for new usage of CinGG so as not to destroy any shell scripts a user may have added to his own usage (seen in $HOME/.bcast5/Cinelerra_rc). But you can test this if you download the latest AppImage without impacting your settings by typing in a terminal window:
    CIN_CONFIG=/tmp/bcast1 /location_of_your.AppImage
You will see when you click on the Shell Commands, a new one on the end "Delete brender files in tmp".
fary54

fary54

2023-01-30 07:05

reporter   ~0005382

Phyllis Smith,

Thank you for your quick response.
I remain at your disposal in case of need or additional information.
PhyllisSmith

PhyllisSmith

2023-01-29 23:19

manager   ~0005381

Good idea. I am working on adding a Shell script to do this.

Issue History

Date Modified Username Field Change
2023-01-29 09:45 fary54 New Issue
2023-01-29 23:19 PhyllisSmith Note Added: 0005381
2023-01-30 07:05 fary54 Note Added: 0005382
2023-01-30 16:47 PhyllisSmith Assigned To => PhyllisSmith
2023-01-30 16:47 PhyllisSmith Status new => acknowledged
2023-02-01 00:20 PhyllisSmith Note Added: 0005385
2023-02-01 07:11 fary54 Note Added: 0005386
2023-02-01 16:32 PhyllisSmith Status acknowledged => resolved
2023-02-01 16:32 PhyllisSmith Resolution open => fixed
2023-02-03 15:38 PhyllisSmith Status resolved => closed
2023-02-03 15:38 PhyllisSmith Note Added: 0005393