please, stop ranting about deleted posts, if your writing does not comply with forum rules - they will get deleted.
but that is not my point. My point is - carefully describe situation how your OSPF node crashes. monitor it between crashes. more info you give to MT faster they can reproduce the problem faster devs can start to fix it and most probably they can fix faster as they have information on what circumstances OSPF crashes.
synthetic pre-release tests cannot reveal all the bugs OSPF might have. so if you see that something is wrong or not working as written in RFC try to see if there are some circumstances when problem reproduce itself.
so steps to perform:
1) install newest RouterOS version, other way all the complaints will be rejected by devs as - this is old version
2) try to check if everything is ok with configuration (double check everything)
3) try to reproduce the bug if you succeed write down how you done that.
4) make shure that following these steps you get at least close to crash
5) after crash create supout.rif file and send it to support at mikrotik.com
6) if you think that you should post your finding in forums, so other people here get to know and check if they have time to fiddle around.
forgot to add - all changes will go into routing-test if taking about v.2.9 if 3.0beta, changes will go into routing
So I ran into OSPF troubles, too. One of my 2.9.43 Routers looses all of it's neighbors
and found it again after rebooting. I enabled/disabled an IP before I noticed the problem
so it might be due to this. But simple enabling/disabling the IP do not reproduce the
problem. The enabled/disabled IP was not within the configured OSPF Network.
I followed all your steps. Let's see if it helps
So yes: OSPF is not stable. Even 2.9.43 routing-test is not production quality
in my eyes.
May be mt-support finds the problem on my side than I will post here to correct
this statement. But I hope to see 2.9.44 with a rock solid OSPF.