Unofficial 'Measure your activity' thread!
-
So, before they patch it with a cloaked view, lets see how active you are!
Step 1) Open your profile to the 'all' tab
Step 2) Scroll down until your browser crashes, pay attention to the dates on the rightMine kicks the bucket by august 20th, evening.
What about you!
*Of note: This doesn't appear to be impacted by quality of computer, my work computer and home computer are basically opposite ends of the spectrum in every possible way and they crashed at the same point.
*I've only tested with latest chrome on win7
-
July 23rd. Then again I am not really active compared to you guys.
tested on Opera whatever the current version is, Windows 8, Laptop
Filed Under: If I were to post on the Like-thread on the other hand... Imighthave stopped at ~August 30th :D
-
Yeah, @Arantor probably gets like 3 days of history, max. I don't post much in the likes thread though, no more than maybe 5-6 times a week on average. (I spam a lot of other topics though)
-
Seems to have given up at July 22nd.
Latest Chrome x64, Win 8.1.
EDIT- Nope, it's going just very slowly. Each load took a couple of minutes but made it to May 26th, which I think was my first post here. Tab in Chrome is using 527MB, peaked at just over 550MB.
EDIT#2- Once Dicsores runs out of things to load, the tab performance returns to normal even with it all loaded.
-
"One day ago" on mobile chrome. I've been trying to catch up in /t/1000, though, my activity is way higher than normal.
-
Nope, it's going just very slowly
That happened to me to. Was taking 30-60 seconds just to trigger the next load. Then I finally got the sad face.
-
No sad face here. Made it all the way back to start eventually.
-
"3 days ago"
in the middle of my autobot like clicker activity.
it's not actually crashed yet but it's taking ~30 seconds to scroll down every time now and ~60 seconds to load the next chunk.
EDIT: Got to the end eventually. last load of activity: ~3 minutes and 6 times chrome informed me the tab had gone unresponsive, i said to let it live, but chrome was not happy
-
August 19th for me.
-
August 19.
-
-
bump~
-
I got a bunch through "1 day ago" before mine crashed on mobile Chrome. I'm sure I was going through a bunch of likes from others when it died.
-
This took all of 10 seconds to do.
-
August 19th was a bad, bad day. i.e.
M3 J00 111eleventy1!
-
June 22nd and no crash.
Should I thank @blakeyrat for the rage quit that kept my activity down?
-
I'd do it out of comedy but I'd really not risk crashing Chrome with all the other tabs I have open that I kind of need.
On the other hand I don't mind sacrificing my Firefox session for this. Hang on...
-
It only crashed the Discourse tab for me.
-
So, as of this there are 54,464 events in my history.
Firefox (current?) on Win7, i7 processor, 16GB RAM.
It's already chugging just at '1 day ago' events. To the point where there's a noticeable multi-second pause even before 'loading' comes up.
It's really grinding now. 10 second pause even before Loading comes up (just hit the 2 days ago margin), and the browser even temporarily reverts to the normal window styling at the top of the window.
And it's maxing out a CPU core that whole time while it's trying to load stuff, so yeah it's definitely having trouble.
Well: there was the 'script on this page may be busy' warning.
Now it's hitting the 'script on this page may be busy' twice in a single page load of content.
And the process now appears to have hung. And I'm not even onto 3 days yet.
-
August 21, but I've only got 800 items on "All".
-
Even better, I scroll down to about 3 days back, got tired of the shit and saw I had a notification, so I clicked the notification link to see the topic and it crashed chrome to click the link.
DICSOUUUUUUUUUUUUUUUUURSE
-
Discousistency says: "got em boss! "