![]() ![]()
#ACCESS VIOLATION IN MODULE ERROR IN PROTEUS CODE#For properly written code it should never happen (this is not kernel code where you may do it intentionally). It's very rare that the access violation is caused by a managed unsafe code because you have to go out of your way to allow it. NET programs the major cause of these exceptions are unmanaged libraries and improper interfaces to unmanaged libraries. I understand that it's nearly inevitable that AccessViolationException will happen at some point if you deploy application at scale to unknown environments. Maybe my perspective will help you understand why I suggest to rely on WER (or any other operating system mechanism) for these kind of errors. NET application and we spend quite some time with trying many error reporting tools (in-app, systems for collecting, external tools, etc.) and 10+ years on debugging various errors with a desktop application deployed to more than million of users. I will post my original follow-up anyway in case someone else stumbles upon it: Can you elaborate on why 64Kb pages are a problem for you? How would 4Kb pages help you? Are you trying to create some guard page scheme? ![]() I kinda started writing a long follow-up before I noticed this sentence. #ACCESS VIOLATION IN MODULE ERROR IN PROTEUS WINDOWS#Saying that for our case if windows allowed 4kb pages in the first place non of this would be needed net core, really the tag should just be removed if it's not going to be supported (it should be supported) And by default there needs to be something to tell the user a crash has occurred, not just closing the application.Īs a bare minimum the documentation needs to make it clear that this feature doesn't work in. I'm well aware that it's not smart to continue running but ultimately I think that decision should be left to the developer, not the. In short it's a terrible solution for us.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |