diff options
| author | Lorenzo Colitti <lorenzo@google.com> | 2016-03-25 17:40:11 +0900 |
|---|---|---|
| committer | Lorenzo Colitti <lorenzo@google.com> | 2016-03-28 17:33:30 +0900 |
| commit | 0ad9ab07fa0a106e55a423c837d306327045befe (patch) | |
| tree | ba36e5931980e505fb87b4fe9ca067912ea1c8d2 /tools/aapt2/java/JavaClassGenerator.cpp | |
| parent | 37127f8620188f5e04c3e0e2aeaa2c15fa8c8e2d (diff) | |
Avoid null app context in StaticApplicationContextServiceFetcher.
StaticApplicationContextServiceFetcher passes the application
context to the services it creates, but sometimes the application
context can be null. Cases we've seen so far are:
- Apps that (incorrectly) call getSystemService in
attachBaseContext. In this case the passed-in context is what
will become the application context soon afterwards.
- ActivityThread$ApplicationThread.setHttpProxy. In this case the
passed-in context is the system context.
In both of these cases the passed-in context is never freed, so
passing it in to the service will not result in a leak.
Bug: 27532714
Bug: 27502146
Bug: 27337770
Change-Id: I5971c67b0e699d1a77850be8a338a448a96ec7d7
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator.cpp')
0 files changed, 0 insertions, 0 deletions