IssueTracker

Thank you for this feedback. The team may reach out for more information on triaging or reproducing this issue.

pallavi@ - Have we done any testing on Win7? Looks like this issue should be easily reproducible.

a.sworowska: could you click the "view problem details" button and send us what that shows?

zyy: is there any other useful information about a crash on Windows that's easily available?

Problem signature:
  Problem Event Name:    APPCRASH
  Application Name:    adb.exe
  Application Version:    0.0.0.0
  Application Timestamp:    34f534d5
  Fault Module Name:    adb.exe
  Fault Module Version:    0.0.0.0
  Fault Module Timestamp:    34f534d5
  Exception Code:    40000015
  Exception Offset:    00016717
  OS Version:    6.1.7601.2.1.0.256.48
  Locale ID:    1033
  Additional Information 1:    7763
  Additional Information 2:    7763cd91f17ba1394e15130ad28436a8
  Additional Information 3:    622c
  Additional Information 4:    622c3aed538ac58f09882fe423edc57a


Also there's a console output: (for adb devices)
List of devices attached
* daemon not running. starting it now at tcp:5037 *
error: cannot open transport registration socketpair: Input/output error

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

We have the same problem at my workplace (computers running with the same configuration).
Changing the port (5037) didn't solve.
We were thinking about a conflict with the company's proxy but we gave up to find a solution as soon as we downgrade to 25.0.3 and understood that the update was responsible of the crash.

>zyy: is there any other useful information about a crash on Windows that's easily available?

One can generate a minidump file on crash, here's instructions (WER part): https://blogs.msdn.microsoft.com/chaun/2013/11/12/steps-to-catch-a-simple-crash-dump-of-a-crashing-process/

Other option would be to integrate Breakpad (https://chromium.googlesource.com/breakpad/breakpad/); it will take much longer but would allow for automatic / user-initiated crash information submission

I did the WER method and generate a dmp file (2 in fact because of the DumpCount set to 2... Should I set it higher ?)
But it is a 40MB file which I can't upload. Any suggestion ?

Thank you so much! You can either archive the dump with 7zip or plain Zip - .dmp files pack really well. Or you could upload it to some file share, e.g. Google Drive, and give a link here. Anything would work

the stack overflow match for "Exception Code:    40000015" says it's what happens when you call abort(3).

that combined with the error message points to this:

    if (adb_socketpair(s)) {
        fatal_errno("cannot open transport registration socketpair");

unfortunately adb_socketpair only writes its failures to the debug log.

i don't think we need a dmp file, but can someone run adb with the ADB_TRACE environment variable set to "all" so we can see the underlying error? we're looking for an error that starts "adb_socketpair:". (and our QA folks did test on Windows 7 but didn't hit this.)

(i'm being deliberately vague about how to set an environment variable on Windows because i assume everyone reading this knows better than i do!)

Output for adb devices (with ADB_TRACE set to "all")

adb I 03-23 09:00:57  3852  6096 adb_trace.cpp:178] Android Debug Bridge version 1.0.39
adb I 03-23 09:00:57  3852  6096 adb_trace.cpp:178] Revision 5943271ace17-android
adb I 03-23 09:00:57  3852  6096 adb_trace.cpp:178]
List of devices attached
adb I 03-23 09:00:57  3852  6096 adb_client.cpp:271] adb_query: host:devices
adb I 03-23 09:00:57  3852  6096 adb_client.cpp:124] _adb_connect: host:version
adb I 03-23 09:00:57  3852  6096 sysdeps_win32.cpp:750] port 5037 type tcp => fd 2048
adb I 03-23 09:00:57  3852  6096 adb_io.cpp:101] writex: fd=2048 len=16 30303063686f73743a76657273696f6e 000chost:version
adb I 03-23 09:00:57  3852  6096 adb_io.cpp:75] readx: fd=2048 wanted=4
adb I 03-23 09:00:57  3852  6096 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 4f4b4159 OKAY
adb I 03-23 09:00:57  3852  6096 adb_client.cpp:157] _adb_connect: return fd 2048
adb I 03-23 09:00:57  3852  6096 adb_client.cpp:165] adb_connect: service host:devices
adb I 03-23 09:00:57  3852  6096 adb_io.cpp:75] readx: fd=2048 wanted=4
adb I 03-23 09:00:57  3852  6096 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 30303034 0004
adb I 03-23 09:00:57  3852  6096 adb_io.cpp:75] readx: fd=2048 wanted=4
adb I 03-23 09:00:57  3852  6096 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 30303234 0024
adb I 03-23 09:00:57  3852  6096 sysdeps_win32.cpp:475] adb_close: 2048(lo-client:5037)
adb server version (36) doesn't match this client (39); killing...
adb I 03-23 09:00:57  3852  6096 adb_client.cpp:124] _adb_connect: host:kill
adb I 03-23 09:00:57  3852  6096 sysdeps_win32.cpp:750] port 5037 type tcp => fd 2048
adb I 03-23 09:00:57  3852  6096 adb_io.cpp:101] writex: fd=2048 len=13 30303039686f73743a6b696c6c 0009host:kill
adb I 03-23 09:00:57  3852  6096 adb_io.cpp:75] readx: fd=2048 wanted=4
adb I 03-23 09:00:57  3852  6096 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 4f4b4159 OKAY
adb I 03-23 09:00:57  3852  6096 adb_client.cpp:157] _adb_connect: return fd 2048
adb I 03-23 09:00:57  3852  6096 sysdeps_win32.cpp:475] adb_close: 2048(lo-client:5037)
adb I 03-23 09:00:59  7704  6108 adb_trace.cpp:178] Android Debug Bridge version 1.0.39
adb I 03-23 09:00:59  7704  6108 adb_trace.cpp:178] Revision 5943271ace17-android
adb I 03-23 09:00:59  7704  6108 adb_trace.cpp:178]
adb I 03-23 09:00:59  7704  6108 sysdeps_win32.cpp:827] port 0 type tcp => fd 2048
adb I 03-23 09:00:59  7704  6108 sysdeps_win32.cpp:1060] adb_socketpair: bound on port 57887
adb I 03-23 09:00:59  7704  6108 sysdeps_win32.cpp:750] port 57887 type tcp => fd 2049
adb I 03-23 09:00:59  7704  6108 sysdeps_win32.cpp:945] adb_socket_accept on fd 2048 returns fd 2050
adb I 03-23 09:00:59  7704  6108 sysdeps_win32.cpp:1087] adb_socketpair: client and peer sockaddrs don't match
adb I 03-23 09:00:59  7704  6108 sysdeps_win32.cpp:475] adb_close: 2048(lo-server:0)
adb I 03-23 09:00:59  7704  6108 sysdeps_win32.cpp:475] adb_close: 2049(lo-client:57887)
adb I 03-23 09:00:59  7704  6108 sysdeps_win32.cpp:475] adb_close: 2050(accept:2048(lo-server:0))
error: cannot open transport registration socketpair: Input/output error

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.


