The error you read here is pointing towards a call to pure virtual - itself very weird - but I also got segfaults.Īs per reproducing it, consider this is very random. Terminate called without an active exception 11:46:57: VERBOSE: ServerEnvironment::deactivateFarObjects(): deactivating object id=30 on inactive block (-109,0,-97)
11:46:57: INFO: Server: Stopping and waiting threads 11:46:57: INFO: Server: Saving environment metadata 11:46:57: INFO: Executing shutdown hooks 11:46:57: VERBOSE: ServerEnvironment::deactivateFarObjects(): deactivating object id=10 on inactive block (-109,0,-97) 11:46:57: VERBOSE: ServerEnvironment::deactivateFarObjects(): object id=11 is not known by clients deleting Mobs_class:mob_staticdata(): leaving, name=mobs_animal:cow Mobs_class:mob_staticdata(): pre-return, name=mobs_animal:cow Mobs_class:mob_staticdata(): entering, name=mobs_animal:cow I noticed that when a crash occurs the 'leaving' print() is missing in the console output and the server immediately starts the shutdown, as you can see here: 11:46:57: VERBOSE: ServerEnvironment::deactivateFarObjects(): deactivating object id=11 on inactive block (-109,0,-97) "." ) local tmp_ret = rialize ( tmp ) print ( "mobs_class:mob_staticdata(): leaving, name=".
In fact after changing that line as follows: print ( "mobs_class:mob_staticdata(): pre-return, name=". Went on and I added some print()'s to it: seems everything works fine until the final return ( api.lua#元026). So, I added -verbose and the resulting logs pointed me towards get_staticdata(). Forgive the long answer, but I thought its time to dive a bit more in what I have observed. Sadly, I just pulled the new mobs_redo revision and it seems the issue is still present. Hi TenPlus1, thanks for your helping in this.
0 kommentar(er)
