[Internal bug 35300219]
It's possible for CronetBidirectionalStream to invoke nativeWritevData() on a destroyed stream adapter, resulting in the following crash.
0002a671 Java_org_chromium_net_impl_CronetBidirectionalStream_nativeWritevData /usr/local/google/home/xunjieli/chrome/src/out/Debug/gen/components/cronet/android/cronet_jni_headers/cronet/jni/CronetBidirectionalStream_jni.h:106
0001dbcc dvmPlatformInvoke+112 /system/lib/libdvm.so
0004e123 dvmCallJNIMethod(unsigned int const*, JValue*, Method const*, Thread*)+398 /system/lib/libdvm.so
00026fe0 <unknown> /system/lib/libdvm.so
0002dfa0 dvmMterpStd(Thread*)+76 /system/lib/libdvm.so
0002b638 dvmInterpret(Thread*, Method const*, JValue*)+184 /system/lib/libdvm.so
00060581 dvmCallMethodV(Thread*, Method const*, Object*, bool, JValue*, std::__va_list)+336 /system/lib/libdvm.so
0004c701 <unknown> /system/lib/libdvm.so
00027b5d _JNIEnv::CallVoidMethod(_jobject*, _jmethodID*, ...)
v------> Java_CronetBidirectionalStream_onWritevCompleted
Comment 1 by bugdroid1@chromium.org
, Feb 15 2017