Dropping EventLoopHandle after running a request causes the program to hang. about rust-web3 HOT 8 CLOSED

After test, I think it is hang at EventLoopHandle::Drop.

Move the event_loop into another thread and ignore it can avoid this bug (uncleanly exit?).

from rust-web3.

Good catch it's really interesting why it fails.

from rust-web3.

I have the same issue

from rust-web3.

FYI: But if I use an event loop from tokio everything is OK

from rust-web3.

Finally, I have known what happened.

It hangs at event_loop.turn(None);, before checking the done flag.

When we want to shutdown the event_loop, we stop send any new message, and set the done flag.
But the event_loop will check the done flag after next message, so it hangs at waiting for next message.
So, it hangs.

The simplest way (but stupid?) to fix this bug is: after set the done flag, send to it a new message.

from rust-web3.

Perhaps we could supply a timeout to turn?

from rust-web3.

@yangby-cryptape is correct I think. I added self.remote.spawn(|_| Ok(())) before the thread join. It seems to fix it on my end.

#144

from rust-web3.

Resolved via #144

from rust-web3.