FIX FOUND:

There is a chance that I am, of course wrong, and hopefully staff will step in and have something to say, but from my experiences today, ALL of the lag issues stopped when I blocked that site from loading on Subeta. (If you want, you can download NoScript / another add on that blocks harmful sites)

@ Staff It would be lovely if this site was ONLY loading on each page when the actual Survey system is being used! :S

Talking to other folks, I'm not the only person having this issue over the last couple of days. Firefox is using insane amounts of memory, even when all pages are "loaded". I am literally only using pages on Subeta right now, I have a total of 4 tabs open, all of them totally loaded and supposedly not doing anything, and this is what I get (click the image or drag it to the address bar to increase the size):

On every single Subeta page, I am getting heavy hang time. It is often trying to connect to google-analytics or cloud flare. Even after the pages have loaded fully, I am still getting increased memory usage on my laptop. This does not happen if I close FF and stay away from Subeta. It is 100% being caused by Subeta.

Another friend of mine has had over 1700k mbs used on her computer within the last 48 hours during one session on Subeta (she tracked her memory usage during questing, it went from ~ 370k mbs used to 1700k+ mbs used).

Clearly something on the backend is forcing the computer to use up large amounts of memory to run the shop search and other pages (nothing is as bad as trying to use the shop search). It's causing other programs (which are running about 1/3 of the memory) to hang up, causing any attempted page load to hang up (I cannot load anything until whatever Subeta tab I'm trying to load is done). This is outrageous. I have games that are run entirely on my system's memory (that are large and intricate - looking at you GW2) that still do not tie up this much memory.

[edit] Monitoring tests. Closed Firefox, reopened and cleared cache/cookies, closed again. Reopened and have one SubetaLodge page open, one forum page, and one user wishlist (and now this, but all counts are before I reopened this thread).

So far I've gone up approximately 300k mbs by using the shops (am currently holding at usage between 400-425k mbs).

My friend, who had restarted Firefox with a memory usage of about 251k mbs (did not clear cookies/cache). Using shops spiked her to the 400-450k mbs used range. She went to the forums and jumped nearly instantly from ~450k mbs to 700k mbs. Closed forum and was stuck hovering around 500-550k mbs. Vaults also caused a spike that dropped back closer to the 550k mbs range. And her lag has restarted.

[edit] My friend tested another theory. She opened up an empty main shop (not user shop, main shop) and went from 550k mbs to 800k mbs instantly. Opening the wardrobe kept it steady at that usage but did not spike it any further. She has now restarted because the lag was out of control. Firefox reopened at 250k mbs. Using another website (and opening several tabs) caused almost no discernible spike in memory usage.

I'm getting this now, too - pages taking forever to load, breaking while loading, links needing to be clicked multiple times, LAG LAG LAG, HUGE jumps in memory usage, endlessly trying to connect to Google Analytics, etc......

What's been broken this time?

I've always noticed this w/ this site and it's always been irritating. There may be days when things seem to load faster but after having several tabs up at once and using them, it begins to bog down and get laggy and s/times when using a portable edition of FF, it just down right has to be restarted. The past few days have been worse than normal and I can only be glad I finished my Wiz quests before it got too bad or like yesterday, just became a constant error.

I've never had this issue before. For the past few days, I'd say around the time the shop search buying was changed, I've had to close FF because it starts to lag then freeze on me. In fact I need to do this after posting this. I haven't changed anything on FF before this started. I did have an update push through a couple of days after this started and I had hoped that was why I was having issues. Nope.

It seems like it comes and goes. It's on subeta's end as I don't have any problems until I start playing on here.

Yeah, I'm having this issue too as the pages are taking ages to load properly. Even scrolling makes it load longer on some of these pages. I use between 3-8 tabs and I never had a loading issue with many tabs. I'm using Safari if that helps.

So the site's been 98% inaccessible to me for the past two and a half days because of this. (I would say 100%, but I can still SEE the forums and shops even if NO POSTS OR ITEMS WILL LOAD.)

I can't do quests, I can't restock (so that's several million sP per day that I'm missing out on,) I can't play games, I can't interact with anyone or anything in any meaningful way.

Gold Account users had better get a bloody credit on their account for this once it's fixed. Otherwise, it's little better than theft.

i thought it was me but lots of lag in battles

I usually use chrome so I just opened the site in firefox and wow, that's a lot of memory being used! This thread uses 86 mb in chrome and 256mb in firefox. That's 3 times of what chrome uses for the same tab!

Oh god, this is back again. Supposedly, it used to be pusher.js that was causing it. Subeta's pulled the plug on pusher months ago, but this has been happening regardless of that.

NoScript is a godsend. I cannot stress this enough. Ever since I installed it and only allowed some parts of the site, I haven't been getting the insane memory spikes even while questing. Only time it goes loco is when I open 40+ tabs, but that's to be expected. With NoScript, site functionality might be a bit reduced (IDK how it works with the shoutbox, I don't use it so I can't say), but it's better than having your computer crippled every time you try to quest.

Every time I disable NoScript for Subeta, Firefox eats memory like I eat cake.

Before it's suggested - no, I am not switching browsers. I should not be expected or asked to change browsers in order to access and use one site.

Yikes. I have 3 tabs open in firefox, This one, Secluded shire and battle quest, currently running 632 MB. My boyfriend even hooked me up the landline, cause he thought the wifi might be on the fritz. Hasn't helped.

Edit: closed down to the battle quest tab and sat it on for a while without clicking anything, still running over 600 mb

These last couple weeks I've been working on TCs for my pets after quests and I have noticed that recently this week while I've been doing this, I have to restart my browser after I'm done each day. I usually start up FF at 200-250mb (Subeta is my homepage actually, so idk if that's contributing) And by the time I am done doing TC stuff I am anywhere from 800mb all the way to 1800mb That's a really drastic change, and I've tried to make sure to have nothing else open to help but it doesn't fix anything =/ it still does it.

Still having this giant issue, wish staff would acknowledge it -_-

There is a chance that I am, of course wrong, and hopefully staff will step in and have something to say, but from my experiences today, ALL of the lag issues stopped when I blocked that site from loading on Subeta. (If you want, you can download NoScript / another add on that blocks harmful sites)

@ Staff It would be lovely if this site was ONLY loading on each page when the actual Survey system is being used! :S

(so you know what's up)

For those of you who also reported this issue, found a fix for us. It's in the post immediately above this one, or you can check the top of the first post (I added it in so it's easy to see).

@ reaper I actually had that blocked for awhile via noscript but certain things don't work right w/out it. I actually didn't notice until I switched over to Chrome w/out any kind of script block and that's how I found what it does.

Having it unblocked hasn't made that much of a difference to how it was before, so it's a lot more behind the scenes stuff than it is w/ the scripts.

Edit: Checked my portable edition of FF to be sure and even w/ everything allowed on these pages, I never breached that. The most I got to was 340 and that was in consistently loading of pages (clicking around). The search shop page spikes (normal) when you put in a word and it shows you a list of results before you click the search button, but that's it.

The only scripts I'm allowing on here now are subeta.com and cloudflare.com. The site still seems to running a bit slower but I'm no longer having to close FF down every 5-10 minutes.

I double browse with FF on here. So I do usually have a few tabs open on each.

@ Reaper Cheers for the ping, but I think there's more than just intercom.io causing issues. This memory load isn't a recent thing - it's been going on for a while and tends to spike up and down over the course of weeks.

I only have subeta.com and cloudflare.com allowed just like and the site works reasonably well for me. It does go into the 700-800k range while questing, but that's not really surprising. I open all questgiver tabs at once and finish 'em one by one.

It's definitely not fixing all of my issues, but it kept me from spiking into 700-800k finally. I only go above 400k right now if I have a lot of tabs open.

I really wish they'd sort the memory leak though - I have huge games that don't use up this much of my memory and they run entirely off of my system =/

:c I know, I wish they'd fix the leak too. NoScript isn't going to fix everything, but at least you don't have to restart firefox every 5 minutes because of memory load.

I'm guessing the programmers have no idea what exactly is causing it. Pusher was blamed around February, they nixed Pusher around May, but I still had issues with massive memory load even after Pusher was removed. It seems to randomly happen and then goes away for a while. 😕

I had huge problems with pusher and mostly they were resolved for me when that was taken away. This memory leak didn't start until they shifted the shop search (or at least it wasn't bad enough for me to really notice until then on my end). Hopefully they can figure it out, or even just acknowledge that they're aware of the issue and are trying to figure it out.