We have solved a huge memory issue in the new version of SolarSeek. Now we can move forward and release something very soon.

The memory issue was caused by some garbage sent by a peer just before closing the network socket. This could lead to a large message (MiBs) and we were allocating all required memory before reading the entire message. Now we’re allocating just 512bytes per message (this value is fine for almost all messages, except RoomList and SearchResults. The NSMutableData/SoulSeekMessage can grow up when necessary) and reusing some NSMutableData very often, avoiding stressing the Garbage Collector.