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

The operation failed for an operation-specific reason #170

Closed
TechGeekUnited opened this issue Aug 4, 2023 · 1 comment
Closed

The operation failed for an operation-specific reason #170

TechGeekUnited opened this issue Aug 4, 2023 · 1 comment

Comments

@TechGeekUnited
Copy link

I Had the same issue with WEBSD when i switched to canary WEBsd Worked but WEBllm still gives the error frequently(Image attached)
Screenshot 2023-08-04 144404

@patnorris
Copy link
Contributor

While the smaller model (RedPajama-INCITE-Chat-3B-v1-q4f32_0) has been working smoothly for me, I'm observing similar errors as reported for Llama-2-7b-chat-hf-q4f32_1. I also tried vicuna-v1-7b-q4f32_0 which worked fine for a message or two until I opened another browser tab (the screen went black and then got "GPU connection lost", "OperationError: The operation failed for an operation-specific reason" and "DOMException: Device is lost") which makes me think that maybe my device cannot handle the needed memory for WebGPU that these bigger models demand. From some initial research about the errors, I also found comments that the browser throws them when it cannot allocate enough memory to WebGPU. Could this be the reason? Do you know of any potential way this could be solved?

@tqchen tqchen closed this as completed May 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants