lmstudio-ai / lmstudio-ai/lmstudio-bug-tracker

App quit without notice if disk full: Uncaught Exception: Error: ENOSPC: no space left on device, write

Open
#232 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
152
Forks
38
PR merge metrics
No merged PRs in 30d

Description

If the disk is full while downloading a model, app will quit (crash?) without any notice. No crash dump is generated. Here's the console output:
```
[GGUFMetadataProvider] Returning cached GGUF metadata for /Volumes/Data/LM Studio/models/lmstudio-community/Mistral-Large-Instruct-2407-GGUF/Mistral-Large-Instruct-2407-Q2_K.gguf
[GGUFMetadataProvider] Returning cached GGUF metadata for /Volumes/Data/LM Studio/models/lmstudio-community/gemma-2-27b-it-GGUF/gemma-2-27b-it-Q6_K.gguf
[GGUFMetadataProvider] Returning cached GGUF metadata for /Volumes/Data/LM Studio/models/lmstudio-community/mathstral-7B-v0.1-GGUF/mathstral-7B-v0.1-Q8_0.gguf
[GGUFMetadataProvider] Returning cached GGUF metadata for /Volumes/Data/LM Studio/models/lmstudio-community/Meta-Llama-3.1-70B-Instruct-GGUF/Meta-Llama-3.1-70B-Instruct-Q3_K_S.gguf
[GGUFMetadataProvider] Returning cached GGUF metadata for /Volumes/Data/LM Studio/models/RichardErkhov/Qwen_-_Qwen2-Math-72B-Instruct-gguf/Qwen2-Math-72B-Instruct.Q3_K_M.gguf
[ModelIndexProvider][Op-1] Finished indexing operation on directory: /Volumes/Data/LM Studio/models
23:18:11.710 › LM Studio dev tools v0.0.27 exist
23:18:11.710 › LM Studio dev tools are not present, copying them over to .cache/lm-studio/bin...
23:18:12.099 › Uncaught Exception: Error: ENOSPC: no space left on device, write
23:18:12.099 › Exception : Error: ENOSPC: no space left on device, write
```

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file, test, or entry point is identified in the report. Start by reproducing a model download with the disk full and trace the ENOSPC error; done means the app remains open and gives the user a clear notice instead of quitting silently.

Written by the indexing model from the issue text.

Assessment

Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.