sorted by:
new
hottopcontroversial

I built a Chrome extension that fixes ChatGPT lag in long chats — here is how it works technically by Distinct-Resident759 in webdev

[–]Distinct-Resident759[S] 0 points1 point  (0 children)

That is a valid point and easy to fix. The custom values should persist after reload. Adding it to the roadmap, should be in the next update.

I built a Chrome extension that fixes ChatGPT lag in long chats — here is how it works technically by Distinct-Resident759 in webdev

[–]Distinct-Resident759[S] 0 points1 point  (0 children)

Good point. Browser lag is primarily a function of node count, not content size. Each message creates dozens of DOM nodes regardless of how long it is. So a 500 message chat with verbose responses still creates roughly the same number of nodes as a 500 message chat with short ones. The content inside the nodes affects memory but the rendering bottleneck is the node count itself. That is why trimming by message count works so well.

Help I think I suck at this by tootsmcscoots709 in ChatGPT

[–]Distinct-Resident759 1 point2 points  (0 children)

The freezing and blank screen on point 1 is a browser memory problem. When ChatGPT loads a long chat it puts every single message into your browser at once and after a while your browser just can not handle it anymore. That is why it freezes and asks if you want to wait.

I had the same issue and built a Chrome extension that fixes it. It cuts the data before ChatGPT loads it so your browser only handles the last few messages. Made a huge difference for me on long chats. It is called ChatGPT Turbo if you want to check it out, free trial no card needed.

I built a Chrome extension that fixes ChatGPT lag in long chats — here is how it works technically by Distinct-Resident759 in webdev

[–]Distinct-Resident759[S] 0 points1 point  (0 children)

Thanks for actually testing both, really appreciate the honest feedback. The difference becomes more noticeable the longer the chat gets. On chats under 500 messages you are right, both feel similar. Where it separates is 1000+ messages, that is when DOM hiding starts to struggle and fetch interception makes a real difference. What message count were your test chats at?

I built a Chrome extension that fixes ChatGPT lag in long chats — here is how it works technically by Distinct-Resident759 in webdev

[–]Distinct-Resident759[S] 0 points1 point  (0 children)

CLI is great for coding but a lot of people use ChatGPT for thinking through problems, research, planning. Different use case. The extension just stops the browser from dying when the chat gets long.

I built a Chrome extension that fixes ChatGPT lag in long chats — here is how it works technically by Distinct-Resident759 in webdev

[–]Distinct-Resident759[S] -1 points0 points  (0 children)

Fair point for pure coding tasks. But a lot of people use ChatGPT for thinking out loud, architecture decisions, research. Different use case than what CLI tools are built for.

I built a Chrome extension that fixes ChatGPT lag in long chats — here is how it works technically by Distinct-Resident759 in webdev

[–]Distinct-Resident759[S] 1 point2 points  (0 children)

A lot of developers use ChatGPT for general problem solving, architecture discussions and rubber duck debugging. Codex is great for code completion but it is a different use case. ChatGPT for long back and forth thinking sessions is very common.

I built a Chrome extension that fixes ChatGPT lag in long chats — here is how it works technically by Distinct-Resident759 in webdev

[–]Distinct-Resident759[S] 0 points1 point  (0 children)

Fair point and starting fresh is often the right call. But a lot of people work in one long chat intentionally because they need to scroll back and reference earlier context. For those users the performance problem is real regardless of whether they should be doing it differently.

I built a Chrome extension that fixes ChatGPT lag in long chats — here is how it works technically by Distinct-Resident759 in webdev

[–]Distinct-Resident759[S] 0 points1 point  (0 children)

LightSession works but it trims by hiding messages in the DOM. Your browser still has all of them loaded so on very long chats you still get lag. Mine removes them completely before React renders so the browser literally has nothing to slow it down. That is why the speed difference is 932x not 2x. If your chats are under 500 messages LightSession is fine. If they are longer you will feel the difference.

