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

Graph Studio Next 32bit version running on 64bit OS silently ignores exceptions that happen from user mode callbacks (e.g. key press handlers) #269

Closed
mikecopperwhite opened this issue Jun 10, 2015 · 1 comment

Comments

@mikecopperwhite
Copy link
Collaborator

http://blog.paulbetts.org/index.php/2010/07/20/the-case-of-the-disappearing-onload-exception-user-mode-callback-exceptions-in-x64/

https://support.microsoft.com/en-us/kb/976038

This Windows issue affects 32bit versions of the program running on 64bit versions Windows 7 and Vista. 32bit versions of Windows and/or 64bit versions of the program are apparently not affected.

For compatibility Windows will silently swallow exceptions (crashes) that happen from a user mode callback (e.g. a key press handler) but won't do this if the same code is reached from another route (e.g. a right click context menu). This leaves the program in an uncertain state with no indication that a problem has occured.

I think Graph Studio Next should call the new API (if the API is present) on startup that disables this horrible behaviour and allows these exceptions to happen. IMO Graph Studio next is a developer tool and should not be masking out filter crashes. If really desirable we could make this a selectable option menu item but I think it should be default to allow exceptions.

@roman380
Copy link
Collaborator

I agree, a dev tool does not need to swallow.

mikecopperwhite added a commit that referenced this issue Jun 10, 2015
…back exception filter as we need to see these exceptions in a developer tool.
mikecopperwhite added a commit that referenced this issue Jun 14, 2015
…ew APIs Get/SetProcessUserModeExceptionPolicy
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants