Skip to content
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

GGML Assert error #428

Closed
ADXXI1590 opened this issue May 23, 2023 · 5 comments
Closed

GGML Assert error #428

ADXXI1590 opened this issue May 23, 2023 · 5 comments
Labels
bug Something isn't working primordial Related to the primordial version of PrivateGPT, which is now frozen in favour of the new PrivateGPT

Comments

@ADXXI1590
Copy link

GGML_ASSERT: C:\Users\circleci.PACKER-64370BA5\project\gpt4all-backend\llama.cpp\ggml.c:4411: ctx->mem_buffer != NULL
not getting any prompt to enter the query?
instead getting the above assertion error? can anyone help with this?

@ADXXI1590 ADXXI1590 added the bug Something isn't working label May 23, 2023
@Om-GG
Copy link

Om-GG commented May 23, 2023

I have the same issue.

@jhoughtelin
Copy link

Increase the amount of memory available. I had the same issue trying to run the python binding of gpt4all. It worked after I provisioned a system with more than 16G of memory.
Slightly different but #90 is also suggesting that the system does not have enough memory.

@Om-GG
Copy link

Om-GG commented May 25, 2023

Yep, I gave it 8 gb and it started moving, good to know that 16 may be a good number to aim for. It doesn't seem that 8gb would be anywhere near enough, as it moves quite slowly and takes a long time to reply to queries.

@rwcitek
Copy link

rwcitek commented Jun 4, 2023

I had the same issue.

I was using a 2 GB cloud instance to build a Docker image with privateGPT. The build worked. Here's a link to the Dockerfile:

https://github.com/rwcitek/privateGPT/blob/docker/docker/Dockerfile

However, when I tried to run privateGPT.py in the instance, it would core dump. Changing the cloud instance to 16GB enabled the container to run. This is the Docker run command that I used:

docker run --rm -it rwcitek/privategpt:2023-06-04 python3 privateGPT.py

Since I did my development using GitHub CodeSpaces, I modified my devcontainer.json file to specify 16GB.

https://github.com/rwcitek/privateGPT/blob/docker/.devcontainer/devcontainer.json

I have not tried it on anything between 2 GB and 16 GB.

@selcukbeyhan
Copy link

same error. I saw multiple reports of this issue:
#90
#186

Is this something part of the model? or something related to this "circleci" user "C:\Users\circleci.PACKER-64370BA5"?

@imartinez imartinez added the primordial Related to the primordial version of PrivateGPT, which is now frozen in favour of the new PrivateGPT label Oct 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working primordial Related to the primordial version of PrivateGPT, which is now frozen in favour of the new PrivateGPT
Projects
None yet
Development

No branches or pull requests

6 participants