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

fix bug,channel receiver in debug is blocked by self io #137

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

zmrush
Copy link

@zmrush zmrush commented Jun 6, 2024

channel receiver in wait_pid function would be blocked by self io opertion

@zmrush zmrush requested a review from a team as a code owner June 6, 2024 09:44
@zmrush
Copy link
Author

zmrush commented Jun 6, 2024

@Burning1020 ,can u help for this commit

@Burning1020
Copy link
Member

@zmrush How did you exec into the vm? There is no keywords when connected to hvsock until input CONNECT 1025.

@zmrush
Copy link
Author

zmrush commented Jun 7, 2024

@zmrush How did you exec into the vm? There is no keywords when connected to hvsock until input CONNECT 1025.

i dont understand your question. but i think exec into vm has nothing to do with 'input connect 1025 using the io'. In other words, it has already exec into the vm?

@zmrush
Copy link
Author

zmrush commented Jun 17, 2024

@zmrush How did you exec into the vm? There is no keywords when connected to hvsock until input CONNECT 1025.

i dont understand your question. but i think exec into vm has nothing to do with 'input connect 1025 using the io'. In other words, it has already exec into the vm?

@Burning1020

@Burning1020
Copy link
Member

@zmrush Sorry, maybe I was misunderstood. So what's the specific problem you got? What's the influence of blocking receiver? Please give more details.

@zmrush
Copy link
Author

zmrush commented Jun 17, 2024

@zmrush Sorry, maybe I was misunderstood. So what's the specific problem you got? What's the influence of blocking receiver? Please give more details.

@Burning1020 blocking receiver may cause memory increase unexpectedly.

@Burning1020
Copy link
Member

@Burning1020 blocking receiver may cause memory increase unexpectedly.

OK, so how to reproduce it? I'd like to investigate it

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

Successfully merging this pull request may close these issues.

2 participants