You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I encountered a panic while using winio on a 32-bit, x86 Windows 7 environment. The usage is quite straightforward—simply continuously read from and write to the pipe in a loop.
I've found the cause of the problem. In file.go under asyncIO, if err != windows.ERROR_IO_PENDING, it directly returns (besides success, there are other non-pending errors). This can lead to the memory invalidation of c *ioOperation. Meanwhile, the getQueuedCompletionStatus called by ioCompletionProcessor might still use this c *ioOperation, which can cause the process to crash.
I encountered a panic while using winio on a 32-bit, x86 Windows 7 environment. The usage is quite straightforward—simply continuously read from and write to the pipe in a loop.
The panic info:
client.go(who panic):
server.go:
The text was updated successfully, but these errors were encountered: