[FFmpeg-devel] [External] Re: Crash in Niagara Workbench Streaming with FFmpeg 7.0.1+ (H.264 Codec) on Initial Attempts

Kumar, Rahul Rahul.Kumar8 at Honeywell.com
Tue Nov 26 16:11:41 EET 2024


I tried to stream H264 video outside Niagara(attached file) Looks like it is running there:

Can you pls guide how to capture ffmpeg crash specific logs which we are facing in Niagara?


Regards,
Rahul


-----Original Message-----
From: ffmpeg-devel <ffmpeg-devel-bounces at ffmpeg.org> On Behalf Of Frank Plowman
Sent: Friday, November 22, 2024 11:37 PM
To: ffmpeg-devel at ffmpeg.org
Subject: [External] Re: [FFmpeg-devel] Crash in Niagara Workbench Streaming with FFmpeg 7.0.1+ (H.264 Codec) on Initial Attempts

WARNING: This message has originated from an External Source. This may be a phishing email that can result in unauthorized access to Honeywell systems. Please use proper judgment and caution when opening attachments, clicking links, scanning QR codes, or responding.

On 22/11/2024 15:07, Kumar, Rahul via ffmpeg-devel wrote:
> I am experiencing a crash in Niagara Workbench when streaming video with the H.264 codec. The crash occurs during the first 3-4 attempts to initialize the stream but then stabilizes afterward. This issue started after upgrading FFmpeg from 6.0 to 7.0.1. Updating to 7.1 also did not resolve the issue.
>
> Steps to Reproduce:
> 1. Use Niagara Workbench configured with FFmpeg 7.0.1.
> 2. Attempt to stream video using the H.264 codec (MaxPro camera driver in Niagara).
> 3. Observe crashes during the first few streaming attempts.
>
> Observations:
> * FFmpeg 6.0 works without crashes.
> * Logs suggest a potential issue in memory allocation or initialization during early attempts.
> * Crash logs point to ntdll.dll, which might indicate heap corruption.
>
> Environment:
> * OS: Windows 10 Enterprise
> * Niagara Workbench Version: [Your Version]
> * FFmpeg Versions Tested: 6.0(working fine), 7.0.1(crashing),
> 7.1(crashing)
>
> Can you please suggest if any changes between FFmpeg 6.0 and 7.0.1 in the H.264 codec or JNI integration could cause this behavior? Could this be related to recently resolved issues like CVE-2024-7055 or others?
>
>
> Regards,
> Rahul Kumar,
> Honeywell

Hi Rahul,

Are you able to provide steps and/or bitstreams which reproduce this issue using FFmpeg alone and not in Niagara Workbench?  There are a number of reasons using FFmpeg 7.0.1 could crash this software which are not due to bugs in FFmpeg.  Most notably, does the software actually support FFmpeg 7?  This is a major version bump and so FFmpeg 7 is not
ABI- or API-compatible with FFmpeg 6.

All the best,
Frank

_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel at ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email ffmpeg-devel-request at ffmpeg.org with subject "unsubscribe".
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ffmpeg_7.1_h264_streaming_test_outside_niagara.txt
URL: <https://ffmpeg.org/pipermail/ffmpeg-devel/attachments/20241126/7e5b5060/attachment.txt>


More information about the ffmpeg-devel mailing list