![]() ![]() 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. 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. Many of the issues we will likely face will be hard to replicate so after the first crash it may never come up again, especially if the error only comes up after extended use.It would require the user to actively work with us to debug the issue when most users, if you are lucky.It only works on windows, defeating the whole point of using core (saying that for our case if windows allowed 4kb pages in the first place non of this would be needed).We would have to sign our application which we don't currently do and see no reason to do so.To enable it each user need to mess with the registry which most people just aren't comfortable doing.I don't want to use Window error reporting because: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
May 2023
Categories |