View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0006039||Multi Theft Auto : San Andreas||Client||public||2011-04-12 21:52||2011-04-27 15:15|
|Target Version||1.1||Fixed in Version||1.1|
|Summary||0006039: Crash when restarting a resource and crashes when joining from then on|
In the past few days this has happened on two different occasions when editing resources (the only similarity I believe between the two occurences were the use of exported functions)
Restart resource --> crash
Version = 1.1-unstable-2516.0.000
EAX=00000043 EBX=09710697 ECX=7FFFFFFE EDX=00000073 ESI=00000000
|Tags||No tags attached.|
I got round all the crashes by stopping every resource then starting them one by one until the game crashed. I stopped the offending resource, all it really did was call customblips and create a bunch of customblips.
So I started customblips and then started the offending resource and it didn't crash. Restarting the server and then joining will again cause the crashes, perhaps it is to do with the ordering in mtaserver.conf? I have now tested this and confirm that it is related to the order in which resources are being started.
I don't believe this ordering has ever been a problem before, some change between 1.0.4 and 1.0.5 made resources start at slightly different times during startup because I've always got a bunch of errors (like teams not existing because the resource that creates them are started miliseconds after) when I first start the server, this change could be root cause of this crash and maybe some other problems too like those initial errors in scripts.
I am testing a script which uses an exported function to draw some dx text. Almost every time I restart it to test the changes it either crashes first time or says something like "bad resource pointer @ call k" or "bad resource pointer @ call (null) then the second time calling the export it will crash.
If the crash reporter is sending out those crash dumps there should be about 10 from me from the past few hours.
Possible fix in http://code.google.com/p/mtasa-blue/source/detail?r=2618
Doesn't crash now.