search

thewh1teagle / vibe

Transcribe on your own!
https://thewh1teagle.github.io/vibe/
MIT License
1.21k stars 71 forks source link

Bug: Crashes on launching transcription since 2.6.5 #395

Open oleole39 opened 1 day ago

oleole39 commented 1 day ago

What happened?

Vibe crashes when launching transcription

Steps to reproduce

What OS are you seeing the problem on?

Linux

Relevant log output

user@computer:~$ RUST_LOG=vibe=debug,whisper_rs=debug RUST_BACKTRACE=1 /usr/bin/vibe
2024-11-16T14:39:52.397089Z DEBUG vibe::setup: Vibe App Running
2024-11-16T14:39:52.397125Z DEBUG vibe::setup: webview version: 2.46.1
2024-11-16T14:39:52.397132Z DEBUG vibe::setup: Cargo features: vulkan
2024-11-16T14:39:52.397135Z DEBUG vibe::setup: CPU feature detection is not supported on this architecture.
2024-11-16T14:39:52.397139Z DEBUG vibe::setup: Executable Architecture: x86_64
2024-11-16T14:39:52.397144Z DEBUG vibe::setup: APP VERSION: 2.6.5
2024-11-16T14:39:52.397147Z DEBUG vibe::setup: COMMIT HASH: 446648d
2024-11-16T14:39:52.397154Z DEBUG vibe::setup: Non CLI mode
2024-11-16T14:39:52.869101Z DEBUG vibe::cmd: Vulkan check skipped on this platform
2024-11-16T14:39:52.879051Z DEBUG vibe::cmd::audio: Default Input Device:
Ok("default")
2024-11-16T14:39:52.879070Z DEBUG vibe::cmd::audio: Default Output Device:
Ok("default")
2024-11-16T14:39:52.898466Z DEBUG vibe::cmd::audio: Devices: 
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
ALSA lib pcm_oss.c:397:(_snd_pcm_oss_open) Cannot open device /dev/dsp
ALSA lib pcm_oss.c:397:(_snd_pcm_oss_open) Cannot open device /dev/dsp
ALSA lib pcm_route.c:877:(find_matching_chmap) Found no matching channel map
ALSA lib pcm_route.c:877:(find_matching_chmap) Found no matching channel map
ALSA lib pcm_route.c:877:(find_matching_chmap) Found no matching channel map
ALSA lib pcm_route.c:877:(find_matching_chmap) Found no matching channel map
ALSA lib pcm_route.c:877:(find_matching_chmap) Found no matching channel map
ALSA lib pcm_route.c:877:(find_matching_chmap) Found no matching channel map
ALSA lib pcm_dmix.c:1005:(snd_pcm_dmix_open) The dmix plugin supports only playback stream
ALSA lib pcm_dmix.c:1005:(snd_pcm_dmix_open) The dmix plugin supports only playback stream
ALSA lib pcm_dmix.c:1005:(snd_pcm_dmix_open) The dmix plugin supports only playback stream
ALSA lib pcm_dmix.c:1005:(snd_pcm_dmix_open) The dmix plugin supports only playback stream
ALSA lib pcm_dmix.c:1005:(snd_pcm_dmix_open) The dmix plugin supports only playback stream
ALSA lib pcm_dmix.c:1005:(snd_pcm_dmix_open) The dmix plugin supports only playback stream
ALSA lib pcm_dmix.c:1005:(snd_pcm_dmix_open) The dmix plugin supports only playback stream
ALSA lib pcm_dmix.c:1005:(snd_pcm_dmix_open) The dmix plugin supports only playback stream
ALSA lib pcm_dmix.c:1005:(snd_pcm_dmix_open) The dmix plugin supports only playback stream
ALSA lib pcm_dmix.c:1005:(snd_pcm_dmix_open) The dmix plugin supports only playback stream
ALSA lib pcm_dmix.c:1005:(snd_pcm_dmix_open) The dmix plugin supports only playback stream
ALSA lib pcm_dmix.c:1005:(snd_pcm_dmix_open) The dmix plugin supports only playback stream
ALSA lib pcm_dsnoop.c:575:(snd_pcm_dsnoop_open) The dsnoop plugin supports only capture stream

** (WebKitWebProcess:133023): WARNING **: 15:40:05.560: The GStreamer FDK AAC plugin is missing, AAC playback is unlikely to work.
2024-11-16T14:40:16.757666Z DEBUG vibe::cmd: loading model first time
2024-11-16T14:40:16.757765Z DEBUG vibe_core::transcribe: open model...
2024-11-16T14:40:16.757819Z DEBUG vibe_core::transcribe: gpu device: 0
2024-11-16T14:40:16.757835Z DEBUG vibe_core::transcribe: use gpu: true
2024-11-16T14:40:16.757867Z DEBUG vibe_core::transcribe: creating whisper context with model path /home/user/.local/share/github.com.thewh1teagle.vibe/ggml-medium.en.bin
2024-11-16T14:40:16.757901Z  INFO whisper_rs::whisper_sys_tracing: whisper_init_from_file_with_params_no_state: loading model from '/home/user/.local/share/github.com.thewh1teagle.vibe/ggml-medium.en.bin'
2024-11-16T14:40:16.758059Z  INFO whisper_rs::whisper_sys_tracing: whisper_init_with_params_no_state: use gpu    = 1
2024-11-16T14:40:16.758081Z  INFO whisper_rs::whisper_sys_tracing: whisper_init_with_params_no_state: flash attn = 0
2024-11-16T14:40:16.758093Z  INFO whisper_rs::whisper_sys_tracing: whisper_init_with_params_no_state: gpu_device = 0
2024-11-16T14:40:16.758105Z  INFO whisper_rs::whisper_sys_tracing: whisper_init_with_params_no_state: dtw        = 0
2024-11-16T14:40:16.900715Z DEBUG whisper_rs::whisper_sys_tracing: ggml_vulkan: Found 1 Vulkan devices:
Segmentation fault (core dumped)
oleole39 commented 17 hours ago

This issue actually appeared in 2.6.5. Using same file, with same parameters and same model works fine in 2.6.4. As opposed to above log when it fires a seg fault error, 2.6.4 log shows the following (text between curly braces are comments):

Vulkan0: {Intel graphics} (Intel open-source Mesa driver) | uma: 1 | fp16: 1 | warp size: 32
2024-11-16T14:52:44.213334Z  INFO whisper_rs::whisper_sys_tracing: whisper_model_load: {Intel graphics} total size =  1533,14 MB
2024-11-16T14:52:58.752395Z  INFO whisper_rs::whisper_sys_tracing: whisper_model_load: model size    = 1533,14 MB
2024-11-16T14:52:58.760029Z DEBUG vibe_core::transcribe: created context successfuly
{etc.}

FWIW, note that: