RDR2_b1491.exe!sub_142B8E35C Rage error

[farsey87]

What happened?

We have currently a lot of issues with this error RDR2_b1491.exe!sub_142B8E35C and I need help to fix this.

Is there any way to see whats the issue is or how to fix it ?

I tried several Artifacts the latest or also older but i doesn't change.

Expected result

solve the issue of RDR2_b1491.exe!sub_142B8E35C

Reproduction steps

I can't reproduce it - it happens since 3-4 weeks now - since last REDM updates

RDR2_b1491.exe!sub_142B8E35C_8.zip RDR2_b1491.exe!sub_142B8E35C_7.zip RDR2_b1491.exe!sub_142B8E35C_6.zip RDR2_b1491.exe!sub_142B8E35C_5.zip RDR2_b1491.exe!sub_142B8E35C.zip RDR2_b1491.exe!sub_142B8E35C_3.zip RDR2_b1491.exe!sub_142B8E35C_4.zip

Importancy

Crash

Area(s)

RedM, FXServer, OneSync

Specific version(s)

REDM

Additional information

No response

[JackPepper]

We have the same issue with many users. With up to 200 players during primetime, the crash happened around 2.129 times within the last week. We tried several artefacts with no success. The latest artefact, 10488, made it better than others, but it still crashes a lot of people.

Here are some crash dumps with error RDR2_b1491.exe!sub_142B8E35C

CfxCrashDump_2024_10_20_06_23_39.zip CfxCrashDump_2024_10_20_05_36_21.zip CfxCrashDump_2024_10_19_22_30_10.zip CfxCrashDump_2024_10_19_21_57_22.zip CfxCrashDump_2024_10_19_20_21_47.zip

[ReformRoleplay]

Also having some issues with this same crash on the latest artifacts

CfxCrashDump_2024_10_19_00_59_35.zip CfxCrashDump_2024_10_19_01_29_04.zip CfxCrashDump_2024_10_20_03_42_29.zip

[JackPepper]

Based on observations, If you clear the cache after you get the rage error, you can connect often without having the issue again. But not always. If you do not clear your cache, you will get the problem whenever you try to connect. But I still dont know what initially triggers the issue.

[iridium-cfx]

This might be fixed in latest canary (10543), please can you check it and let me know if it's still happening?

[outsider31000]

~these were not fixed just had someone testing~ if you on canary or beta the issue is fixed

[JackPepper]

With the latest artifact, 10573, and users on Canary, we no longer have the issue!

[iridium-cfx]

Thanks, closing this issue as fixed.