Crash Offsets

IrateRedKite

0x00012e10 in content.dll
0x062FFBEB in common.dll

Relates to a bad NPC costume (inconsistent gender choices according to IDA) in mBases.ini. Many thanks to Laz for helping pin this one down.

DragonFire

0x0004fe6c in common.dll

CShip::Launch causes a CTD when the client and server don’t have matching base nicknames in the [Object] entry in a system INI. The client is the one that has the CTD.

Example:
Reproducible by running a vanilla v1.1 server and a JFLP v1.25 client and undocking from either Ronnenburg Base or Yanagi Depot. Client crashes immediately at undocking cutscene. If the inverse is performed, the same outcome is achieved.

Reason:
Vanilla entry for Ronnenburg is nickname = Bw02_02_Base, JFLP v1.25 entry is nickname = Bw02_02
Vanilla entry for Yanagi Depot is nickname = Bw05_03_Base, JFLP v1.25 entry is nickname = Bw05_03

Why:
FL multiplayer black magic?

IrateRedKite

Just thought I’d drop in and mention that the crash offset database is now available as a json payload through the new TSP wiki!

https://wiki.the-starport.net/wiki/fl-binaries/crash-offsets

If you have any automation or scripts that handle Freelancer when it crashes, you can call on this file to try and correlate the offset with your Windows Event logs. A working example of how you might go about doing this can be found here.

IrateRedKite

Got a new crash for a new forum! I’ve not been able to pin this one down at all:

Freelancer.exe, PID 12824 has stopped unexpectedly at 20:29:51 after running for 124.8607 seconds. Fetching crash event from Application logs... 
Source Name: Application Error
Event ID: 1000
Exception Code: 0xc0000005
Faulting Application Name: Freelancer.exe, version 0.1.1223.11, PID 12824
Faulting Application Path: C:\Users\User\AppData\Roaming\freelancer-bmod\EXE\Freelancer.exe
Faulting Module Name: ntdll.dll, version 10.0.19041.3693
Faulting Module Path: C:\Windows\SYSTEM32\ntdll.dll
Fault Offset: 0x0004591f
Attempting to fetch JSON crash information from the Starport KnowledgeBase...
No crash offset at 0x0004591f in ntdll.dll has been documented previously. Please determine the cause of the crash and submit an update to the Starport KnowledgeBase

Not been able to replicate this one reliably, which is a bit frustrating, and I’m not really sure where to start investigating as it’s a system DLL. Any ideas? Suspect it’s related to NPCs in some way, given what I was doing when this occurred.

adoxa

Could you run it in a debugger (OllyDbg, x64dbg, WinDbg)? That would enable you get a call trace and (hopefully) find where in Freelancer it called the system.

IrateRedKite

Unfortunately I’ve been unable to reliably replicate this one and haven’t been able to get the game to crash in the same area again! I’ve made a note so it should flag up the next time it occurs while I’m testing. If I can reliably get it crashing I’ll try running it with my client hooks w/ the debugger attached, and if that fails, with OllyDbg

Venemon

I have tried to keep myself out of Freelancer for a time, but I found a way to start story missions in a live server though some weird tricks, I couldnt help myself to finish this thing, in that time I have documented some crash offsets that might be useful

(If anyone wants to see how I did this, I put the source code in the Moddb website in the download link, “Freelancer Co-Op Campaign Mode”, my code is very bad but StartStory() function explains how it is done)

content.dll+1aa9f
_SendMessage (Server uses this to communicate with every function) crashes due to following reason;
if anyone calls Story mission "Act_State = SUCCEED" server will call DestroyInstance for every story instances are running, it will crash the server if there are more than 1 in action 

