-
Notifications
You must be signed in to change notification settings - Fork 470
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
GetDataSetDirectoryAsync got System.AccessViolationException #498
Comments
In what function does the application crash? |
Hi, App crashed at "con.GetDataSetDirectoryAsync"
|
Please note that, when con.MaxPduSize does not set. (default value 65000) this function works well. |
I found an issue with the .NET wrapper when the server doesn't send a response but an error message instead. Could this be the case here? I guess the dataset is too big to fit into a the small MMS PDU size and the server is sending an error message instead. |
You are correct. And the issue I want to point out is the dataset is too big to fit into a the small MMS PDU size. the reason PDU size is 1000 is for GetNameListHandler work well, when PDU larger than 1000 I got many IED timeout with my test. |
There is no way to send a larger dataset when the MMS size is too small. Only the getnamelist MMS service supports splitting the response in multiple MMS messages. But the issue (crash) should be resolved with this fix: 681d1b0 |
Okay. Thank youuuu. Let me try again with the latest source code |
Hello,
Evinronment: C#
Lib version 1.5.3
When I set MaxPduSize to 1000 app crash happens.
The reason I need to set it to 1000 to GetLogicalDeviceVariablesAsync without problem of timeout. When the value of MaxPduSize is larger than 1000 IED timeout error happens frequently.
System.AccessViolationException HResult=0x80004003 Message=Attempted to read or write protected memory. This is often an indication that other memory is corrupt. Source=<Cannot evaluate the exception source> StackTrace: <Cannot evaluate the exception stack trace>
The text was updated successfully, but these errors were encountered: