Skip to content
View in the app

A better way to browse. Learn more.

LCPDFR.com

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
The latest updated version of RAGE Plugin Hook, required to play LSPDFR, can be found inside the LSPDFR download. It is not currently available on the RAGE Plugin Hook website.

The game crash after 20 minutes, can someone help me please?

Featured Replies

  • Community Team

Update:

- DeadlyWeapons

- DeryllCallouts

- Immersive Ambient Events

- MCCallouts

- RiskierTrafficStops

 

Remove: 

- BetterEMS

- HighwayCallouts

- PoliceSmartRadio

- TrafficPolicer


Move: 

- InputManager

- NAudio

- RageNativeUI

from /Plugins/ to your GTA V main directory. 

I would say this is more LSPDFR crash rather than anything else.. I read both logs the first one many things were outdated and not updated but Lennyy said what needs doing, but the 2nd log

2 plugins failed to load properly due to missing required plugin attributes both files where `Newtonsoft.Json.dll` and `Venoxity.Common.dll`. This might suggest that incompatible or corrupt plugins were present, though these issues occurred prior to the crash

But further in the log there was a critical error in the `GameFiber::Main() stating "TLS no longer matches initial TLS". This repeated multiple times, indicating that the thread local storage (TLS) became inconsistent, leading to fiber shutdown issues.

This TLS mismatch error is the most likely cause of the crash, and it seems to be related to LSPDFR's handling of fibers (threads). This could be due to memory management problems, conflicts between plugins, or issues with how threads are cleaned up during shutdown.

Looking to take your projects to new heights? Look no further! At Code Master, we're not just about FiveM or GTA; we're your one-stop destination for cutting-edge web development, HTML tools, games and much more!


Kind Regards, 

CEO - SMURF @Code Master 

  • Management Team
3 hours ago, Code Master said:

But further in the log there was a critical error in the `GameFiber::Main() stating "TLS no longer matches initial TLS". This repeated multiple times, indicating that the thread local storage (TLS) became inconsistent, leading to fiber shutdown issues.

This TLS mismatch error is the most likely cause of the crash, and it seems to be related to LSPDFR's handling of fibers (threads). This could be due to memory management problems, conflicts between plugins, or issues with how threads are cleaned up during shutdown.

No, it likely has nothing to do with it here. The message is a debugging message shown after fiber shutdown (both normal and abnormal), and can be ignored by non-developers.

1 hour ago, Cyan said:

No, it likely has nothing to do with it here. The message is a debugging message shown after fiber shutdown (both normal and abnormal), and can be ignored by non-developers.

Got it, thanks for clarifying!

Looking to take your projects to new heights? Look no further! At Code Master, we're not just about FiveM or GTA; we're your one-stop destination for cutting-edge web development, HTML tools, games and much more!


Kind Regards, 

CEO - SMURF @Code Master 

  • Author

for a while worked, now crash often when i tap F4, or during a call. Sometimes it takes 20 minutes to crash, sometimes 50min/1 hour.

Edited by Lucasprata

This is a support topic.
Only reply here to offer help or assistance to Lucasprata. Off-topic or "me too" replies will be removed.

Need support yourself? Make a new topic instead.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

Recently Browsing 0

  • No registered users viewing this page.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.