|
10 news for every delete - that's the way to go. 
|
|
|
|
|
Mike Mullikin wrote: Today we see the result of said advice..
It really does seem that way. All I can think is these apps load everything into memory as a distinct object and then never let it go. It's just crazy -- no lazy loading, no setting things to null after done with use. Just wanton memory eating with no thought.
|
|
|
|
|
raddevus wrote: no lazy loading
That's unfortunate naming, for once. Loading everything at once IS the lazy way of achieving it. 
|
|
|
|
|
surely the OS can handle that ...oh wait, it's winduds.
Message Signature
(Click to edit ->)
|
|
|
|
|
If you plan to run multiple OSes, you're advised to pack a lot of RAM, whichever your host OS is. Because the guest OS (Chrome) will not be appeased by single digits gigs of RAM.
|
|
|
|
|
Free the mallocs!
Whenever you find yourself on the side of the majority, it is time to pause and reflect. - Mark Twain
|
|
|
|
|
Free the Guildford Four! The Birmingham Six! The Renault Five!
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
if you open Task Manager, and watch Postman's memory usage, you can actually see it adding about 0.1 MB/sec, just sitting there, doing nothing.
|
|
|
|
|
Chris Losinger wrote: just sitting there, doing nothing.
Except leaking memory! 
Ironic, I got this email from Postman last week basically tooting their horn about how great they are, how much their customer base has grown, etc. Sad, because their UI sucks, and their app sucks too IMHO.
Latest Article - Slack-Chatting with you rPi
Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny
Artificial intelligence is the only remedy for natural stupidity. - CDP1802
|
|
|
|
|
Marc Clifton wrote: I got this email from Postman last week basically tooting their horn about how great they are,
It's great because it stands alone.
There is Fiddler - Free Web Debugging Proxy - Telerik[^] too but it isn't much better (UI or memory leakage).
|
|
|
|
|
Marc Clifton wrote: consume 1/2 Gig of RAM
.Net
|
|
|
|
|
|
Slack App? Why not use the browser?
Oh you've covered Chrome!
I got nothing to say. 
Okay wait, I got one important thing to say- Postman is Sh*t.
|
|
|
|
|
Marc Clifton wrote: F***ing insane.
Agreed!!
|
|
|
|
|
There is a resistance however. One of my workmates positively rejects C++ strings because they could be a 'waste of memory' with respect to C arrays of characters.
|
|
|
|
|
640K is enough for anyone!
If you can keep your head while those about you are losing theirs, perhaps you don't understand the situation.
|
|
|
|
|
"I understand that reference, sir". I think Adobe or Norton should get it engraved on their front door.
|
|
|
|
|
I think that everyone who works in C#, Java, and the other offending languages should be sent to boot camp for a few weeks, to learn C.
A few hundred thousand malloc statements later, they'll maybe understand what a bloody mess they're making and relying on microsoft to handle for them!
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Marc Clifton wrote: now it uses a meager 2GB.
That's because you restarted the background logging of your activities, navigation, music listening,... by closing the browser.
|
|
|
|
|
Apparently, their latest and "greatest" (yeah, just kidding, Slack sucks big time) takes a bit less memory (roughly 350Mb).
Still, it's pathetic - and for a messaging app, the only thing I love about it is the ability to scroll using PgUp/PgDn while in the "Message" editbox - which sadly, Skype doesn't have even now.
Best,
John
|
|
|
|
|
Marc Clifton wrote: What in gods green earth would require Slack to consume 1/2 Gig of RAM?
Marc Clifton wrote: And don't even get me started on Chrome.
Slack is Chrome... At least, it's built as a Javascript app on Electron, which uses Chromium as its display engine...
Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p
|
|
|
|
|
Stuart Dootson wrote:
Slack is Chrome... At least, it's built as a Javascript app on Electron, which uses Chromium as its display engine...
And therein lies the problem.
|
|
|
|
|
Your point is valid, and it sure is a problem that kids of today never learned the RAM equivalent of the big-O of algorithms
Yet it is easy to be misled by too quick observations. If you map a 2 GByte file into RAM, you haveessentially set up 500K page table entries, without bringing any of it into physical RAM. In many cases, just a tiny little fraction of it will ever get into RAM before the application terminates. Checking my RAM use right now, there is slightly above 6 GB "In use", green color in the resource monitor, which means that is any process needs RAM, nothing needs to be paged out - the other process can take over those pages without any fuzz. A mere 35 MB is currently "Modified" and needs to be saved to backing storage before another process takes over. 1.9 MB is in "Standby" - the last user of those pages are no longer using them, but they are frequently used segments, so chances are that another process soon may ask for (parts of) it to be "loaded", which is a null operation of the pages are still in memory.
Of course there are cases of software that really needs huge amounts of data space - FEM and huge matrix models (read: weather forecasting) are the classical ones. I am currently testing out Coverity (a code analysis tool) that builds a complete flow graph of a million lines of source code; that fills some space.
And then there are those that really shouldn't need more than a handful of MB, but requires a few hundred. Or a couple GB. Yet, if it requires a GB during startup, and then that memory is paged out (which is a null operation for code segments), leaving a working set of a dozen MB for continued running, it won't slow down your other programs very much.
Only if it actually addresses RAM "all over the place", continously maintaining a huge working set, is there something to worry about. Some programs are that way. But lots of users are screaming out because they see huge numbers, without understanding what the numbers represent.
|
|
|
|
|
Marc Clifton wrote: 17 tabs and almost 5GB. Close Chrome, restart with exactly the same 17 tabs, and now it uses a meager 2GB.
Don't necessarily blame Chrome for that one. I worked on a project a few years ago, a "web designer" had built the front end and I was supposed to make the back-end work. The page loaded fine (apart from the 20 or so errors thrown up in the console, that the "designer" had never looked at); but it then used about 1Mb every 5 seconds until Chrome crashed or Windows ground to a total halt. Never did find exactly what the issue was, but thinning out the 200+ stylesheets and script references made a big difference. Recoded the script to just use JQuery plus about 100 lines of custom code and all was well.
A lot of websites seem to be built by designers just throwing in every possible framework and widget because they can't be bothered to style something by hand and don't know how to do even basic scripting.
Sorry - inadvertently entered rant mode there...
|
|
|
|
|
Just try implementing ISlackFactoryDefaultAttachmentConnectionCreatorFactoryMetaEnumeratorFactoryInstantiator without using 0.5GB of RAM.
Software Zen: delete this;
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
