I updated to version 6.34rc39 and found the dude client would no longer connect with the error "Error: Operation Failed: 10053: An established connection was aborte..."
On the CHR instance running the dude the CPU was constantly at 50% (2 cores) and the profile tool showed the causes as the dude.

I have left this for 8hours but it never became usable.

If I attempt to disable the dude (/dude set enable=no) it times out but the CPU activity does stop till I try to connect the client or reboot.

I then updated to 6.34rc41 and it was exactly the same.

I have tried uninstalling the dude package, deleting the data, reinstalling and then importing an export of the database but it does the same.
If I dont import my db export then I can connect to the dude but this is no use without my data.

I just got the exact same thing. I think i know what did it.

Everything was working ok, I was making a new function and it dropped out.

I think it was from using º in the unit? field (what ever the bottom one says).

running on x86 with 4 cpu its maxing 1 of the cpu on the router.

If possible please try generating supout file when that problem is ongoing with dude server and send it to support@mikrotik.com debug output should show what server gets so upset about.

already rebuilt it and reimported my old backup. However it just did it again, I wasn't really doing anything at the time came back to the office moved some stuff around on a network map and it died again with the same symptoms. one thing i did notice this time is the first time i try and connect to it after rebooting it i get error 10054 then it does the 10053 error continiously.

It looks like its generated its own autosupout.rif at the time it broke I'll shoot that through.

Similar thing.
After upgrade my CCR from v6.34rc34 to v6.34rc41 I also upgraded to dude-6.34rc41-tile.npk and install dude-install-6.34rc34.exe on my laptop.
Now I get:

Also And I cannot find Dude process via Profile

rc43 should should contain fix for this problem.