Builder ffmpeg64-solaris10-i386 Build #12789

Results:

Failed shell_2 shell_3 shell_4 shell_5

SourceStamp:

BuildSlave:

Reason:

The SingleBranchScheduler scheduler named 'schedule-ffmpeg64-solaris10-i386' triggered this build

Steps and Logfiles:

1. git update ( 5 secs )
   1. stdio
2. shell 'gsed -i ...' ( 0 secs )
   1. stdio
3. shell_1 'gsed -i ...' ( 0 secs )
   1. stdio
4. shell_2 'gsed -i ...' failed ( 1 secs )
   1. stdio
5. shell_3 './configure --samples="../../../ffmpeg/fate-suite" ...' failed ( 8 secs )
   1. stdio
   2. config.log
6. shell_4 'gmake fate-rsync' failed ( 0 secs )
   1. stdio
7. shell_5 '../../../ffmpeg/fate.sh ../../../ffmpeg/fate_config_64.sh' failed ( 0 secs )
   1. stdio
   2. configure.log
   3. compile.log
   4. test.log

Build Properties:

Forced Build Properties:

Responsible Users:

1. Frank Plowman

   postohnoyoudont@frankplowman.com

Timing:

All Changes:

:

1. Change #249729

   Category	ffmpeg
   Changed by	Frank Plowman <postohnoyoudont@frankplowman.com>
   Changed at	Mon 24 Nov 2025 06:08:58
   Repository	https://git.ffmpeg.org/ffmpeg.git
   Project	ffmpeg
   Branch	master
   Revision	76827a6f3bdc908a52b6f534c5b668e8e5f781b9

   Comments

   lavc/hevc: Fix usage of slice segment in invalid state
   Previously, we set s->slice_initialized to 0 to prevent other slice
   segments from depending on this slice segment only if hls_slice_header
   failed.  If decode_slice fails for some other reason, however, before
   decode_slice_data is called to bring the context back into a consistent
   state, then slices could depend on this slice segment while it is in an
   invalid state.  This can cause segmentation faults and other sorts of
   nastiness.  Patch fixes this by always setting s->slice_initialized to 0
   while the state is inconsistent.
   
   Resolves #11652.

   Changed files

   • libavcodec/hevc/hevcdec.c