Live data from Hacker News

The longer my convo with ChatGPT, the more processing power is consumed

news.ycombinator.com

1–7 of 7 posts

Re: The longer my convo with ChatGPT, the more processing power is consumed

#4

Might be the javascript on the page

sure, but why would the JS not be scalable? Seems like a flaw on the frontend. The app is very simple and should not heat up an M3.

It's definitely a memory leak from the conversation API. It seems to keep track of browser state and to limit computation on their end based on the 'active' tab.

Re: The longer my convo with ChatGPT, the more processing power is consumed

#5

Earlier quoted context omitted.

sure, but why would the JS not be scalable? Seems like a flaw on the frontend. The app is very simple and should not heat up an M3.

It's definitely a memory leak from the conversation API. It seems to keep track of browser state and to limit computation on their end based on the 'active' tab.

Do you have a source for that?

Re: The longer my convo with ChatGPT, the more processing power is consumed

#6

Earlier quoted context omitted.

It's definitely a memory leak from the conversation API. It seems to keep track of browser state and to limit computation on their end based on the 'active' tab.

Do you have a source for that?

My browser

Re: The longer my convo with ChatGPT, the more processing power is consumed

#7

Earlier quoted context omitted.

sure, but why would the JS not be scalable? Seems like a flaw on the frontend. The app is very simple and should not heat up an M3.

It's definitely a memory leak from the conversation API. It seems to keep track of browser state and to limit computation on their end based on the 'active' tab.

You nailed it! I think Openai Team needs to patch it.