[Bug] Application crashes with "std::bad_function_call" exception when loading existing chat

[Martinligabue]

Bug Report

The application crashes with a std::bad_function_call exception when attempting to load an existing chat. The console also logs several warnings related to tracking invalid responses, which occur both before and after the crash.

Steps to Reproduce

1. Launch the application.
2. Attempt to load an existing chat from a previous session.
3. Observe warnings in the console about invalid tracking responses (track invalid response and track response != 200).
4. The application throws an exception and crashes with the following message:

Qt has caught an exception thrown from an event handler. 
Throwing exceptions from an event handler is not supported in Qt. 
You must not let any exception whatsoever propagate through Qt code.
terminate called after throwing an instance of 'std::bad_function_call'
what():  bad_function_call

Console:

[Debug] (Sun Sep 15 21:42:46 2024): SingleApplication: Cannot communicate with primary so assuming primary status.
constructGlobalLlama: could not find Llama implementation for backend: cuda
constructGlobalLlama: could not find Llama implementation for backend: cuda
[Debug] (Sun Sep 15 21:42:47 2024): deserializing chat "/mnt/storage/ai/gpt4all-ebaed32d-113f-4503-8903-569c34752b11.chat"
[Warning] (Sun Sep 15 21:42:47 2024): ERROR: track invalid response.
[Warning] (Sun Sep 15 21:42:47 2024): ERROR: track response != 200 code: 0
[Warning] (Sun Sep 15 21:42:54 2024): ERROR: track invalid response.
[Warning] (Sun Sep 15 21:42:54 2024): ERROR: track response != 200 code: 0
[Warning] (Sun Sep 15 21:43:15 2024): ERROR: track invalid response.
[Warning] (Sun Sep 15 21:43:15 2024): ERROR: track response != 200 code: 0
[Warning] (Sun Sep 15 21:43:22 2024): Qt has caught an exception thrown from an event handler. 
terminate called after throwing an instance of 'std::bad_function_call'
what(): bad_function_call

The application crashes when loading an existing chat. The console logs repeated warnings about invalid tracking responses, followed by the std::bad_function_call exception.

This is consistent even with different chats and new ones too.

Expected Behavior

The application should handle exceptions within the event handler and load the existing chat without crashing.

Your Environment

• OS: Arch Linux
• Installation: Installed from AUR
• Application Version: 3.2.2-dev0
• Qt Version: 5.15.15 (installed in /usr/lib)
• Model: Llama 3 8B Instruct