Panic when opening a file dialog on macOS chip M4
Open
Nobody has claimed this yet.
bug
help wanted
needs more testing
- Dominant language
- Rust
- Stars
- 830
- Forks
- 108
- Avg merge
- 6d 33m
- Merged PRs (30d)
- 2
Description
Hey @PolyMeilex a user of my app reported this panic message every time he tries to open a file dialog:
thread 'main' panicked at /Users/runner/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/objc2-app-kit-0.3.1/src/generated/NSOpenPanel.rs:127:5:
unexpected NULL returned from +[NSOpenPanel openPanel]
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
fatal runtime error: failed to initiate panic, error 3, aborting
This doesn't happen on my macOS Intel chip, but does happen on his M4 chip.
Original issue: https://github.com/GyulyVGC/sniffnet/issues/878
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the file-dialog failure on an Apple M4 macOS system and capture the backtrace around objc2-app-kit-0.3.1/src/generated/NSOpenPanel.rs:127. Compare the macOS path with Intel behavior and identify why +[NSOpenPanel openPanel] returns NULL. Done means opening a file dialog no longer panics on the reported M4 environment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100