tag | 35aa09d40518a43cd5a9adbf385ee37bf25c3d23 | |
---|---|---|
tagger | Gergely Szell <sethyx@gmail.com> | Mon Feb 25 11:01:22 2013 +0100 |
object | f770893767331b574f05ca2520fac94c90a47fca |
jb-mr1_build-4
commit | f770893767331b574f05ca2520fac94c90a47fca | [log] [tgz] |
---|---|---|
author | Chih-Hung Chou <robert_ch_chou@acer.com.tw> | Tue Sep 18 10:38:08 2012 -0300 |
committer | Jonathan Steadman <xxwhitehawk@gmail.com> | Sun Feb 10 10:13:19 2013 -0800 |
tree | 5c7c94fafc5e40da86b16845e2ac247d29be5a79 | |
parent | 758fb6cde3ee6ab53aa6b4b07a2acc2bde0b6c5d [diff] |
fix memory leaking There is a possible memory leaking when lo is allocated but the lo->name is not. In this case, we should free the lo and then return original change I475968bd570a113c9f61f02b974d57d1caaa0236 picked from: https://android-review.googlesource.com/#/c/23450/ Change-Id: I21dd3267fa2521578d93f7b1a7bc2a6726de15ac