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

Unhandled win32 exception #87

Open
Lance-Inman opened this Issue Aug 31, 2017 · 2 comments

Comments

Projects
None yet
2 participants
@Lance-Inman
Copy link

Lance-Inman commented Aug 31, 2017

An unhandled win32 exception is thrown while using Smart Responses with Persistent TCP enabled causing PacketSender.exe to crash.

I am using a Smart Response with the following parameters:
If Packet data equals "05 00" Reply with "06 00" with HEX Encoding

I receive three TCP packets with the content "05 00" on separate connections at 1 second intervals, the sender closes the socket immediately after sending the packet. Packet Sender shows "05 00" being received and "06 00" being sent in the log and opens a Persistent TCP window. After 1 second another Persistent TCP window is opened and Packet Sender may or may not show "05 00" being received and "06 00" being sent. Packet Sender then crashes. The "06 00" that shows as being sent from Packet Sender is never received by the sender of "05 00".

Visual Studio JIT Debugger describes the bug as "An unhandled win32 exception occurred in PacketSender.exe [111132]."

Replicating this process without Smart Responses by manually sending the "06 00" response works fine.

@dannagle

This comment has been minimized.

Copy link
Owner

dannagle commented Aug 31, 2017

How does it do without Persistent TCP enabled?

@dannagle dannagle added the bug label Aug 31, 2017

@Lance-Inman

This comment has been minimized.

Copy link
Author

Lance-Inman commented Aug 31, 2017

When Persistent TCP is not enabled it works fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.