Vort
Vort
I figured out that one of memory leaks (fast, happens during shutdown) appears at this line: https://github.com/PurpleI2P/i2pd/blob/d3b699d7cdec72e6513d7a55c711e6e21902dba4/libi2pd/Transports.cpp#L474 `m_Peers` there have size of `0xfffffffffffffff7` and it starts to call `new` function...
I noticed the same behaviour for my node. Probably it happens because of packet loss. But I think that even in such case there should be no switch to Firewalled...
Try looking at log file - maybe it will contain some hints.
@verdare, you probably encountered bug #1988. Possible solutions: adding `nettime.frompeers = false` to config file or updating to version built from latest commit (c5cab05a6b8690f3fd2442054c1475e06dc43640 at this time).
Did you added `nettime.frompeers = false` before first `[]` section of `i2pd.conf`?
You may also try clearing `netDb` and `peerProfiles` directories. NetDb is almost empty anyway at this moment.
@verdare: another idea: may it be that your OS updated OpenSSL to version 3.2? In such case, i2pd update is also needed, to latest commit.
I don't know where files are stored on macOS. But there should be subdirectories like `r0`, `r1`, `r2` with files like `routerInfo-....dat` and `profile-....txt`. Please check OpenSSL version, it is...
> Damn, so I really need to pull the latest commit? When do you estimate OpenSSL 3.2 support will make it into the release version? You can try to use...
Both SOCKS 4a and SOCKS 5 are fine for accessing internal addresses with `127.0.0.1:4447`.