Is this what you wanted?

Here is mine : (french savage, I'll translate the french part =)   )



Z:\>adb start-server
adb I 03-23 09:39:49  5064  5788 adb_trace.cpp:178] Android Debug Bridge version
 1.0.39
adb I 03-23 09:39:49  5064  5788 adb_trace.cpp:178] Revision 5943271ace17-androi
d
adb I 03-23 09:39:49  5064  5788 adb_trace.cpp:178]
adb I 03-23 09:39:49  5064  5788 adb_client.cpp:124] _adb_connect: host:version
adb I 03-23 09:39:50  5064  5788 sysdeps_win32.cpp:742] could not connect to tcp:5037: cannot connect to 127.0.0.1:5037: Une requ├¬te dÔÇÖenvoi ou de r├®ception de donn├®es nÔÇÖa pas ├®t├® autoris├®e car le socket nÔÇÖest pas connect├® et (lors de lÔÇÖenvoi sur un socket datagramme en utilisant un appel sendto) aucune adresse nÔÇÖa ├®t├® fournie. (10057)
adb I 03-23 09:39:50  5064  5788 adb_client.cpp:165] adb_connect: service host:start-server
* daemon not running. starting it now at tcp:5037 *
adb I 03-23 09:39:50  3088  3320 adb_trace.cpp:178] Android Debug Bridge version 1.0.39
adb I 03-23 09:39:50  3088  3320 adb_trace.cpp:178] Revision 5943271ace17-android
adb I 03-23 09:39:50  3088  3320 adb_trace.cpp:178]
adb I 03-23 09:39:50  3088  3320 sysdeps_win32.cpp:827] port 0 type tcp => fd 2048
adb I 03-23 09:39:50  3088  3320 sysdeps_win32.cpp:1060] adb_socketpair: bound on port 52137
adb I 03-23 09:39:50  3088  3320 sysdeps_win32.cpp:750] port 52137 type tcp => fd 2049
adb I 03-23 09:39:50  3088  3320 sysdeps_win32.cpp:945] adb_socket_accept on fd2048 returns fd 2050
adb I 03-23 09:39:50  3088  3320 sysdeps_win32.cpp:1087] adb_socketpair: client and peer sockaddrs don't match
adb I 03-23 09:39:50  3088  3320 sysdeps_win32.cpp:475] adb_close: 2048(lo-server:0)
adb I 03-23 09:39:50  3088  3320 sysdeps_win32.cpp:475] adb_close: 2049(lo-client:52137)
adb I 03-23 09:39:50  3088  3320 sysdeps_win32.cpp:475] adb_close: 2050(accept:2048(lo-server:0))
error: cannot open transport registration socketpair: Input/output error

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
could not read ok from ADB Server
* failed to start daemon *
error: cannot connect to daemon



Translate :

adb I 03-23 09:39:50  5064  5788 sysdeps_win32.cpp:742] could not connect to tcp:5037: cannot connect to 127.0.0.1:5037: A sending or receiving request is not authorize because the socket is not connected and (during the sending on a datagramme socket using a call sendto) no adress given. (10057)

reassigning to jmgao to see if he can work out what's going on here. (i worry that we might have to ask you to run a build that actually prints out the difference between the two sockaddrs. does anyone know whether https://technet.microsoft.com/en-us/sysinternals/bb896645.aspx can trace network operations?)

smudunuri: we'd still be very interested if you can reproduce this.

Tried with the following steps to verify the bug.

OS: Windows 7 SP1 - 64 bit.
Studio Tested: 2.3.0

Followed the below steps.
1. Open studio with platform-tools 25.0.3
2. Go to SDK/Plaform-tools and run "adb devices"
3. Select the update channel in the studio to stable.
4. Update the platform-tools from 25.0.3 to 25.0.4
5. Go to SDK/Platform-tools and run "adb devices"

Updated platform-tools is working well.

I've uploaded a debug build with additional logging to https://drive.google.com/open?id=0B-WZo8dnekVTM3FjV0ZhMmx1MWs (too big to attach to the bug), could you try replacing your adb.exe with this and posting the output it gives?

@smudn : I tried your way... Didn't work

@jm : I don't have access to google drive (and most of the dl sites), is it possible to upload it somewhere else ? Or I'll do it next week.