Meet the Other Phone. A phone that grows with your child.

Meet the Other Phone.
A phone that grows with your child.

Buy now

Please or to access all these features

Site stuff

Join our Innovation Panel to try new features early and help make Mumsnet better.

See all MNHQ comments on this thread

Page freezing/ Edge, only this site affected

67 replies

GeneratedRandomly · 06/12/2022 12:23

This only happens on MN.
Using Edge on W10 laptop.
I am reading a thread, it is too long to finish so I leave the page open for when I return.
I return and the page just stays solidly in place, will not scroll. I have to refresh, then I get a page with options to wait or leave. I select leave because wait does nothing but wait and wait and wait. It then lets me refresh and allows me back to the page.
I changed a setting on Edge and it was OK, then there was an update and now it is doing it again.
I am getting tired of it now, as I said above it is only on this site.

OP posts:
thewinterwitch · 18/12/2022 13:16

Oh my god. This has been driving me crazy for months. Also on edge. Ever since the upgrade, I think. I thought it was just something weird with my computer. Not much better in terms of freezing the whole thing up on chrome.

Sigma33 · 18/12/2022 17:25

God this site is buggy

Using Edge

Have endless problems with threads over about 100 posts, and quoting posts is hit and miss for just about all threads

notthe1Parrot · 18/12/2022 19:43

Further to my post of about a week ago, I changed to 50 posts/page. This worked, so after a couple of days I moved to 100posts/page.

So far, so good ... Fingers crossed....

SnowlayRoundabout · 21/12/2022 00:20

LilyMumsnet · 06/12/2022 16:44

Hi all

Please can we check how many posts per page you are viewing when this happens?

Why does this matter? Before you revamped the site, it could cope fine with pages with 1000 posts on. Literally months ago you told me on another similar threat that you were dealing with this, but it's as bad as ever. And, for what it's worth, I'm on Safari, not Edge. I really don't want to have to change my settings to 100 posts per page because it's a total pain in the neck.

HebeMumsnet · 21/12/2022 10:25

Morning! We are sorry this still isn't resolved. We are still looking into it. In the meantime, for anyone just arriving on the thread who might have missed it, here are a few things to try:

  1. The issue for the majority of people will be the posts per page so if you can set that to 25 (or 50 if that works for you) that will solve the problem for many. Make sure you have saved your preferences properly - we've had lots of people think they're on 25 posts per page but are actually still on 1000.
  2. If you've already done that, try clearing your cache.
  3. If you're not using Chrome, try switching to that as it seems to be the most effective browser for avoiding the issue of freezing threads.
  4. Antiviral software may be causing this for some. Have a look here if you're getting a 'fatal memory exceeded' message: https://www.chromestory.com/2020/06/sbox-fatal-memory-exceeded/.
  5. If none of that works, let us know what device and browser you are using, how much RAM you have and whether you're on the app or the site and we'll take a look

Thank you for your patience. Flowers

ShowOfHands · 21/12/2022 16:34

I've been on 1000 posts per page since I joined nearly 2 decades ago and it's always coped on much slower and less sophisticated devices. It's been since the upgrade and anything above around 50 posts. And even those threads are slow to load.

I don't want to use a page view.

tribpot · 21/12/2022 17:29

I think your devs are giving you the run around on that memory exceeded error @HebeMumsnet - just because it can be caused by an anti virus program doesn't mean it is. I reported it and I am definitely not using the one mentioned in the article. The article also notes that it can be caused by a website with a memory leak and that's certainly what this looks like. It might load initially but then if you come back to the tab later it's crashed. It could have something to do with modern browsers putting unused tabs to sleep to save power - I noticed that Task Manager was reporting Edge as consuming a LOT of power whenever the MN tab was active.

GeneratedRandomly · 04/02/2023 11:55

Just to update on this issue. It is still crap. In fact it has got worse. I believe it is to do with the gigantic ads that infest the site.

I have had enough of it, truly. It is just a heap of crap. I have everything set as suggested but it takes too much of my life waiting for it to condescend to start working every time I open it after a break so am spending less time bothering with reading threads.

I don't know if Premium users also get this, but am not going to try it to find out.

OP posts:
ShowOfHands · 04/02/2023 17:23

I'm a Premium user and the problem is exactly the same. No ads and the same lag, crashing constantly, taking forever to load, freezing, floating menu bars, unresponsive pages. It's not an ad thing.

GeneratedRandomly · 04/02/2023 18:06

ShowOfHands · 04/02/2023 17:23

I'm a Premium user and the problem is exactly the same. No ads and the same lag, crashing constantly, taking forever to load, freezing, floating menu bars, unresponsive pages. It's not an ad thing.

Thank you for clarifying that. I have never known such a badly maintained site, ever. I thought Ebay was bad but at least they fixed the issues.

OP posts:
tribpot · 04/02/2023 19:38

I have to say, I have found it a lot more manageable since I went to paginated threads. Few sites I think allow users to interact with such massively long pages as a 1000 post thread (poss with pics etc). However, if this is what the problem is, MN need to front up and just say sorry, you have to paginate now (all new users do anyway).

Even paginated, when I came back to this tab to finish this post, it still struggled a bit to render it. I do think the enormous ads are part of the problem, I'm not sure how it works for the Premium users but the ads could be loaded into the page and then not displayed?

Patineur · 04/02/2023 19:43

This site managed previously absolutely fine with 1000 post threads. And MN have been promising us for months that they were going to sort this out. I had paginated threads when I started, I found it amazingly annoying, especially when I wanted to check back on a particular post and didn't know which page it was on.

I'm just glad I'm not actually paying for Premium membership, that would be really, really irritating.

milkyaqua · 04/02/2023 21:54

Worth reading MattTech's detailed posts re this on this thread:

www.mumsnet.com/talk/site_stuff/4702668-for-the-love-of-god

tribpot · 04/02/2023 22:05

Yes, that's the first time I've seen a decent explanation from anyone at MN and hopefully will mean they stop asking people to clear their cache or disable antivirus (FFS) instead of admitting it's MN's fault.

AuntieStella · 05/02/2023 08:20

Really crappy today, just crashed on a thread of only 122 posts (despite being on a much loathed 25 post view)

Now "see all" is a feature that you know is much prized by MNers - to the extent that it was retained for "classic"

And it worked just fine in the immediate aftermath of the replatforming.

We want it back! Do think about how you prioritise a feature that users clamour for v new stuff imposed top down that no-one would miss (and which buggers up site performance)

Though I am glad to see the rather better tech info on the other long-running thread about this (which doesn't just tell users they need to Do Stuff, as it's now clear you know the issue is your end)

GeneratedRandomly · 12/02/2023 22:18

I am now getting this (again):

Hmmm… can't reach this pagewww.mumsnet.com took too long to respond
Try:
Checking the connection
Checking the proxy and the firewall
Running Windows Network Diagnostics
ERRCONNECTIONTIMED_OUT

OP posts:
LilyMumsnet · 13/02/2023 15:16

Hi OP
Thanks for sharing that - we're really sorry you're still having issues with this.

As you're viewing 25 posts per page, it's not something we've managed to replicate yet. We're aware of an issue with a memory leak on longer threads when viewing more posts - but not in this case.

We're still investigating but if you can, and we appreciate it's a faff, could you email a screen recording over to [email protected]? When we're not able to replicate things, it's a really big help for us to see how the issue is playing out.

New posts on this thread. Refresh page