Interesting, just to check something, do you have any users blocked? Don't need names, even if it's just one person a yes or no will do. Just to narrow it down.

Quoting: liamdaweInteresting, just to check something, do you have any users blocked? Don't need names, even if it's just one person a yes or no will do. Just to narrow it down.

Nope, no blocked user(s).

Okay, I did an adjustment for when you're hitting a notification. Can you re-test?

No, sorry ,still the same.

How long are we talking? For me it's practically instant.

OK, eventually something was still cached om my side, seems a lot faster now. Thanks!

Glad to hear it, as if it's fine my end then it can't have been the code, unless you did have hundreds of people blocked it had to remove posts for before displaying :)

No, sorry, it is still broken for new notifications. I guess the issue happens when first something needs to be updated in your database (marking a notification as read). It's not just seconds, the request seems to hang forever.

Since I have never encountered the issue and no one else has reported it, it's going to be hard to track down.

What browser and what plugins are you using?

Considering the amount of topics i end up following and the amount of notifications I get constantly, it's been tested extensively.

Edit: I just made a minor improvement to the handling. Who knows, maybe it will help.
Edit #2: Okay, I've made another adjustment that actually reduces the amount of MySQL queries it needs to do, by cutting one out completely.

Thanks, I'll report back. I don't get that much notifications :)
To clarify: I never had this before I changed my paging settings, so quite sure it's related to that.

PS: I do see notifications in the notification center for regular threads, but not from the forum here. is this correct? I'm "subscribed without e-mail".

Let me know how you get on, I'm constantly getting them and the entire page loads and displays everything within seconds for me.

The notification system is not integrated with the forum yet, waiting until I'm completely happy with it first.

No, sorry, the problem is still there. must be something different :(
Can you see some long running requests or queries on your side?

It's standard Chrome with Adblock disabled for this site.

Well it's not doing anything heavy and i'm really surprised, even on my mobile net on my phone it's fast.

If multiple others report the same thing, then I can take a look again. For now ill have to sit on it sinve it never happens to me and even on my slower net on my mobile its fine. :(

Sorry.

Just to be sure, are you using similar paging settings like me (Comments & forum posts per-page: 50
Articles per-page, for homepage and category (tag) view: 25). These hanging requests started after I changed my preferences to that numbers.

Yes exacrly the same settings.

I just tested on my mobile net, while its downloading (so its slow) and a new notification loaded the actual page in about 3 seconds.

mmh, weird indeed. As I said, it's not slow, the request stalls completely and never finishes. While a request hangs I can't even open your front page in a new tab. That request hangs too. Like a deadlock on the session or similar. A browser restart is the only solution.

Quoting: jensmmh, weird indeed. As I said, it's not slow, the request stalls completely and never finishes. While a request hangs I can't even open your front page in a new tab. That request hangs too. Like a deadlock on the session or similar. A browser restart is the only solution.

Ah, i was going by slow loading not a deadlock. To me that sounds like a browser issue, never once encountered that anywhere on GOL.

Only thing I can think of is to have the F12 menu open, with the console tab open and see if anything interesting comes up there.

I already did that. Nothing strange there. I see a
"Uncaught TypeError: Cannot read property 'getEditor' of undefined
at a (ckeditor.js:344)
at Object.CKEDITOR.replace (ckeditor.js:348)
at 2984:1133"
but that seems unrelated.

My guess would be a database deadlock somewhere since I seem to experience this only in combination with a write action into the db ("mark notification as read", "set last login date" or "edit a post"). But indeed strange that I seem to be the only one experiencing this. Could be that I'm the only "normal" user using this paging settings ;). Your user account has certainly a different user role than mine. Eventually that make a difference too.

If there was a deadlock in the DB it would affect everyone regardless of the setting. It sounds like an issue your end.

Try a different browser for a while and if you dont see the issue that will say it all.

User role has nothing to do with this issue, it runs the same for each of us.

No, a deadlock in a database should affect only the participating transactions. But of course no idea if you actually use transactions. Dunno if this is a db-deadlock, just the symptoms seem similar. From my experience I'm pretty sure this is a server-side issue. My browser fires the request, but the request times out.

Anyway, I understand that this one seems difficult to track down, lets see if somebody else experiences this. It took me a few months until I reported it here since this is annoying behavior, but with a workaround.