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

CatAI crashes when quitting a browser or when starting CatAI when a browser is already open. #29

Closed
TheSystemGuy1337 opened this issue Jul 11, 2023 · 10 comments
Labels
bug Something isn't working

Comments

@TheSystemGuy1337
Copy link

Please refer to the troubleshooting before opening an issue. You might find the solution there.

Describe the bug
CatAI really doesn't like having the browser be open when you start it. If you attempt to start CatAI with the browser open, it prints this out to the terminal

..................../home/thesystemguy/.nvm/versions/node/v20.2.0/lib/node_modules/catai/node_modules/openurl/openurl.js:39
throw error;
^

Error: Gtk-Message: 00:49:11.085: Failed to load module "xapp-gtk3-module"
[2:2:0711/004911.245184:ERROR:nacl_fork_delegate_linux.cc(313)] Bad NaCl helper startup ack (0 bytes)
Gtk-Message: 00:49:11.272: Failed to load module "xapp-gtk3-module"

at Socket.<anonymous> (/home/thesystemguy/.nvm/versions/node/v20.2.0/lib/node_modules/catai/node_modules/openurl/openurl.js:35:25)
at Socket.emit (node:events:525:35)
at endReadableNT (node:internal/streams/readable:1359:12)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21)

Node.js v18.16.0
at file:///home/thesystemguy/.nvm/versions/node/v20.2.0/lib/node_modules/catai/scripts/cli.js:69:27
exit code: 1

A reinstallation nor reboot does not fix this issue. This issue cropped up after Google Chrome broke and Firefox assumed itself as the default browser and I changed the settings.

Screenshots
n/a

Desktop (please complete the following information):
OS: Linux Mint 21.1 Cinnamon, Linux 5.15.0-76-generic
Browser: Google Chrome
CatAI version 0.3.12
Node.js version v18.16.0
CPU: AMD Ryzen 5 5600H with Radeon Graphics
RAM: 30.7 GiB (512 MiB reserved to graphics chipset)

@TheSystemGuy1337 TheSystemGuy1337 added the bug Something isn't working label Jul 11, 2023
@ido-pluto
Copy link
Collaborator

You can disable the open in browser feature vis environment variable, check the config.
I will try to see if there is a workaround to prevent CatAI from crashing after failing to open the browser.

@TheSystemGuy1337
Copy link
Author

TheSystemGuy1337 commented Jul 11, 2023 via email

@ido-pluto
Copy link
Collaborator

Supposed to work on the latest version, is the problem fixed?

npm install -g catai@1.0.2

@TheSystemGuy1337
Copy link
Author

TheSystemGuy1337 commented Jul 19, 2023 via email

@TheSystemGuy1337
Copy link
Author

Trying to run catai update works, but yields same result.

fatal runtime error: Rust cannot catch foreign exceptions
Aborted (core dumped)
fatal runtime error: Rust cannot catch foreign exceptions
Aborted (core dumped)
at file:///home/thesystemguy/.nvm/versions/node/v20.2.0/lib/node_modules/catai/scripts/cli.js:69:27
exit code: 134 (Process aborted)

@TheSystemGuy1337
Copy link
Author

Reinstalling does this
llama.cpp: loading model from /home/thesystemguy/catai
fatal runtime error: Rust cannot catch foreign exceptions
Aborted (core dumped)
llama.cpp: loading model from /home/thesystemguy/catai
fatal runtime error: Rust cannot catch foreign exceptions
Aborted (core dumped)
at file:///home/thesystemguy/.nvm/versions/node/v20.2.0/lib/node_modules/catai/scripts/cli.js:69:27
exit code: 134 (Process aborted)

@ido-pluto
Copy link
Collaborator

I did upgrade the node-llama version (this is the binding to the model)

@TheSystemGuy1337
Copy link
Author

TheSystemGuy1337 commented Jul 19, 2023 via email

@ido-pluto
Copy link
Collaborator

CatAI now uses a custom lib - develop by the CatAI team.
Can you try to update and use one of the models listed in catai ls?

@TheSystemGuy1337
Copy link
Author

The install failed, mainly as you didn't specify sudo.

Even after that small blunder and having to upgrade NodeJS from 18 to 20 using insane command line nonsense, it bloody works now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants