Bug#831591: ffmpeg: kodi crash

Hi Andreas, 2016-11-03 23:06 GMT+01:00 Andreas Cadhalpun : > Hi Bálint, > > On 03.11.2016 13:00, Bálint Réczey wrote: >> 2016-11-03 12:54 GMT+01:00 Balint Reczey : >>> Thank you for the triaging and extensive description of the problem.

Bug#831591: ffmpeg: kodi crash

Hi Bálint, On 03.11.2016 13:00, Bálint Réczey wrote: > 2016-11-03 12:54 GMT+01:00 Balint Reczey : >> Thank you for the triaging and extensive description of the problem. >> I have now forwarded the patch to upstream under your name since I did >> not really add anything to

Bug#831591: ffmpeg: kodi crash

2016-11-03 12:54 GMT+01:00 Balint Reczey : ... > On Fri, 14 Oct 2016 01:27:47 +0200 Andreas Cadhalpun > wrote: > ... > >> >> Hi, >> >> The relevant backtrace from the kodi_crashlog is: ... >> In the experimental kodi branch there is

Bug#831591: ffmpeg: kodi crash

Control: forwarded -1 https://github.com/xbmc/xbmc/pull/10846 Control: tags -1 upstream Hi Andreas, On Fri, 14 Oct 2016 01:27:47 +0200 Andreas Cadhalpun wrote: ... > > Hi, > > The relevant backtrace from the kodi_crashlog is: > > Thread 1 (Thread

Bug#831591: ffmpeg: kodi crash

Control: reopen -1 Control: reassign -1 kodi 16.1+dfsg1-2 Control: severity -1 important Hi, The relevant backtrace from the kodi_crashlog is: Thread 1 (Thread 0x7f1b6bffe700 (LWP 16893)): #0 0x7f1ba92991c8 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 #1

Bug#831591: ffmpeg: kodi crash

Control: fixed -1 7:3.1.3-1 Hi Carl, 2016-09-07 20:21 GMT+02:00 Carl Eugen Hoyos : > Hi Bálint! > >> I went throught the unclassified bugs and set the >> proper state to help tracking them. > > This bug (#831591) and #832364 contain neither backtrace > nor bisect. Note that

Bug#831591: ffmpeg: kodi crash

Hi Bálint! > I went throught the unclassified bugs and set the > proper state to help tracking them. This bug (#831591) and #832364 contain neither backtrace nor bisect. Note that they most likely have to be fixed in Kodi, FFmpeg will (afaict) not break ABI once more for the 3.1 release

Bug#831591: ffmpeg: kodi crash

Hi Carl, 2016-09-06 12:41 GMT+02:00 Carl Eugen Hoyos : > Hi! > >> Knowing what broke could be >> interesting for FFmpeg devs > > It would most likely be even more interesting > for the Kodi developers: We currently assume > that there is an unknown bug in Kodi... Well, the

Bug#831591: ffmpeg: kodi crash

Hi! > Knowing what broke could be > interesting for FFmpeg devs It would most likely be even more interesting for the Kodi developers: We currently assume that there is an unknown bug in Kodi... > > Slightly related: More that half of the open tickets > > concerning FFmpeg in Debian either

Bug#831591: ffmpeg: kodi crash

Hi Carl, 2016-09-06 11:39 GMT+02:00 Carl Eugen Hoyos : > Hi Bálint! > >> I don't have the test file. > > In this case I suggest to close the relevant tickets: > We cannot reproduce, there is no backtrace and no bisect. Tobias has test files as he wrote in #832364 and he would

Bug#831591: ffmpeg: kodi crash

Hi Bálint! > I don't have the test file. In this case I suggest to close the relevant tickets: We cannot reproduce, there is no backtrace and no bisect. Since FFmpeg has made three point releases with the ABI that is apparently incompatible with (old) Kodi, it is very unlikely that it will be

Bug#831591: ffmpeg: kodi crash

Hi, 2016-08-27 15:48 GMT+02:00 Carl Eugen Hoyos : > Hi! > >> 2016-08-24 22:55 GMT+02:00 Carl Eugen Hoyos : >> > >> > First, please understand that so far, no ABI breakage between >> > FFmpeg 3.0 and FFmpeg 3.1 was found, only the usage of >> > non-public api

Bug#831591: ffmpeg: kodi crash

Hi! > 2016-08-24 22:55 GMT+02:00 Carl Eugen Hoyos : > > > > First, please understand that so far, no ABI breakage between > > FFmpeg 3.0 and FFmpeg 3.1 was found, only the usage of > > non-public api (that we decided to work-around for 3.1.1). > > OK, then assume that Kodi uses

Bug#831591: ffmpeg: kodi crash

Hi Carl, 2016-08-24 22:55 GMT+02:00 Carl Eugen Hoyos : > Hi! > > First, please understand that so far, no ABI breakage between > FFmpeg 3.0 and FFmpeg 3.1 was found, only the usage of > non-public api (that we decided to work-around for 3.1.1). OK, then assume that Kodi uses

Bug#831591: ffmpeg: kodi crash

Hi! First, please understand that so far, no ABI breakage between FFmpeg 3.0 and FFmpeg 3.1 was found, only the usage of non-public api (that we decided to work-around for 3.1.1). Am I correct that no backtrace was provided for this issue? But even with a backtrace, I fear a bisect may be

Bug#831591: ffmpeg: kodi crash

Hi, 2016-08-18 17:59 GMT+02:00 Bálint Réczey : > Hi, > > 2016-07-17 23:17 GMT+02:00 Sebastian Ramacher : >> Control: severity -1 serious >> >> On 2016-07-17 21:38:13, Carl Eugen Hoyos wrote: >>> Kodi reports "FFmpeg version: 3.0.1-3": >>> Could

Bug#831591: ffmpeg: kodi crash

Hi, 2016-07-17 23:17 GMT+02:00 Sebastian Ramacher : > Control: severity -1 serious > > On 2016-07-17 21:38:13, Carl Eugen Hoyos wrote: >> Kodi reports "FFmpeg version: 3.0.1-3": >> Could somebody test if the crash disappears after Kodi gets recompiled >> against >> current

Bug#831591: ffmpeg: kodi crash

Control: severity -1 serious On 2016-07-17 21:38:13, Carl Eugen Hoyos wrote: > Kodi reports "FFmpeg version: 3.0.1-3": > Could somebody test if the crash disappears after Kodi gets recompiled > against > current FFmpeg? Wasn't 3.1.1 supposed to revert all the ABI breakage? Raising the severity

Bug#831591: ffmpeg: kodi crash

Kodi reports "FFmpeg version: 3.0.1-3": Could somebody test if the crash disappears after Kodi gets recompiled against current FFmpeg?

Bug#831591: ffmpeg: kodi crash

On Sun, Jul 17, 2016 at 05:30:40PM +0300, Vladmimir Stavrinov wrote: > It happens with 7:3.1.1-2 - see attached log. With 7:3.0.2-4 there P.S. kodi crashes on acestream only. ### Vladimir Stavrinov ###

Bug#831591: ffmpeg: kodi crash

Package: ffmpeg Version: 7:3.1.1-2 Severity: normal It happens with 7:3.1.1-2 - see attached log. With 7:3.0.2-4 there are no such problem. -- System Information: Debian Release: stretch/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'),