-
Notifications
You must be signed in to change notification settings - Fork 10.2k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fix memory allocation issues and seg faults
- Loading branch information
Showing
1 changed file
with
16 additions
and
18 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
4870e45
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not sure how to trace it correctly, but it still segfaults for me, using alpaca model
4870e45
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok found out that tensor type become invalid at that point
4870e45
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
also found out it always crash here when n_past reach 513
4870e45
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
still segfaults,
ggml_new_tensor_impl: not enough space in the context's memory pool (needed 537102496, available 536870912)
zsh: segmentation fault ./main -m ./models/65B/ggml-model-q4_0.bin -t 16 -n 256 --repeat_penalty 1.0
It was fixed but I guess it reappeared?
4870e45
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Never had any segfaults but after this I do. :(
ggml_new_tensor_impl: not enough space in the context's memory pool (needed 537029792, available 536870912)
Edit: Always starts off fine for a bit, then after a handful of responses it happens.
4870e45
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems to have broken --perplexity as well, runs out of memory on the first batch.