-
Notifications
You must be signed in to change notification settings - Fork 10.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
finetune: terminate called after throwing an instance of 'std::bad_alloc' #4389
Comments
Can confirm that this is happening with current build using CUDA. Same setup with current llama.cpp pull as this: But now I get the
as original poster. |
I am getting the same error. Is there any fix ? |
I've got it working on this commit (built via makefile), but only if I don't offload to the GPU (idk if this is relevant here).
Inference on the GPU still works with the workaround commit. |
Same error as above using the commit when trying to finetune |
Yes, indeed,
Yes, I get the same. It's the other issue that @jooray linked above. |
Can you test if #4486 fixes all the issues? |
thank you for the quick patch, it does indeed fix "std::bad_alloc" as I do now get to the training part. There it now crashes with a new/different error message.
The error seem similar to #4212 (should we move the discussion over there?) I've tried it with a |
The fix is only for the bad_alloc issue, training on the GPU is not currently supported. It may work with a f16 model, but I am not sure that you will get anything from it. |
Could be useful to add to readme that fine tuning on GPU is not supported.
|
I have the same error. This guide suggests that it is possible to finetune on gpu, but I can't figure out how. |
I get the same error trying to fine tune with NO GPU (w64devkit\w64devkit.exe).
|
Which commit are you on, do you have #4486? How much memory do you have ? This error could also just mean you tried allocating too much. If not, you could consider opening a new issue. In any case, you probably don't want to use llama.cpp for any serious finetuning at this point, I think it's meant more as a demo. |
Yes, in my case it was probably allocating more memory than available. I just closed browser and VS code and finetune continued without error. |
Prerequisites
Please answer the following questions for yourself before submitting an issue.
Environment and Context
Failure Information (for bugs)
finetune fails with "terminate called after throwing an instance of 'std::bad_alloc'"
Steps to Reproduce
Please provide detailed steps for reproducing the issue. We are not sitting in front of your screen, so the more detail the better.
Failure Logs
The text was updated successfully, but these errors were encountered: