From 4ad32fe2dc7b27adc7a811223c2dc2bdf9e50afb Mon Sep 17 00:00:00 2001 From: zachh Date: Thu, 13 Jul 2017 16:22:50 -0700 Subject: Use a shared thread pool for spam transport. Before, we were creating a custom thread pool for spam transport, which isn't necessary. Instead, we can just use an application wide thread pool. Also fixed some instances where we were not clearing the thread stats tag after opening the socket. Test: manually launched app with data cleared and observed no crash PiperOrigin-RevId: 161882076 Change-Id: I39bdd31cf5fa8a974d7535e861ec0716c85986f3 --- java/com/android/voicemail/impl/mail/MailTransport.java | 2 ++ 1 file changed, 2 insertions(+) (limited to 'java/com/android/voicemail') diff --git a/java/com/android/voicemail/impl/mail/MailTransport.java b/java/com/android/voicemail/impl/mail/MailTransport.java index 00339f03d..c35e41450 100644 --- a/java/com/android/voicemail/impl/mail/MailTransport.java +++ b/java/com/android/voicemail/impl/mail/MailTransport.java @@ -195,6 +195,8 @@ public class MailTransport { } catch (IOException ioe) { LogUtils.d(TAG, ioe.toString()); throw new MessagingException(MessagingException.IOERROR, ioe.toString()); + } finally { + TrafficStats.clearThreadStatsTag(); } } -- cgit v1.2.3