While you're here, please consider supporting GamingOnLinux on:
Reward Tiers: Patreon. Plain Donations: PayPal.
This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!
You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Reward Tiers: Patreon. Plain Donations: PayPal.
This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!
You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Login / Register
- Founder of Baldur's Gate 3 developer blasts publisher greed
- Proton 9.0 (Beta16) brings more regression fixes, updated Steamworks SDK
- Windows compatibility layer Wine 9.5 released
- Backpack Battles has sold 500,000 copies in two weeks on Steam
- System76 release upgraded Lemur Pro laptop, plus a desktop sale now on
- > See more over 30 days here
-
The Triple-i Initiative gaming showcase is coming April…
- Pengling -
Oh Snap! Canonical now doing manual reviews for new pac…
- redneckdrow -
EA anticheat arrives for Battlefield V in April, will b…
- hell0 -
EA anticheat arrives for Battlefield V in April, will b…
- Purple Library Guy -
SDL 3 will prefer Wayland Over X11, if certain protocol…
- nwildner - > See more comments
Latest Forum Posts
- Probably quite slow for the next 9 days
- redneckdrow - How to find out if a game is native for sure?
- Myrhan - Logitech G29 steering wheel - Snowrunner support
- njasd2w - Weekend Players' Club 3/22/2024
- Pengling - Nintendo-style gaming, without Nintendo!
- Linux_Rocks - See more posts
Could you please give chrome a shot and report if you still got that issue? I would feel better if someone would at least confirm that I'm not going nuts :)
Currently clearing a notification and redirecting to a specific comment are done in the same page that renders an article. What i will do is split them up into two files. So we will have one to render that article as normal and one to actually do the notification clearing and redirect.
This way I can track down easier where the stall is coming from.
@liamdewe, thanks a lot for keeping keen to track this down. Note that I got this also when editing one of my posts in a longer thread on pages other than the first page (only with editing, never with initially posting). The editing itself is successful, but the redirect to the thread results in 5 minutes waiting for a response.
I've done an adjustment that might help, let me know.
Essentially, I wasn't doing a "die()" after sending the redirect header in php to send you to the correct comment. This results in the rest of the entire article rendering page still executing (possibly then stalling somehow). I've added them in, which should stop any unexpected behaviour.
Clicking on a notifications link seem fine now and even much faster. I'll keep an eye out and report back.