Find at least "5" (there are more) raw memory leaks due to missing or mis-handled implementation
Created by: anonimal
Easter-egg hunt in January?
21:15:06 zzz | for your todo list: <orignal> there are approcimately 5 more places sending raw memory 21:48:55 str4d | <orignal> they are all marked with TODO: <-- raw memory locations (I assume he means padding)
Note: focus on any
TODO's, especially those marked with
Note: regarding the time-frame to complete d649e8ae in #165:
- I was waiting for #140 to be resolved but, in our meetings, we eventually agreed to not wait any longer and pursue a patch instead
- I wanted to focus on finishing #149 (closed) before flipping branches and committing d649e8ae. This could have easily gone the other way but, since we are not in production, and the leak is actually not raw (it is initialized, just not with random padding as java i2p specifies), I chose to focus on the bigger work involved in #149 (closed) and, once completed, resolve this ticket.