Version 6.4.1.2 memory overflow with only one mode 9 driver

[Achimobil]

I updated to the newest version, got to the Turion and activate the BGA filling. I change to another vehicle and whole game hangs. I update from 6.4.0.8 with the hope the getcurrenthelper nil error was solved, but this is much worse. For the helper nil I will create another report.

In the log I see this:

2021-11-06 14:01 :52 [info lp11084] CLAAS TORION 1914 (#1): AI driver in mode 9 starting at 57/57 waypoints (COURSEPLAY_FIRST_POINT)
2021-11-06 14:02 Warning: Performing emergency garbage collection pass - memory went from 278671 KB to 557594 KB in less than one frame
2021-11-06 14:02 Usage is now 557568 KB; full GC took 426.142700ms
2021-11-06 14:02 Warning: Performing emergency garbage collection pass - memory went from 557568 KB to 1115166 KB in less than one frame
2021-11-06 14:02 Usage is now 1115166 KB; full GC took 735.275300ms
2021-11-06 14:02 Warning: Performing emergency garbage collection pass - memory went from 1115166 KB to 2230663 KB in less than one frame
2021-11-06 14:02 Usage is now 2230663 KB; full GC took 1076.530200ms
2021-11-06 14:02 Warning: Performing emergency garbage collection pass - memory went from 2230663 KB to 4461357 KB in less than one frame
2021-11-06 14:02 Usage is now 4461357 KB; full GC took 2049.075100ms
2021-11-06 14:02 Warning: Performing emergency garbage collection pass - memory went from 4461357 KB to 8922744 KB in less than one frame
2021-11-06 14:03 Usage is now 8922744 KB; full GC took 7458.373800ms
2021-11-06 14:04 Warning: Performing emergency garbage collection pass - memory went from 8922744 KB to 17845519 KB in less than one frame

Complete log here
log.txt

[Tensuko]

You don't need to open a report for helper nil if that is fixed in current version.

[Tensuko]

#7588

[Achimobil]

Hi Tensuko,

ich habe noch kein Ticket gemacht, weil ich mit nicht sicher bin on der helper nil fehler von courseplay kommt, von autodrive, vom VehicleInspector oder von einen der anderen mods, er war auf ein mal da und ich versuche noch das genauer zu bestimmen. Danke für das zuordnen zu dem anderen Bug, sieht gleich aus wie bei mir.
Noch als Info:
Zurück auf 6.4.0.8 und der oben geschriebene Fehler ist bei mir weg.