Crash Offsets
-
Here’s a plugin to log what’s happening with engbase at 0x124bd. Add it to dacomsrv.ini and you’ll get EXE\EngBase-0124BD-YYYY-MM-DD.hhmmss.txt (the time when the server was started). Since there’s a lot of data, I reset it every 100 calls, so there’s a slight possibility the crash will occur with no context. I also try another test for a bad address (thus preventing the crash); if it occurs, the file is renamed as *-bad_N_.txt (at least, I hope it is, didn’t actually test it).
-
Now we have sometimes 000c45a2 in content.dll - something wrong with npc, but what?
-
adoxa wrote:
That’s a really strange address for a crash - cmp dword[ecx+34], 1 when there’s mov [ecx+2c], eax a few instructions earlier.i use http://the-starport.net/freelancer/forum/viewtopic.php?post_id=31645#forumpost31645 patch but think it is of wrong encounter parameters
-
adoxa wrote:
Ah, that explains it. I did a better patch in an IM: 0C457F, 9981E2FF->7411EB05. Don’t forgot to undo the other one.Undo #34 and apply this?
-
adoxa wrote:
Ah, that explains it. I did a better patch in an IM: 0C457F, 9981E2FF->7411EB05. Don’t forgot to undo the other one.Tried on vanilla content dll without patches - crash at 000c458f
-
Sill in test - works well
-
ntdll.dll crashes - Not supported parameter or typing error, not supported/equipable archetype in players char file.
06F47BC4 - incorrect base position?
-
Those are the two offsets we get as the most frequent crash reasons. What makes me helpless is, that you can’t pinpoint a special player or NPC activity as the crashes happen randomly, some times the server runs crash free for three weeks and then crashes happen two or three times in a row. It happens with one player or ten players, in different systems and with players flying missions or simply trading.
I hope with a hint what is triggered I can get an idea where to look at.
-
Ah X) Dirty saying image base + offset
-
Here’s a new plugin for the content 124bd problem. This one only logs on a bad address (also eliminating the crash), so you should have no problem on a running server. It will generate EXE\EngBase-0124BD-bad.txt, logging the values of the previous call.
-
:Reviving stale thread…
Seeing the same 0x47bc4 error in content.dll. What’s interesting me is the idea that it’s related to NPC chatter. I can hear the NPCs chattering to each other, and when I ‘hail’ them. They seem to know who they are but most do not seem to know where they are going or where they’re from.
Every now and again I’ll get the ‘this is patrol white-1, we’re out of the tau-31 system’ or something like that, but in most cases the chatter just dead ends after the we’re out of the/ and no system or base is indicated.
Where would that info be added to the NPCs characteristics? It seems to be related to the added NPCs in the system (Order and DSE in Omicron Minor) and not elsewhere in the universe.
Also, most times you hail an NPC you get the identifier and the destination or origin points. If you want more you have to keep ‘hailing’ them. Usually within a couple hails they start getting rude, but they don’t talk to you without you hitting the hail button.
In some cases I’m experiencing a chatterbox. I’ll hail once and the response will be something like:
idenifier, (chokes just before stating origin)
then an additional choked message will also be played. Most I’ve had were three statements with one press of the hail button, all choked.
