sniffnet: thread 'main' panicked on launch (macOS)

Describe the bug sniffnet panics immediately on launch on MacBook Pro w/ M1 Pro

To Reproduce Describe steps to reproduce the bug, e.g.:

❯ RUST_BACKTRACE=full sniffnet

  /---------------------------------------------------------\
 |     _____           _    __    __                  _      |
 |    / ____|         (_)  / _|  / _|                | |     |
 |   | (___    _ __    _  | |_  | |_   _ __     ___  | |_    |
 |    \___ \  | '_ \  | | |  _| |  _| | '_ \   / _ \ | __|   |
 |    ____) | | | | | | | | |   | |   | | | | |  __/ | |_    |
 |   |_____/  |_| |_| |_| |_|   |_|   |_| |_|  \___|  \__|   |
 |                                                           |
 |                   ___________                             |
 |                  /___________\                            |
 |                 | ___________ |                           |
 |                 | |         | |                           |
 |                 | | v1.1.2  | |                           |
 |                 | |_________| |________________________   |
 |                 \_____________/   by Giuliano Bellini  )  |
 |                 / ''''''''''' \                       /   |
 |                / ::::::::::::: \                  =D-'    |
 |               (_________________)                         |
  \_________________________________________________________/
thread 'main' panicked at '', /Users/brew/Library/Caches/Homebrew/cargo_cache/registry/src/github.com-1ecc6299db9ec823/wgpu-hal-0.14.1/src/metal/adapter.rs:485:13
stack backtrace:
   0:        0x10271bf6c - __mh_execute_header
   1:        0x102469748 - __mh_execute_header
   2:        0x102701d94 - __mh_execute_header
   3:        0x10271bcc4 - __mh_execute_header
   4:        0x10270c3fc - __mh_execute_header
   5:        0x10270c0dc - __mh_execute_header
   6:        0x10244bb80 - __mh_execute_header
   7:        0x10270cb7c - __mh_execute_header
   8:        0x10271c63c - __mh_execute_header
   9:        0x10271c5ac - __mh_execute_header
  10:        0x10270c7cc - __mh_execute_header
  11:        0x1028206c8 - __mh_execute_header
  12:        0x1027f1314 - __mh_execute_header
  13:        0x1027fe5f8 - __mh_execute_header
  14:        0x1027fb32c - __mh_execute_header
  15:        0x1024361a8 - __mh_execute_header
  16:        0x1026af910 - __mh_execute_header
  17:        0x10244ab30 - __mh_execute_header
  18:        0x102686da8 - __mh_execute_header
  19:        0x10244de20 - __mh_execute_header

Desktop (please complete the following information):

OS: macOS 13.3

About this issue

Original URL
State: closed
Created a year ago
Reactions: 1
Comments: 25 (11 by maintainers)

Most upvoted comments

Don’t worry at all man! And thanks for the further confirmation that the issue has been fixed. I’ll close it once next version is released.

GyulyVGC on Apr 14, 2023

Working for me now 👍

adwhit on Apr 14, 2023

I will help out with some linkage test failures with this formula upgrade PR, and we should be good to go from there. 😃

chenrui333 on Apr 20, 2023

A new release has just been published. Thanks to you all guys for having pointed out the problem. Closing the issue.

GyulyVGC on Apr 18, 2023

Hello! FYI I installed just now with cargo install sniffnet and got the same error on macOS 13.3/M1 Pro. I’m not a Rust person so I’m not sure but maybe this is because a cargo registry needs to be updated with the fixed version, or something like that? Anyway, no big problem, just trying it out, but reporting in case it’s useful. Cheers 😃

Hi @igorclark. Exactly. I’ll update the version on crates in the next few days. However, you can immediately use the last commit from GitHub by cloning the repo and building the app with

cargo run --release

GyulyVGC on Apr 14, 2023

Ayy glad its working!

Love the sniffnet

ElhamAryanpur on Apr 14, 2023

No Problem. The .dmg from the github release also works fine

exomaniac on Apr 4, 2023

I just did a build myself. This runs fine. ill try the other options also

Oh, that’s nice to know. I guess it’s a problem related with the brew package then. I will contact them! Thank you very much.

GyulyVGC on Apr 4, 2023