[GH-ISSUE #2604] [APP BUG]: ORBIS_VIDEODEC2_ERROR_STRUCT_SIZE does not give out a proper error #852

New issue

Closed

opened 2026-02-27 21:08:30 +03:00 by kerem · 2 comments

kerem commented

2026-02-27 21:08:30 +03:00

Owner

Originally created by @Hasster1 on GitHub (Mar 6, 2025).
Original GitHub issue: https://github.com/shadps4-emu/shadPS4/issues/2604

Checklist

I have searched for a similar issue in this repository and did not find one.
I am using an official build obtained from releases or updated one of those builds using its in-app updater.

Describe the Bug

The error code ORBIS_VIDEODEC2_ERROR_STRUCT_SIZE is being triggered by Five Nights At Freddy's Security Breach (CUSA24172) in videodec2.cpp (sceVideodec2GetPictureInfo, currently at line 168) when trying to decode an mp4 video.

Emulator crashes with seemingly no errors

shad_log.txt

Reproduction Steps

Trigger that error code.

Expected Behavior

Error should be shown in the log.

Specify OS Version

Windows 10

Originally created by @Hasster1 on GitHub (Mar 6, 2025). Original GitHub issue: https://github.com/shadps4-emu/shadPS4/issues/2604 ### Checklist - [x] I have searched for a similar issue in this repository and did not find one. - [x] I am using an official build obtained from [releases](https://github.com/shadps4-emu/shadPS4/releases) or updated one of those builds using its in-app updater. ### Describe the Bug The error code ORBIS_VIDEODEC2_ERROR_STRUCT_SIZE is being triggered by Five Nights At Freddy's Security Breach (CUSA24172) in videodec2.cpp (sceVideodec2GetPictureInfo, currently at line 168) when trying to decode an mp4 video. Emulator crashes with seemingly no errors ![Image](https://github.com/user-attachments/assets/cbc18b1f-ea48-4379-ba6c-508c9d2bbc4a) [shad_log.txt](https://github.com/user-attachments/files/19101205/shad_log.txt) ### Reproduction Steps Trigger that error code. ### Expected Behavior Error should be shown in the log. ### Specify OS Version Windows 10

kerem closed this issue

2026-02-27 21:08:31 +03:00

kerem commented

2026-02-27 21:08:31 +03:00

Author

Owner

@thecatontheceiling commented on GitHub (Mar 6, 2025):

Have you made sure the log type is set to sync? I think that can affect things like this

@thecatontheceiling commented on GitHub (Mar 6, 2025): Have you made sure the log type is set to sync? I think that can affect things like this

kerem commented

2026-02-27 21:08:31 +03:00

Author

Owner

@Hasster1 commented on GitHub (Mar 6, 2025):

Have you made sure the log type is set to sync?

I've tried with both sync and not, it doesn't really help.

On another note, i just realized that it might just be an internal ps4 code, and the actual error should just be logged beside that return function... Is that right?

@Hasster1 commented on GitHub (Mar 6, 2025): > Have you made sure the log type is set to sync? I've tried with both sync and not, it doesn't really help. On another note, i just realized that it might just be an internal ps4 code, and the actual error should just be logged beside that return function... Is that right?

kerem referenced this issue

2026-02-27 21:14:01 +03:00

[PR #852] [MERGED] cpu_patches: Patch just-in-time using signal handlers. #1806