Vort
Vort
I've found where main bug is located. Here is how to fix it: https://github.com/Vort/vain/commit/370d8db260db1f01918591c9f417c467a3b9a54a. But there may be more bugs of course.
In case anyone interested, I published CPU generator with my modifications here: https://github.com/Vort/vain
> If the build used a pure makefile There are two parallel build systems. One of which is pure makefile. If I'm not wrong of course.
I suggest you to shut down node, delete peerProfiles folder and start node again. > I wonder if this is normal This is side effect of ongoing attack.
Yes, network is under attack. There were several waves of spreading fake floodfills routerinfos. That what lots of peerprofiles means. They describe fake nodes.
They are cleared automatically. But in case of attack there are just too many of them.
@SilmorSenedlen that RAM consumption is a big problem. But I don't know how to track down why it happens. From my experience, it can happen because of lags. Something somewhere...
For Windows, here: https://github.com/PurpleI2P/i2pd/actions/workflows/build-windows.yml https://github.com/PurpleI2P/i2pd/actions/runs/4903844731 https://github.com/PurpleI2P/i2pd/suites/12722999303/artifacts/683318292
Commit with changes around this place: c215f2e8d19f07b95163fdfecd974fa5eec2dce1. Maybe fixes this bug, maybe not.
c215f2e8d19f07b95163fdfecd974fa5eec2dce1 **not** fixes this bug. Iterator itself gets corrupted - crash happens before `.second` can be checked: 