RmlDocument 'removeChild' will crash alt:V client

[masterus808]

Description of the problem

Reloading client-side code with RMLDocument within that resource will cause alt:V client to crash entirely whenever the script will start to load, it is not related to any map replacement mods etc., just pure code.

Reproduction steps

restart [resource] in alt:V server console

Expected behaviour

Load resource with RMLDocument properly like before (wasn't happening before 16.3.34 (RMLUI 3D API implementation))

Additional context

[16:35:23] Downloading resource from: http://localhost:7788/core.resource
[16:35:23] Skipping integrity check for resource core
[16:35:23] Downloaded and validated resource core succesfully
[16:35:23] Finished downloading all resources
[16:35:23] Stopping resource core
[16:35:23] MINIDUMP: Temporary dump saved
[16:35:24] Last loaded asset: id2_rail_3.ybn hei_hw1_08_0.ybn
[16:35:24] Texture info: rsn_sl_fog_stream01 NoFlow
[16:35:24] Last deleted vehicle model 0000000000000000
[16:35:24] Last pos Point{ x: 389.945, y: -355.897, z: 47.4804 }
[16:35:24] Shutting down

(12/05/2025) code 'snippet' and temporary workaround

Operating system

Windows 11 (23H2 & 24H2)

Version

16.3.34 (latest release version) & 16.3.35-rc.5 (latest RC version)

Crashdump ID

99aa0539-4f0e-4c02-a76c-b9fed9ceeca1

Confirmation of issue's presence

• By submitting this ticket, I affirm that I have verified the presence of this issue on the latest RC (Release Candidate) version available at the time of writing this ticket.

[masterus808]

Additionally - this might be related to client-side RMLUI that the core resource in this case contains, it is purely 2D if that matters.

[masterus808]

Looks like 16.3.35 release update fixed that issue and it no longer crashes the client, even if that was 'fixed by mistake' - thank you!

[masterus808]

Okay, so - it seems that RMLUI cache (somewhere) is causing the crash. Closed it before because of me breaking the entire RMLUI logic on my end, which didn't cached any RMLElements or RMLDocuments on the client itself. After we managed to resolve issue that I created at the beginning, it started to crash again. Tested it with basic nametags on clean gamemode (player entity spawn -> create RMLElement inside of a created RMLDocument -> reload resource -> crash)

[masterus808]

Still outgoing on 16.3.44, any RMLDocument within an resource while it's reloading? Crash. 2D or 3D.

[masterus808]

Found a 'temporary solution' by user 'Kern Code' on alt:V Discord
This piece of code will not crash at all:

  alt.on("gameEntityDestroy", this.removeFromNametags.bind(this));

  private removeFromNametags(entity: alt.Entity): void {
      const rmlElement = this.nametags.get(entity.scriptID);
      if (!rmlElement) {
        return;
      }
  
      this.forceRemoveFromNametags(entity.scriptID, rmlElement);
    }
  
  private forceRemoveFromNametags = (id: number, rmlElement: RmlElement) => {
      rmlElement.addClass("hide");
      this.nametags.delete(id);
    };

But if we update forceRemoveFromNametags function to the previous (which was working fine before 3D RML introduction) one which was exactly this:

  private forceRemoveFromNametags = (id: number, rmlElement: RmlElement) => {
      const container = this.document.getElementByID("nametags-wrapper");
      container?.removeChild(rmlElement);
      rmlElement.destroy();
      this.nametags.delete(id);
    };

It will crash entirely, not even during reloading resource - can crash randomly when entity just despawns or will unstream. Tried different solutions (like clearing every single map from nametags by destroying and clearing every single RmlElement entity and then 'recreating' an document) but none of them works, the issue is with removeChild function which just crashes the client, no matter what. And yes, checking if the getElementById return value is valid or w/e doesn't matter, it will crash anyway.