| Summary: | Kdenlive 24 less stable than 22.12 on my laptop | ||
|---|---|---|---|
| Product: | [Applications] kdenlive | Reporter: | gertrudedu12 |
| Component: | Rendering & Export | Assignee: | Jean-Baptiste Mardelle <jb> |
| Status: | CONFIRMED --- | ||
| Severity: | crash | CC: | berndmj |
| Priority: | NOR | Keywords: | triaged |
| Version First Reported In: | 24.12.0 | ||
| Target Milestone: | --- | ||
| Platform: | Mint (Debian based) | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | Screenshot of error | ||
What does the message say in the amber box in your screenshot? Something along the lines of less than 100MB of RAM available? Editing video and rendering it is a very memory intensive process, in particular when dealing with 4K sources. How much RAM do you have, what is the size of your SSD (or HDD), and how much swap space have you allocated? I suspect the errors you listed are red herrings, and the main reason for failing to finish the render is lack of RAM. Admittedly, Kdenlive is suffering from bad memory management with known memory leaks. (In reply to Bernd from comment #1) > What does the message say in the amber box in your screenshot? Something > along the lines of less than 100MB of RAM available? > > Editing video and rendering it is a very memory intensive process, in > particular when dealing with 4K sources. How much RAM do you have, what is > the size of your SSD (or HDD), and how much swap space have you allocated? > > I suspect the errors you listed are red herrings, and the main reason for > failing to finish the render is lack of RAM. Admittedly, Kdenlive is > suffering from bad memory management with known memory leaks. Thanks you for the answer ! I have 16gb of ram. What can be the explanation that is working well with Kdenlive 22 and not 24 ? I forgot to say too that when i do the rendering with Kdenlive 24, the ventilation start very strong then stop after few minutes at the same time of render. My SSD is a 500go and i have 120go free. For the allocated swap space, i don't know exactly what it is. Thanks you Hi, i just come back to say that i check and my swap is 2go. (In reply to gertrudedu12 from comment #3) > Hi, i just come back to say that i check and my swap is 2go. Assuming "2go" means 2GB like all the other specs you gave (so, GB in French is "go"?) I suggest to up this to at least half your RAM size, in your case that would be 8GB. If you can afford the space, go even as high as 16GB for your swap size. But since you said this never happened in release 22, I need to refer to Jean-Baptiste to look into this further. (In reply to Bernd from comment #4) > (In reply to gertrudedu12 from comment #3) > > Hi, i just come back to say that i check and my swap is 2go. > > Assuming "2go" means 2GB like all the other specs you gave (so, GB in French > is "go"?) I suggest to up this to at least half your RAM size, in your case > that would be 8GB. If you can afford the space, go even as high as 16GB for > your swap size. > > But since you said this never happened in release 22, I need to refer to > Jean-Baptiste to look into this further. Yes Go for GigaOctet, haha I just try to change to 8gb and try to start a render and its look working, i will see in the time how it will be. Thanks you to tell me about the swap size cause i never heard about that. |
Created attachment 176861 [details] Screenshot of error First of all, i'm on Linux Mint 21.3 using the appimage. My computer is a Hp Pavilion with Nvidia GTX 1650 Ti and my processor is Intel© Core™ i5-10300H CPU @ 2.50GHz × 4. The fact is that is impossible to make render using Kdenlive 24.08 or 24.12, it's always get stuck at one point for long video. The only solution is to make part by part, then to import it to kdenlive 22.12 to use it and like that it's work. It Is for 4k rendering. So you can imagin that i stop to use the Kdenlive 24 cause it's a big loose of time. I try the new version today and the problem is still the same. I have the impression that the 24 version crash more often than the 22 when i'm editing too. Do you have an idea of how to solve the problem ? Maybe i didn"t configure it good I just put the screen of the error message, i did the same render with Kdenlive 22 and it's worked great. Here is the full error : Le rendu de /home/lilian/Vidéos/message erreur.mp4 a été interrompu par une erreur fatale qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile qt.svg: /home/lilian/Vidéos/Vlog/1er decembre/Illus/Carte/Langues_de_la_France.svg:281:871: Could not add child element to parent element because the types are incorrect. qt.svg: /home/lilian/Vidéos/Vlog/1er decembre/Illus/Carte/Langues_de_la_France.svg:282:856: Could not add child element to parent element because the types are incorrect. qt.svg: /home/lilian/Vidéos/Vlog/1er decembre/Illus/Carte/Langues_de_la_France.svg:283:788: Could not add child element to parent element because the types are incorrect. qt.svg: /home/lilian/Vidéos/Vlog/1er decembre/Illus/Carte/Langues_de_la_France.svg:284:843: Could not add child element to parent element because the types are incorrect. qt.svg: /home/lilian/Vidéos/Vlog/1er decembre/Illus/Carte/Langues_de_la_France.svg:285:830: Could not add child element to parent element because the types are incorrect. qt.svg: /home/lilian/Vidéos/Vlog/1er decembre/Illus/Carte/Langues_de_la_France.svg:286:788: Could not add child element to parent element because the types are incorrect. qt.svg: /home/lilian/Vidéos/Vlog/1er decembre/Illus/Carte/Langues_de_la_France.svg:287:843: Could not add child element to parent element because the types are incorrect. qt.svg: /home/lilian/Vidéos/Vlog/1er decembre/Illus/Carte/Langues_de_la_France.svg:288:843: Could not add child element to parent element because the types are incorrect. qt.svg: /home/lilian/Vidéos/Vlog/1er decembre/Illus/Carte/Langues_de_la_France.svg:289:840: Could not add child element to parent element because the types are incorrect. qt.svg: /home/lilian/Vidéos/Vlog/1er decembre/Illus/Carte/Langues_de_la_France.svg:290:840: Could not add child element to parent element because the types are incorrect. qt.svg: /home/lilian/Vidéos/Vlog/1er decembre/Illus/Carte/Langues_de_la_France.svg:291:843: Could not add child element to parent element because the types are incorrect. qt.svg: /home/lilian/Vidéos/Vlog/1er decembre/Illus/Carte/Langues_de_la_France.svg:292:843: Could not add child element to parent element because the types are incorrect. qt.svg: /home/lilian/Vidéos/Vlog/1er decembre/Illus/Carte/Langues_de_la_France.svg:293:843: Could not add child element to parent element because the types are incorrect. qt.svg: /home/lilian/Vidéos/Vlog/1er decembre/Illus/Carte/Langues_de_la_France.svg:294:836: Could not add child element to parent element because the types are incorrect. qt.svg: /home/lilian/Vidéos/Vlog/1er decembre/Illus/Carte/Langues_de_la_France.svg:294:1279: Could not add child element to parent element because the types are incorrect. qt.svg: /home/lilian/Vidéos/Vlog/1er decembre/Illus/Carte/Langues_de_la_France.svg:295:824: Could not add child element to parent element because the types are incorrect. qt.svg: /home/lilian/Vidéos/Vlog/1er decembre/Illus/Carte/Langues_de_la_France.svg:296:843: Could not add child element to parent element because the types are incorrect. qt.svg: /home/lilian/Vidéos/Vlog/1er decembre/Illus/Carte/Langues_de_la_France.svg:297:850: Could not add child element to parent element because the types are incorrect. qt.svg: /home/lilian/Vidéos/Vlog/1er decembre/Illus/Carte/Langues_de_la_France.svg:320:843: Could not add child element to parent element because the types are incorrect. qt.svg.draw: The requested buffer size is too big, ignoring qt.svg.draw: The requested buffer size is too big, ignoring qt.svg.draw: The requested buffer size is too big, ignoring qt.svg.draw: The requested buffer size is too big, ignoring [mp3 @ 0x3de6000] Estimating duration from bitrate, this may be inaccurate [mp3 @ 0x3ddfe40] Estimating duration from bitrate, this may be inaccurate [in @ 0x7f7af80ed900] Changing video frame properties on the fly is not supported by all filters. [in @ 0x7f7af80ed900] filter context - w: 3840 h: 2160 fmt: 1 csp: unknown range: unknown, incoming frame - w: 3840 h: 2160 fmt: 1 csp: bt709 range: tv pts_time: 0 [in @ 0x7f7a46493b00] Changing video frame properties on the fly is not supported by all filters. [in @ 0x7f7a46493b00] filter context - w: 3840 h: 2160 fmt: 26 csp: unknown range: unknown, incoming frame - w: 3840 h: 2160 fmt: 26 csp: bt709 range: tv pts_time: 8.84 [in @ 0x7f7a46473a40] Changing video frame properties on the fly is not supported by all filters. [in @ 0x7f7a46473a40] filter context - w: 3840 h: 2160 fmt: 26 csp: unknown range: unknown, incoming frame - w: 3840 h: 2160 fmt: 26 csp: bt709 range: tv pts_time: 9.12 [in @ 0x7f775f8c0780] Changing video frame properties on the fly is not supported by all filters. [in @ 0x7f775f8c0780] filter context - w: 3840 h: 2160 fmt: 26 csp: unknown range: unknown, incoming frame - w: 3840 h: 2160 fmt: 26 csp: bt709 range: tv pts_time: 117.36