Summary: | 17.04 - Crash on Exit | ||
---|---|---|---|
Product: | [Applications] kdenlive | Reporter: | Paul Konecny <paul> |
Component: | Video Display & Export | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
Status: | RESOLVED UPSTREAM | ||
Severity: | crash | CC: | amartyobanerjee, anton.gubarkov, bugseforuns, frederic.coiffier, freekdekruijf, jaak, jb, lingtjien, marco.castro, pajaro, paul, pranav.sharma.ama, rjvbertin, vortex |
Priority: | NOR | Keywords: | drkonqi |
Version: | git-master | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Paul Konecny
2017-04-05 15:32:37 UTC
Thanks for your report. This was fixed in a recent MLT commit: https://github.com/mltframework/mlt/commit/a3188e301b5a9a1f25dbb98a510e366363348e64 Using MLT from git or the next MLT version to be released will solve the crash Gotcha! Thanks J-B. What I don't understand is why a call is made to Render::stop() in this location, esp. when no rendering was ever done (I get the crash when I simply start and then quit Kdenlive). Am I far off the truth assuming that MLT gets "deconfigured" before the Monitor dtor is called? How about doing this sort of prepare-for-exit steps in reaction to QCoreApplication::aboutToQuit()? To answer my own question: something else appears to be going on. Even when I take down most of the MLT resources in reaction to `aboutToQuit` and in fact leave most of that to the global destruction phase (i.e. the MLT library itself) I see a crash in MLT. Yet when I revert to kdenlive 16.12.0 the issue disappears, so it should be possible to avoid the crash in kdenlive. *** Bug 379836 has been marked as a duplicate of this bug. *** *** Bug 379717 has been marked as a duplicate of this bug. *** *** Bug 378763 has been marked as a duplicate of this bug. *** *** Bug 381208 has been marked as a duplicate of this bug. *** *** Bug 381648 has been marked as a duplicate of this bug. *** *** Bug 384672 has been marked as a duplicate of this bug. *** *** Bug 387492 has been marked as a duplicate of this bug. *** *** Bug 388252 has been marked as a duplicate of this bug. *** (In reply to Jean-Baptiste Mardelle from comment #1) > Thanks for your report. This was fixed in a recent MLT commit: > https://github.com/mltframework/mlt/commit/ > a3188e301b5a9a1f25dbb98a510e366363348e64 > > Using MLT from git or the next MLT version to be released will solve the > crash What is the use if upstream won't release a new version? According to https://github.com/mltframework/mlt/releases their last release was 6.4.1 on Nov 16, 2016. Dear Kdenlive! Whatever reasons upstream has, it hurts Your users! Isn't there something You could do to work around this? |