this can be temporarily fixed by altering the function, which prevents DestroyInstance erase Story instances (it will only stop the last instance which Co-Op mod does for 0x1 iClientID)
(BIG NOTE: this offset effects even random missions, restart the server as soon as "missions" ends)
(Another big note: Act_State = SUCCEED" function itself needs to be changed, in order to have everyone their own instances and make them successfuly finish)

content.dll+49c95
settimer assignment error, unstable instance for unknown reasons

content.dll+89651
reputation based error (happened when SP Story reputation functions are enabled in MP)

content.dll+2d541
story manager tried to submit an order/reputation to a NPC that does not exist
documented this bug at SpawnShip within initState = ACTIVE trigger

content.dll+55796
Client crashed during MP base cutscene when server shut down (crash in DestroyInstance)

content.dll+25cc9
Story trigger, Act_LockDock error?, possible nullpointer base? it might be related to other story triggers too(Previous OPjump does initilaize every trigger of story manager)

Content.dll+2FE8F
AI logic error, as far as I can tell, 3 different functions use this area, one of them controls their orders as they spawn and the other one upon destruction

Common.dll+6c282
Group formation leader error, unknown

Freelancer.exe+13d55a
Client tried to dock to a solar that does not exist from its perspective, either done through SwitchOut or following a formation leader that is docking

Freelancer.exe+1469F6
Client tried to sends its targetting information to the server, but failed (tried to target during SystemSwitchOut)

Freelancer.exe+001aad50
Based on pure speculation, Client tried to switch chars during server froze and it crashed

UNKNOWN/UNKNOWN
Observed multiple times, if a Story mission called a [Trigger] but has no Cnd_ condition line

Server.dll+f988
Client and Server failed to sync jump destination system, causes crash in Singleplayer

IrateRedKite

@Venemon Can’t stay away huh? Thanks for the contributions, I’ve added these to the crash offsets page.

josbyte

Shading.dll 0x0001014a or RP8.dll 0x00033b2f, seems like it can happen on either two.

if In the current system there is one or more objects that doesn’t have power of two size textures

IrateRedKite

@josbyte Added to the wiki, thanks for the addition

josbyte

Glad to help. another one i just had with random missions

1aa9f

It is already on the list as something related to server stuff, but this also happpens when, for example in my case, you are missing m13.ini file on a open sp. This offset has a bunch of causes but in general it is “Freelancer function that has the task to control the player status on missions had a problem , could be that it doesn’t know if the next mission is a story mission or keep the player doing random missions, or it mistakenly thinks the player is on a story mission when it isn’t”

You guys can word that better than me, hope it helps.

josbyte

8381a

Happens when a market good cost 0 credits and the games tries to calculate stuff with it on clicking it on the dealer.

IrateRedKite

@josbyte I’ve amended both of these offsets in the wiki. 8381a was actually already present as I had this when we had a file generator write ‘nan’ into the price field, so it’s any sort of invalid value here. Have updated it to make it clear that 0 isn’t an option for prices!

josbyte

0x2a397241

The npcships NPCShipArch entry is missing at faction_prop.ini on the faction that it is trying to spawn from (npc_ship = NPCShipArch nickname)

IrateRedKite

@josbyte I’ll add this to the wiki, but which dll file is the crash occurring in? My guess would be common.dll or freelancer.exe but I don’t have the time to replicate the crash at the moment

josbyte

Nombre de aplicación con errores: Freelancer.exe, versión: 1.0.1223.11, marca de tiempo: 0x3e401b79
Nombre del módulo con errores: unknown, versión: 0.0.0.0, marca de tiempo: 0x00000000
Código de excepción: 0xc0000005
Desplazamiento con errores: 0x2a397241
Id. de proceso con errores: 0x3FE4

Right! sorry, tho it says unknown, maybe it is just fl.exe itself

IrateRedKite

Curious, I’ll hold off on adding this and see if I can’t replicate the crash on a pure vanilla install and get a faulting module this afternoon. At what point does the crash occur, presumably when attempting to spawn the NPC?

josbyte

Exactly, game tries to spawn a npc which exists with their loadout and all but it is not defined as a possible spawn for the faction in faction_props.ini