Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to use more than 40 devices! I have 100 sets of equipment! Unable to start #464

Open
q6654282 opened this issue Oct 28, 2022 · 9 comments

Comments

@q6654282
Copy link

How to use more than 40 devices! I have 100 sets of equipment! Unable to start

@rom1v
Copy link
Collaborator

rom1v commented Oct 28, 2022

Unable to start

What do you execute? What is the error message in the console?

@q6654282
Copy link
Author

Memory allocation exceeded

@q6654282
Copy link
Author

2022-10-29 13:14:23.902 ERROR AdbMonitor: Failed to monitor adb devices: Packet size should not be that big: 2222
2022-10-29 13:14:23.902 INFO AdbMonitor: Restarting adb daemon

@q6654282
Copy link
Author

Problems! As above

@rom1v
Copy link
Collaborator

rom1v commented Oct 29, 2022

How to use more than 40 devices! I have 100 sets of equipment! Unable to start

Memory allocation exceeded

Yes, this is a known design issue (I can't find another related bug but I remember it exists): a buffer is allocated upfront for each connection (so there is no memory allocation during forwarding).

It should be rewritten to dynamically allocate/reuse packets.

2022-10-29 13:14:23.902 ERROR AdbMonitor: Failed to monitor adb devices: Packet size should not be that big: 2222

Indeed, the adb monitor does not expect more than 1024 bytes per read. To be fixed also in autoadb.

Also refs #396.

@q6654282
Copy link
Author

How to use more than 40 devices! I have 100 sets of equipment! Unable to start
Memory allocation exceeded

Yes, this is a known design issue (I can't find another related bug but I remember it exists): a buffer is allocated upfront for each connection (so there is no memory allocation during forwarding).

It should be rewritten to dynamically allocate/reuse packets.

2022-10-29 13:14:23.902 ERROR AdbMonitor: Failed to monitor adb devices: Packet size should not be that big: 2222

Indeed, the adb monitor does not expect more than 1024 bytes per read. To be fixed also in autoadb.

Also refs #396.

yes! This is the problem of automatic cache allocation! Is it possible to upgrade the version to solve this problem!

@q6654282
Copy link
Author

q6654282 commented Nov 4, 2022

Is there a solution to this problem

@rom1v
Copy link
Collaborator

rom1v commented Nov 4, 2022

Not really without major design changes, that I don't plan to make because I'm not really working on gnirehtet anymore (I still continue scrcpy, and both are on my free time only).

@q6654282
Copy link
Author

q6654282 commented Nov 5, 2022

All that remains is to wait! ha-ha

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants