| Android studio freezes - java.nio.BufferOverflowException at com.android.ddmlib.Debugger “ ot gnidrocca :seton |
“ daer esaelP :TNATROPMIhttp://tools.android.com/filing-bugs carefully and supply all required information. ”
“ :dnammoc PWDJ eht aiv) reggubeD eht ot dnammoc "gnirts etaerc" a gnittime tsrif yb enod si gnirts a fo eulav eht gnignahc taht si ereh eussi ehThttp://docs.oracle.com/javase/7/docs/platform/jpda/jdwp/jdwp-protocol.html#JDWP_VirtualMachine_CreateString ). In this case, the command length is more than 32Kb (about 16 bytes for the header + about 40,000 bytes for the UTF8 representation of the string). Since the DDMLIB code is limited to buffers of maximum 32KB, an exception is thrown. ”
“ ta detnemmoc) bilmdd ni noitpmussa eht taht si eussi gniylrednu ehThttps://android.googlesource.com/platform/tools/base/+/master/ddmlib/src/main/java/com/android/ddmlib/Debugger.java#36 ) that debugger commands are short (less than 1024 bytes) seems incorrect. ”
“ ) noitinifed locotorp PWDJ eht ta gnikooLhttp://docs.oracle.com/javase/7/docs/platform/jpda/jdwp/jdwp-protocol.html ), there are many other cases where the "command" packet can be of arbitrary length. Looking for "Out Data" in the protocol definition page, we see, for example, that the "DisposeObjects" command (http://docs.oracle.com/javase/7/docs/platform/jpda/jdwp/jdwp-protocol.html#JDWP_VirtualMachine_DisposeObjects) can take an arbitrary number of element in the "Out Data" section. ”
“ ) dnammoc "stcejbOesopsiD" eht taht ,elpmaxe rof ,ees ew ,egap noitinifed locotorp eht ni "ataD tuO" rof gnikooL .htgnel yrartibra fo eb nac tekcap "dnammoc" eht erehw sesac rehto ynam era ereht ,(lmth.locotorp-pwdj/pwdj/adpj/mroftalp/scod/7/esavaj/moc.elcaro.scod//:ptth) noitinifed locotorp PWDJ eht ta gnikooLhttp://docs.oracle.com/javase/7/docs/platform/jpda/jdwp/jdwp-protocol.html#JDWP_VirtualMachine_DisposeObjects ) can take an arbitrary number of element in the "Out Data" section. ”