Re:A Closer Look at Android RunTime in Android L
by agumonkey on Monday November 10, 2014 @04:28AM
(#8582677)
Memory management is obscure. `malloc` isn't free either, and gc has been shown to allow some 'out-of-order' benefits. It's a different way of thinking altogether. Right now libart's AOT makes launching overhead very small and tight loops faster but sometimes it introduces lags that I didn't have under Dalvik.
[ Parent
| on HN ]
Re:A Closer Look at Android RunTime in Android L
by sz4kerto on Monday November 10, 2014 @04:45AM
(#8582713)
> `malloc` isn't free
I see what you did there. :)
Re:A Closer Look at Android RunTime in Android L
by agumonkey on Monday November 10, 2014 @05:19AM
(#8582791)
Ha. I wish, but it was too early in the morning for me to generate such puns.
Re:A Closer Look at Android RunTime in Android L
by wabbawabbe on Monday November 10, 2014 @05:52AM
(#8582878)
What's the pun ?
Re:A Closer Look at Android RunTime in Android L
by jimktrains2 on Monday November 10, 2014 @06:30AM
(#8582990)
free() is the "counterpart" to malloc(). malloc() lets you allocate memory for your use; free() returns that memory back to the system.
The original posters meaning was that "malloc() has non-trivial execution costs", but the other meaning is, tautologically, malloc is the "complement" of free (think true is not false).