Bug 397108 - GPU crash when setting the needle
Summary: GPU crash when setting the needle
Status: RESOLVED DUPLICATE of bug 380019
Alias: None
Product: kdenlive
Classification: Applications
Component: User Interface (show other bugs)
Version: 18.04.3
Platform: Manjaro Linux
: NOR crash
Target Milestone: ---
Assignee: Jean-Baptiste Mardelle
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-08-02 20:52 UTC by Mateus Seenem Tavares
Modified: 2018-11-10 14:19 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
fritzibaby: MOVIT+


Attachments
kde error didnt sent (19.82 KB, text/plain)
2018-08-02 20:52 UTC, Mateus Seenem Tavares
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mateus Seenem Tavares 2018-08-02 20:52:06 UTC
Created attachment 114277 [details]
kde error didnt sent

-- Information about the crash:
- What I was doing when the application crashed:
Changing the needle position

- Unusual behavior I noticed:
If I save at every or almost every modification, i can use with speed kdenlive
running without primusrun (to run with my dedicated video board (nvidia 950m)) it is pretty stable, but already face almost same thing with videos encoded diferent, so, maybe is the way it handles the files, and with the ones more heavy it will crash sooner than latter, even without gpu

- Custom settings of the application:
primusrun kdenlive

The crash can be reproduced every time.

The reporter indicates this bug may be a duplicate of or related to bug 392902.

Possible duplicates by query: bug 392902.
Comment 1 emohr 2018-08-06 16:18:23 UTC
I’m not sure but change in the timeline window, top left from “High Quality” to “none” and try again.
This changes the render from QT to MLT.
Comment 2 Mateus Seenem Tavares 2018-08-06 20:21:28 UTC
hm, gonna tried that, but after disabling gpu aceleration(moovit) it comes back normal.
Comment 3 emohr 2018-11-10 14:19:35 UTC
Unfortunately MOVIT (GPU effects) is not stable and not ready for production use.

*** This bug has been marked as a duplicate of bug 380019 ***