Online Users Page


QN

Previous notifications:
4 years ago
New Blog Entry In .:A-MAN:. lists stuff!
11 years ago
Regular accepted your friend request
More..
9Smalls 12 months ago
Pretty sure I unintentionally fixed a weird “out of memory” error my website has been having since I switched to pre-rendering the first page load by changing how I define arrays.

I did it for overall performance improvements across the website and the API, but I didn’t expect it to fix a bug I have been struggling to figure out a fix for.
Back

Please Login To Post

69.:A-MAN:.
12 months ago
@Smalls lol fair
Reply
9Smalls 12 months ago
@.:A-MAN:. uhm acktually that was 2009

**shoves glasses so far up his face that it covers my 5head**
Reply
69.:A-MAN:.
12 months ago
@Smalls What about the DSi? :P
Reply
9Smalls 12 months ago
@.:A-MAN:. Actually don’t answer that. I don’t want to go back to the early 2010s smartphones.
Reply
69.:A-MAN:.
12 months ago
@Smalls lol
Reply
9Smalls 12 months ago
@.:A-MAN:. WebAssembly and mobile web browsers, name a more memory constrained duo.
Reply
69.:A-MAN:.
12 months ago
@Smalls weird. Not sure how that would happen.
Reply
9Smalls 12 months ago
@.:A-MAN:. Well part of me is wondering if the way I was defining arrays before was actually taking up too much memory as the site was doing the handover from the pre-rendered state to the locally rendered state.
Reply
69.:A-MAN:.
12 months ago
I guess if it work, it works. 🤷‍♂️
Reply
v3.2