I can reproduce this in chromium. Clicking a link on the notifications page almost always causes chromium to go on strike and stop loading pages altogether. The browser has to be restarted or it won't load any URL at all. I've never seen this happen in Firefox.

The only thing I had to do was open up my notifications page and click one of the links. Didn't seem to matter if the link was unread. It happens reliably at the highest posts per page setting, but I got it to trigger with only 30 posts per page after a couple of successful page loads. Something about these links makes that particular browser engine choke.

No time to dig into this further (it's three in the morning for me), but just wanted to confirm it's not just jens.

Quoting: tuubithe only thing I had to do was open up my notifications page and click one of the links. Didn't seem to matter if the link was unread. It happens reliably at the highest posts per page setting, but I got it to trigger with only 30 posts per page after a couple of successful page loads. Something about these links makes that particular browser engine choke.

Thanks for confirming. Yes, you are correct. It doesn't has to be an unread notification, sorry, that was a false positive from my side.

I tried Firefox just now. First time I could reproduce it there too. Login and then just click on the first (already read) link in the notification center and the browser keeps loading forever. Second time after a browser restart everything was fine. Strange indeed.

Quoting: jensI tried Firefox just now. First time I could reproduce it there too. Login and then just click on the first (already read) link in the notification center and the browser keeps loading forever. Second time after a browser restart everything was fine. Strange indeed.

I've seen GOL stop responding for a few minutes every now and then, yesterday and this morning as well, but I assumed it was something else. And I'm still not sure it's related as it seems more random and always starts working again after a while. Affects only GOL so I assumed the server just wasn't responding for some reason. I'll have to keep an eye on whether it only happens when I'm clicking the notification links or if it is purely random.

Liam, you might want to spend a bit of time perusing the server logs (mysql and apache at least) for anything suspicious. The blackouts are a bit alarming, unless they're caused by you working on the server.

This is strange since I never encounter the issue.

I use Chrome on my phone and Firefox on desktop and don't see a thing.

Will install chromium on the desktop and see if I can reproduce that way.

In future, if you do see it happen I need exact times to help find it for you.

Edit: Here's a test for you, for the notification that stops working. Find the post, click the link icon (the one with the permalink for the comment) and see if that link does the same.

I have tested the following urls between 16:50 and 17:20 CEST
https://www.gamingonlinux.com/articles/heres-a-look-at-some-good-fps-games-available-on-linux-steamos.10447/comment_id=105656
https://www.gamingonlinux.com/articles/heres-a-look-at-some-good-fps-games-available-on-linux-steamos.10447/comment_id=105643
https://www.gamingonlinux.com/articles/heres-a-look-at-some-good-fps-games-available-on-linux-steamos.10447/comment_id=105597
https://www.gamingonlinux.com/index.php?module=articles_full&aid=10447&comment_id=105597&clear_note=51521
https://www.gamingonlinux.com/index.php?module=articles_full&aid=10447&comment_id=105643&clear_note=51586
https://www.gamingonlinux.com/index.php?module=articles_full&aid=10447&comment_id=105656&clear_note=51690
Test pattern was always the same: Open a new Google Chrome window (with no other windows open), paste the url into the address bar and press enter.

I see the hanging requests for both types of urls, permalink and the generated one from the notification center. Though not always, I fail to see a pattern yet :(. Kind of strange is that it takes quite some time until I see something in network tab of the chrome, though I see "waiting for www.gamingonlinux.com" in the status bar.

Edit:
I have waited quite some time, several minutes, for a link in the notification tab and the network tab shows repeatedly:
https://www.gamingonlinux.com/includes/ajax/update_notifications.php Status (pending)
and finally a
https://www.gamingonlinux.com/articles/heres-a-look-at-some-good-fps-games-available-on-linux-steamos.10447/page=2 504 Gateway timeout
Edit2:
Waiting for a permalink also ends with a 504 Gateway timeout.

Do you have load-balancer with a failing node or something similar?
Hope this helps.

Honestly I've never seen it, my host has now tested on an account with the same settings and doesn't see anything either.

I'm at a complete loss here.

Okay, my host has asked if you can reproduce it now. Let me know.

Hi, seems OK now, I can't reproduce it anymore.
I used the same procedure, open a new browser and paste+go a random url from the ones I mentioned and repeated this several times. Every time I got nicely redirected to the corresponding message.

May I ask what has changed?

Disabled PHP-FPM to see if that was the issue, they are investigating further.

Do keep testing if you can, let me know if/when it returns.

Thanks a lot for the follow-up. Seems good so far. I'll report back when this issue reappears.

Still all good here, please keep the changed php-settings! Makes navigation so much easier :)

Great, will mark as solved.

Hi Liam,

This is issue is back. Did your provider reverted the php settings? ;)

Regards,
Jens

Keep an eye out, I've changed a bunch today code-wise that should hopefully sort this.

The stalled requests are still there..

Quoting: jensThe stalled requests are still there..

Okay, so to re-confirm, the page just seems to infinite load or you get to some sort of time out. And it's only when clicking a notification?

Next time it happens, please screenshot and post it here.

I have this every time now. Like it was before and like tuubi has described it too. Just click on a notification for a long thread. One thing is different though. After exactly 5 minutes of waiting the requests successfully completes, so no longer gateway timeout anymore.

Happens with Chrome for me sometimes (haven't tested that long since its not my main browser).

Never seen it with Vivaldi, Opera (though they use same engine) and Firefox.