You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A user of my application reports a crash when "spending a couple of seconds looking for files" in dialogs. They report that it happens with both open-file dialogs and save-file dialogs. The user is on macOS Monterey. I'm using the sync API and I believe I'm calling from the main thread in a windowed environment (miniquad/macroquad).
The text was updated successfully, but these errors were encountered:
The application is built on macOS 13, so maybe this could be due to a forward-incompatibility issue in macOS? I'm not sure how that sort of thing works.
This is the backtrace I have. However, most of the stack frames are <unknown> and in my experience the order of frames can't really be trusted; i.e. I've seen other examples where the last frame before the panic handler code is not the frame the panic actually originated from.
A user of my application reports a crash when "spending a couple of seconds looking for files" in dialogs. They report that it happens with both open-file dialogs and save-file dialogs. The user is on macOS Monterey. I'm using the sync API and I believe I'm calling from the main thread in a windowed environment (miniquad/macroquad).
The text was updated successfully, but these errors were encountered: