Fixed
Status Update
Comments
st...@gmail.com <st...@gmail.com> #2
have you actually hit this limit in practice?
ol...@gmail.com <ol...@gmail.com> #3
I've hit this limit and that made me question the choice of !28 in this bug report.
The scenario is the following:
- we're deploying unit and functional tests over SSH to non rooted Android devices
- beside executables we're deploying big assets (several GB) over SSH wtih rsync
- we're using SSHDroid which home is /data/data/berserker.android.apps.sshdroid/home
/data/data/berserker.android.apps.sshdroid/home is already 48 characters which is more than a third of the maximum allowed name if you pass an absolute path to dlopen()
Gregory
The scenario is the following:
- we're deploying unit and functional tests over SSH to non rooted Android devices
- beside executables we're deploying big assets (several GB) over SSH wtih rsync
- we're using SSHDroid which home is /data/data/berserker.android.apps.sshdroid/home
/data/data/berserker.android.apps.sshdroid/home is already 48 characters which is more than a third of the maximum allowed name if you pass an absolute path to dlopen()
Gregory
ol...@gmail.com <ol...@gmail.com> #5
I have patched 1.0.26 version of adb for windows, which can handle more that 64 handles, now it can handle about 256 handles.
but patch made not very well, good solution to change whole processing of handles, but now i have not enough time for it.
I'm attaching diff of sysdeps_win32.c and build patched version of adb.exe
but patch made not very well, good solution to change whole processing of handles, but now i have not enough time for it.
I'm attaching diff of sysdeps_win32.c and build patched version of adb.exe
ho...@gmail.com <ho...@gmail.com> #6
Google please help!! I also encounter this problem with r_10.
ma...@gmail.com <ma...@gmail.com> #7
[Comment deleted]
fr...@gmail.com <fr...@gmail.com> #8
The patched version above solved my problems. Great contribution!!
j7...@gmail.com <j7...@gmail.com> #9
[Comment deleted]
j7...@gmail.com <j7...@gmail.com> #10
Thanks to oleg.at for your help.
I'm encounter the same problem. I use your patch and solved my big problems, too.
Devices: HTC Desire HD 2.3.3 (kernel: 2.36.405.8)
Eclipse: Helios 1.3.2.20110301-1807
DDMS: 10.0.1.v201103111512-110841
Android SDK: r10
Tested on Win7 x64 with Eclipse x64
and WinXP x32 with Eclipse x32
I'm encounter the same problem. I use your patch and solved my big problems, too.
Devices: HTC Desire HD 2.3.3 (kernel: 2.36.405.8)
Eclipse: Helios 1.3.2.20110301-1807
DDMS: 10.0.1.v201103111512-110841
Android SDK: r10
Tested on Win7 x64 with Eclipse x64
and WinXP x32 with Eclipse x32
ni...@gmail.com <ni...@gmail.com> #11
Same problem here with a Desire HD.
This must be fixed ! Thanks oleg for your patch, this issue was driving me crazy.
This must be fixed ! Thanks oleg for your patch, this issue was driving me crazy.
si...@gmail.com <si...@gmail.com> #12
Oleg, thanks a lot ! Your patched file solved my problem with crashing adb.exe.
Device: HTC Desire HD 2.3.3 with kernel: 2.36.405.8
OS:Windows 7 64bit
Eclipse: Helios Service Release 2
Android SDK: r11.
Device: HTC Desire HD 2.3.3 with kernel: 2.36.405.8
OS:Windows 7 64bit
Eclipse: Helios Service Release 2
Android SDK: r11.
sa...@gmail.com <sa...@gmail.com> #13
Had the same problem.
Tested oleg's patch and works perfectly.
Device: HTC Desire HD 2.3.3 with kernel: 2.36.405.8
OS:Windows 7 64bit
Eclipse: Helios Service Release 2
Android SDK: r11.
Tested oleg's patch and works perfectly.
Device: HTC Desire HD 2.3.3 with kernel: 2.36.405.8
OS:Windows 7 64bit
Eclipse: Helios Service Release 2
Android SDK: r11.
pr...@gmail.com <pr...@gmail.com> #14
Way to go Oleg...your patch works beautifully.
MT4G/Windows XP (x32)/Eclipse Helios
MT4G/Windows XP (x32)/Eclipse Helios
ja...@gmail.com <ja...@gmail.com> #15
Thank you ! This patch fix my problem ...
al...@gmail.com <al...@gmail.com> #16
Had the same problem.
Tested oleg's patch and works perfectly.
Device: HTC Flayer P510e 2.3.4 with kernel: 2.6.35.10-g5c757f6
OS:Windows XP 32bit
Eclipse: Helios Service Release 1
Android SDK: r11.
Tested oleg's patch and works perfectly.
Device: HTC Flayer P510e 2.3.4 with kernel: 2.6.35.10-g5c757f6
OS:Windows XP 32bit
Eclipse: Helios Service Release 1
Android SDK: r11.
li...@gmail.com <li...@gmail.com> #17
This patch fixed my problem on HTC Flyer too. Thank you oleg.
my...@gmail.com <my...@gmail.com> #18
The patch helps a lot! Thanks oleg!
ma...@gmail.com <ma...@gmail.com> #19
Worked for me as well, Thank You!
gd...@gmail.com <gd...@gmail.com> #20
Thx a lot, the patch works like a charm ! :D
de...@gmail.com <de...@gmail.com> #21
Thank you very much. The patch saved me!
wa...@gmail.com <wa...@gmail.com> #22
Same problem, thanks for the patch.
OS: Windows XP 32bit
Eclipse: Galileo SR2
Android SDK: r12
OS: Windows XP 32bit
Eclipse: Galileo SR2
Android SDK: r12
vi...@gmail.com <vi...@gmail.com> #23
Awesome thanks for the patch!!!
se...@gmail.com <se...@gmail.com> #24
This fixed the constant crashing I was experiencing on my EVO 3D. Great work! Starring this so that it might find its way into the released ADB.
li...@gmail.com <li...@gmail.com> #25
Thank you for your patch.
dn...@gmail.com <dn...@gmail.com> #26
Shame on you google... What the @@@@ are you waiting for?.
Can't you fix this issue?
Can't you fix this issue?
gl...@gmail.com <gl...@gmail.com> #27
Thank you for your patch.
lo...@gmail.com <lo...@gmail.com> #28
Just updated my development tools and started seeing this bug again. Good thing I managed to find this thread to re-download the modified adb.exe. Else my development would have ground back to a screeching halt.
Android Team, how is this not fixed yet? It's been almost a year now since the issue was pointed out and a working patch was posted. That's like centuries in Androidtime. Believe it or not, Windows is used by quite a few of your developers...
Android Team, how is this not fixed yet? It's been almost a year now since the issue was pointed out and a working patch was posted. That's like centuries in Androidtime. Believe it or not, Windows is used by quite a few of your developers...
ma...@gmail.com <ma...@gmail.com> #29
Just updated too and started seeing this problem again. You'd think the android team would have patched it by now...
eu...@gmail.com <eu...@gmail.com> #30
Awesome!! I considered already to return to RIM dev.
t3...@gmail.com <t3...@gmail.com> #31
Just had to put in that after I upgraded to InfectedROM Eternity on my Evo 3D, adb started crashing in Eclipse as well as on the DOS shell. After applying the patch, adb works now! Thanks.
gy...@gmail.com <gy...@gmail.com> #32
Thank you~!
se...@gmail.com <se...@gmail.com> #33
Thank you! i was getting mad in having App Inventor working with latest Gingerbread Rom, with the patched adb.exe now all works perfectly!
Google should fix this asap!
Google should fix this asap!
st...@gmail.com <st...@gmail.com> #34
This did not seem to work for me. I continue to get this error when adb restarts.
Windows 7 64 bit
Android SDK v13
Android Platform Tools v7
HTC Panache
Android 2.3.3
Any ideas?
Windows 7 64 bit
Android SDK v13
Android Platform Tools v7
HTC Panache
Android 2.3.3
Any ideas?
[Deleted User] <[Deleted User]> #35
Try turning USB debugging off and then on again on your phone. That often
gets things to 'wake up' for me.
gets things to 'wake up' for me.
al...@gmail.com <al...@gmail.com> #36
Had the same problem.
Tested oleg's patch and now working again - thank for the workaround!!
*** Hey Android team! Please get this officially fixed!!! ***
Device: HTC Thunderbolt 2.3.4 (das BAMF 1.0.5)
OS:Windows 7 64bit
Eclipse: Helios Service Release 2
Android SDK: r13.
Tested oleg's patch and now working again - thank for the workaround!!
*** Hey Android team! Please get this officially fixed!!! ***
Device: HTC Thunderbolt 2.3.4 (das BAMF 1.0.5)
OS:Windows 7 64bit
Eclipse: Helios Service Release 2
Android SDK: r13.
le...@gmail.com <le...@gmail.com> #37
Workaround worked for me!
Thanks!
Thanks!
ma...@gmail.com <ma...@gmail.com> #38
Thanks for the workaround,that solve my big problem.
ro...@gmail.com <ro...@gmail.com> #39
Just started learning Android development and ran into this right away. Thanks to the Global Internets I found your patched ADB right away. Thanks so much!
as...@googlemail.com <as...@googlemail.com> #40
WOW!!! Thank you Oleg for the fix, I'd click the donate button if I found one!
I've been developing with this Android Desire HD for the last 6 months with unplugging/plugging in the USB, restarting computer and finding the adb failed on nearly every other attempt... it was incredibly painful that I even reverted to the slow emulator as being a faster way to develop. This patch fixes it and I'm over the moon today. Thank you, Thank you, Thank you, Thank you, Thank you.
I've been developing with this Android Desire HD for the last 6 months with unplugging/plugging in the USB, restarting computer and finding the adb failed on nearly every other attempt... it was incredibly painful that I even reverted to the slow emulator as being a faster way to develop. This patch fixes it and I'm over the moon today. Thank you, Thank you, Thank you, Thank you, Thank you.
al...@gmail.com <al...@gmail.com> #41
Thank you very much Oleg!
en...@gmail.com <en...@gmail.com> #42
Thank you, it works! Google, Please fix the problem!!
al...@gmail.com <al...@gmail.com> #43
Thank you very much! I've lost half day on this...
ol...@gmail.com <ol...@gmail.com> #44
It's very strange why google can't fix this. Or just apply my patch.
Adb have updated, but no fixies from google.
It's very pity!
Adb have updated, but no fixies from google.
It's very pity!
en...@gmail.com <en...@gmail.com> #45
Oleg, sorry, did you try to submit a patch with this method: http://source.android.com/source/submit-patches.html ?
Thanks for your help!
Thanks for your help!
da...@gmail.com <da...@gmail.com> #46
This really needs a fix. I had the problem of ADB crashing constantly with eclipse.
After few mins of usage it was disconnecting randomly.
Now witch oleg's patch its working well.
I actually flamed one kernel developer over this. Just fix it, Google.
After few mins of usage it was disconnecting randomly.
Now witch oleg's patch its working well.
I actually flamed one kernel developer over this. Just fix it, Google.
ho...@gmail.com <ho...@gmail.com> #47
Im developing on HTC Desire and Magic. Issue appears with both devices and was fixed using the adb.exe from above.
Thanks Oleg! Looking forward to a fix.
Thanks Oleg! Looking forward to a fix.
zk...@gmail.com <zk...@gmail.com> #48
Thanks Oleg for the contribution! I have suggested HTC to co-work with google to solve the problem.
ve...@gmail.com <ve...@gmail.com> #49
hi i am using htc desire s, i also got same problem, can any one tell me the procedure how to add these patchs stp by step. i am dont know how to fix this.
da...@gmail.com <da...@gmail.com> #50
Easy solution: just replace adb.exe in your sdk folder with the one provided by Oleg. This fixed my SGS/SGS2 connectivity.
Another solution (advanced): compile newest patched adb.exe.
Another solution (advanced): compile newest patched adb.exe.
ol...@gmail.com <ol...@gmail.com> #51
New patched version of adb (1.0.29)
Patch (diff) the same as early
Patch (diff) the same as early
mi...@sesma.eu <mi...@sesma.eu> #52
This issue has started happening to me when I've rooted a Desire HD. It shows normally 55 proceses in Eclipse and when compiling and running goes over 64 and crashes.
The weird thing is that I've also a rooted Nexus one that only shows in Eclipse the processes corresponding to my own applications that are running on the device while the Desire HD shows all the processes running like system processes. other apps, etc.
The weird thing is that I've also a rooted Nexus one that only shows in Eclipse the processes corresponding to my own applications that are running on the device while the Desire HD shows all the processes running like system processes. other apps, etc.
kd...@gmail.com <kd...@gmail.com> #53
Patched adb from Oleg works for me. Thanks a lot! No more adb crashes for me and my Desire HD
vi...@gmail.com <vi...@gmail.com> #54
Thanks a lot. I was going nuts for 2 days because of this issue. your binary fixed it.
hy...@gmail.com <hy...@gmail.com> #55
It really works,thanks a lot.
tw...@gmail.com <tw...@gmail.com> #56
HTC Desire HD, also have this problem~ Thanks for Oleg patch, it's work~
an...@gmail.com <an...@gmail.com> #57
The problem seems to be fixed with the 10th release of platform-tools ;)
ae...@gmail.com <ae...@gmail.com> #58
Guys, this has been driving me nuts for the past two days... the patch did not work for me :( have you got any more suggestions?
Just a quick update on the scenario: I have been working on my app for two weeks on the following environment: WIN 7 64 BIT > ECLIPSE > HTC DESIRE HD. Everything worked fine up to yesterday, when, out of nowhere, the adb started crashing. I tried (in the following order) to: 1. restart Eclipse; 2. Restart device; 3. Restart computer (done that several times) and manually restarted adb via prompt; 4. Updated my HTC drivers; 5. Tried to update android SDK (nothing new there); 6. uninstalling apps from device; and finally 7. Oleg's patch
I am almost formatting my laptop (really didn't want to do that) and restoring my phone to a month's old backup... all I get at the moment is the annoying windows crashed app dialog and the following message if I try to run/debug the app in my phone:
Failed to install myApp.apk on device 'HT0CFRX23906': Connection refused: connect
Any tips / suggestions / advice is most welcome.
Just a quick update on the scenario: I have been working on my app for two weeks on the following environment: WIN 7 64 BIT > ECLIPSE > HTC DESIRE HD. Everything worked fine up to yesterday, when, out of nowhere, the adb started crashing. I tried (in the following order) to: 1. restart Eclipse; 2. Restart device; 3. Restart computer (done that several times) and manually restarted adb via prompt; 4. Updated my HTC drivers; 5. Tried to update android SDK (nothing new there); 6. uninstalling apps from device; and finally 7. Oleg's patch
I am almost formatting my laptop (really didn't want to do that) and restoring my phone to a month's old backup... all I get at the moment is the annoying windows crashed app dialog and the following message if I try to run/debug the app in my phone:
Failed to install myApp.apk on device 'HT0CFRX23906': Connection refused: connect
Any tips / suggestions / advice is most welcome.
08...@seecs.edu.pk <08...@seecs.edu.pk> #59
@aerciofi
I had the same problem but with Samsung Galaxy S2, Oleg's patch worked perfectly for me. If you are formatting you laptop and doing stuff which is irrelevant then you are wasting your time and data. Just make sure to restart your adb and eclipse after applying Oleg's patch.
I had the same problem but with Samsung Galaxy S2, Oleg's patch worked perfectly for me. If you are formatting you laptop and doing stuff which is irrelevant then you are wasting your time and data. Just make sure to restart your adb and eclipse after applying Oleg's patch.
[Deleted User] <[Deleted User]> #60
I have the same question too.However after tring oleg`s adb.exe my problem has not been solved. what is the way?
[Deleted User] <[Deleted User]> #61
Another question is How shuold I use the sysdeps_win32.c.diff?
du...@gmail.com <du...@gmail.com> #62
Guys,so nice! It really works! Im developing on HTC Incredible S.
st...@gmail.com <st...@gmail.com> #63
thank you oleg, your patch works eventually!
It has been driving me nuts for the past two days...I downloaded you patch and replace the old adb.exe,but the patch did not work for me at first eventhough I restart the IDE,reboot my phone...
At last,I downgrade my phone's Android version (Nexus S,samsung I9023) from 4.0.4 to 2.3.6,then it works.
It has been driving me nuts for the past two days...I downloaded you patch and replace the old adb.exe,but the patch did not work for me at first eventhough I restart the IDE,reboot my phone...
At last,I downgrade my phone's Android version (Nexus S,samsung I9023) from 4.0.4 to 2.3.6,then it works.
ke...@gmail.com <ke...@gmail.com> #64
thx OLeg, the patch work perfectly!
pr...@gmail.com <pr...@gmail.com> #65
Thanks for the patch, adb workded for me all the time (original one) but today it started freaking crazy, adb tried to connect, got a connection and after a few seconds "This program does not work anymore..." force close and this within an endless loop.
Patch fixed it.
Win 7 64-Bit
Patch fixed it.
Win 7 64-Bit
ds...@gmail.com <ds...@gmail.com> #66
Has anyone managed to get the patch to work for them with a Galaxy S2?
Even with the patched version mine crashes ADB (with the 'forcibly closed by the remote host' error) after about 5-10s of being connected - gives me very little time to grab a screenshot, and the need to endlessly restart DDMS makes it rather difficult to get any work done :\
Even with the patched version mine crashes ADB (with the 'forcibly closed by the remote host' error) after about 5-10s of being connected - gives me very little time to grab a screenshot, and the need to endlessly restart DDMS makes it rather difficult to get any work done :\
st...@gmail.com <st...@gmail.com> #67
I'm experiencing the same problem :( There're only two solutions to this problem I found on-line, one is the adb.exe patch, the other is to restart adb, but neither of them works for me.
Windows 7 64-bits
Android SDK Tools Rev.16
Android SDK Platform-tools Rev.10
Windows 7 64-bits
Android SDK Tools Rev.16
Android SDK Platform-tools Rev.10
ch...@gmail.com <ch...@gmail.com> #68
- What happened.
Adb server krash. And if you enable adb debug trace you can see :
--------
I think you want to say "crash"?
Adb server krash. And if you enable adb debug trace you can see :
--------
I think you want to say "crash"?
no...@gmail.com <no...@gmail.com> #69
I think it is not problem in eclipse or adb its problem in the phone software means some antivirus or firewall software force to close the connection try to stop that software.
Thanks
Thanks
jv...@gmail.com <jv...@gmail.com> #70
how do i use the sysdeps?
de...@gmail.com <de...@gmail.com> #71
Thanks Oleg. That was really starting to annoy me.
ma...@gmail.com <ma...@gmail.com> #72
I replaced adb.exe to /platform-tools/ and restarted adb, also restarted my computer. But it doesn't work :((
My phone: HTC Desire A8181.
My phone: HTC Desire A8181.
sm...@gmail.com <sm...@gmail.com> #73
I just replaced the abd.exe file and now my HTC Aria connects
Thanks Oleg!
Thanks Oleg!
pf...@gmail.com <pf...@gmail.com> #74
thx @oleg..
win7 amd64 (restart os needed!)
win7 amd64 (restart os needed!)
[Deleted User] <[Deleted User]> #75
"--New patched version of adb (1.0.29)
Patch (diff) the same as early--"
It still not working for me.
...
The logcat "Unexpected error while launching logcat. Try reselecting the device.] 远程主机强迫关é—了一个现有的连接。"
IDE:Windows 7
Patch (diff) the same as early--"
It still not working for me.
...
The logcat "Unexpected error while launching logcat. Try reselecting the device.] 远程主机强迫关é—了一个现有的连接。"
IDE:Windows 7
mf...@gmail.com <mf...@gmail.com> #76
patch for mac??
qi...@gmail.com <qi...@gmail.com> #77
Thanks a lot!
dh...@gmail.com <dh...@gmail.com> #78
wheres the patch for ubuntu???
dh...@gmail.com <dh...@gmail.com> #79
I found a simple solution which worked for me
window >> prefrences >> logcat >> uncheck monitor logcat
only if you need to run the application badly
window >> prefrences >> logcat >> uncheck monitor logcat
only if you need to run the application badly
[Deleted User] <[Deleted User]> #80
a simple solution which worked for me
window >> prefrences >> logcat >> uncheck monitor logcat
only if you need to run the application badly
dhruvils...@gmail.com
window >> prefrences >> logcat >> uncheck monitor logcat
only if you need to run the application badly
dhruvils...@gmail.com
pr...@gmail.com <pr...@gmail.com> #81
very goog
ed...@gmail.com <ed...@gmail.com> #82
thank you
[Deleted User] <[Deleted User]> #83
my adb information :
Android Debug Bridge version 1.0.35
Revision 102d0d1e73de-android
seems not work
Android Debug Bridge version 1.0.35
Revision 102d0d1e73de-android
seems not work
Description
- Steps to reproduce the problem.
Write a script or do more than 64 unique port forwards. Ex,
adb forward tcp:10000 tcp:10000
adb forward tcp:10001 tcp:10001
adb forward tcp:10002 tcp:10002
etc etc...
- What happened.
Adb server krash. And if you enable adb debug trace you can see :
adb_win32: waiting for 65 events
handle count 65 exceeds MAXIMUM_WAIT_OBJECTS, aborting!
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
- What you think the correct behavior should be.
Linux version does not have this limitation and I would expect the same on windows.
Can be reproducible running the emulator.