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

Infinite Mac crash when using CMD-Q and cancelling the quit browser dialog #277

Open
that-ben opened this issue Jan 4, 2024 · 2 comments

Comments

@that-ben
Copy link

that-ben commented Jan 4, 2024

I don't know if it's worth investigating, but I figure it's best to post it just in case it might lead to discovering more bugs related to this. It's 100% reproducible in Firefox under macOS Sonoma:

  1. Launch Mac OS 9 in IM: https://infinitemac.org/1999/Mac%20OS%209.0

  2. Left click a sticky note.

  3. Hit CMD-Q which will trigger Firefox quit browser confirmation dialog. Click cancel.

  4. Type the letter Q on your keyboard a couple times and IM will crash with one of those (random, but most of the times I get an out of bounds exception and sometimes the Aborted() error)

Screenshot 2024-01-04 at 12 47 45 PM Screenshot 2024-01-04 at 12 47 03 PM Screenshot 2024-01-04 at 12 46 15 PM
@that-ben that-ben changed the title Infinite Mac crash when using CMD-Q and cancelling the quit browser dialog window Infinite Mac crash when using CMD-Q and cancelling the quit browser dialog Jan 4, 2024
@ghost
Copy link

ghost commented Jan 10, 2024

I was messing around in Mac OS 9 and somehow triggered this error in Chrome on Windows. I don't remember what I was doing but I somehow crashed the emulator while doing nothing that should crash it. Wonder if the SheepShaver emulators are getting unstable for some reason.

It might be worth actually building SheepShaver with "-sASSERTIONS" so we can figure out exactly why it crashes (since this dialog only appears if there is an error, it would be useful to know why the emulator aborted)

@that-ben
Copy link
Author

that-ben commented Jan 10, 2024

It definitely has something to do with keystrokes after the emulator canvas is losing and regaining focus. Somehow it overflows a buffer of some kind, but I'll not pollute this thread with assumptions and leave the pro take a look at it 😜

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

1 participant