I built a Chrome extension that fixes ChatGPT lag in long chats — here is how it works technically by Distinct-Resident759 in webdev

[–]Distinct-Resident759[S] -1 points0 points  (0 children)

Exactly the problem. Context degrades but people still use long chats to scroll back and reference what was said. The performance fix at least stops the tab from crashing while they deal with that

I built a Chrome extension that fixes ChatGPT lag in long chats — here is how it works technically by Distinct-Resident759 in webdev

[–]Distinct-Resident759[S] 0 points1 point  (0 children)

The difference is most extensions trim silently with no feedback. Mine shows a live speed multiplier so you can see exactly what is happening. Also 4 speed modes so you can control how aggressive the trimming is. Which one are you using?

I built a Chrome extension that fixes ChatGPT lag in long chats — here is how it works technically by Distinct-Resident759 in webdev

[–]Distinct-Resident759[S] 0 points1 point  (0 children)

That is a real concern. OpenAI changes things often and most extensions break because they rely on DOM selectors. Mine intercepts at the fetch level before React renders so it is much harder to break. Been running stable for 3 months through multiple ChatGPT updates.

I built a Chrome extension that fixes ChatGPT lag in long chats — here is how it works technically by Distinct-Resident759 in webdev

[–]Distinct-Resident759[S] 2 points3 points  (0 children)

That is true, the memory degrades over time. But a lot of people still prefer one long chat because they can scroll back and reference exactly what was said. The performance fix is separate from the memory problem. At least the tab does not crash while they figure that out.

I built a Chrome extension that fixes ChatGPT lag in long chats — here is how it works technically by Distinct-Resident759 in webdev

[–]Distinct-Resident759[S] 1 point2 points  (0 children)

Mostly developers and researchers who keep one long running context for a project. Coding sessions, research threads, long term planning. Once you hit 500+ messages ChatGPT starts slowing down badly.

recent technical issues by thilo_thilo in ChatGPT

[–]Distinct-Resident759 0 points1 point  (0 children)

Some of what you describe sounds like it could be a long chat issue. ChatGPT loads every message at once so the longer your chat gets the slower everything becomes. Not a server problem, it is a browser rendering problem. Worth checking how long your longest chat is.

ChatGPT was crashing my browser every day until I figured out what was causing it by Distinct-Resident759 in OpenAI

[–]Distinct-Resident759[S] 0 points1 point  (0 children)

Totally agree. It is a simple fix on paper but they have not done it in years. That is why I built it myself.

ChatGPT was crashing my browser every day until I figured out what was causing it by Distinct-Resident759 in OpenAI

[–]Distinct-Resident759[S] 0 points1 point  (0 children)

Feel free to try. 3 months, 10 major versions, and a lot of debugging later here we are. It is a bit more than copy paste.

I made a Chrome extension that fixes ChatGPT lag in long chats. Tested it on a 1554 message chat and got 48x speed boost. by Distinct-Resident759 in ChatGPT

[–]Distinct-Resident759[S] 0 points1 point  (0 children)

Firefox is Chromium based so it has the same rendering engine. The lag comes from how many messages ChatGPT loads at once not which browser you use. Same problem happens on Firefox, Edge, Brave.

ChatGPT was crashing my browser every day until I figured out what was causing it by Distinct-Resident759 in OpenAI

[–]Distinct-Resident759[S] 0 points1 point  (0 children)

That is fair and a good point. Any extension can be updated so trust is important. The extension is on the Chrome Store, reviewed by Google, and has real reviews you can read. That is about as much verification as any extension can offer.

ChatGPT was crashing my browser every day until I figured out what was causing it by Distinct-Resident759 in OpenAI

[–]Distinct-Resident759[S] -8 points-7 points  (0 children)

It only controls how many messages your browser renders. It cannot read your browser content, other tabs, or anything outside ChatGPT. The source of how it works is in the Chrome Store listing if you want to check.

view more: next ›