All localhost plugins seem to be running up the Chrome CPU usage and crashing it, once there’s a response from the server. Even an empty or simple text response, including vanilla starter plugin example crashes immediately.
When I come re-open ChatGPT, the response from the crashed tab will show up under “New Chat” as the first message of the new chat. If I try to respond it’ll say “Conversation not found” or something similar.
Yup, I spent the whole day assuming I was doing something wrong in my openapi.yaml untill I finally tried firefox just to check my sanity, and Voila!
Hope this gets fixed soon…
Getting the same effect. I don’t think it is the custom APIs themself. All of the API calls on my end complete. But after GPT gets the data, it hangs for a little bit, then crashes.
Yeah it’s the GPT-Plugin model that’s crashing. If you monitor traffic, so see it receive it properly, and then it just jacks up GPU/CPU and Chrome kills it
Based on very limited testing, it seems if I open both the openai debugging tool AND chrome browser developer-tools debugger, my plugin seems to work, even after 5 calls. It had been crashing the browser immediately on response from the first call. Kinda awkward, the two debuggers take up a lot of screen real-estate, but at least I can continue working. We’ll see how long before a crash.
There seems to have been a UI update (the bottom left corner now expands to show settings). The tab has crashed after every plugin request since the update.
I just checked my network tab, and the call to the localhost API request responds as expected.
Then two calls to the OpenAI /conversation endpoint occur directly before the crash. Considering that erroneous conversations appear in my chat history, the bug probably has to do with these requests to /conversation.
@wfhbrian
posted this in the other thread by accident, but after refresh I just see a blank new chat window, no original input or edit or resubmit. Did I miss something?