I know that performance of Emacs is notoriously poor when it encounters long lines. I have a somewhat large file (260KB), that might have about 100 or 200 longer lines (in the ballpark of 1000 characters). I recognize that this might be difficult for Emacs to handle due to its underlying algorithm choice - but is that enough to forgive it for eating 9 GIGABYTES of my RANDOM ACCESS MEMORY, 4 GIGABYTES of my SWAP FILE, and then TRIGGERING THE OOM KILLER, just because I selected the entire buffer? I don't think so.
The interesting thing is that it only happens in the GUI. Without the configuration file loaded, it doesn't consume all of the memory - it settles on consuming CPU cycles instead. emacs -nw works fine even with the configuration file loaded - which is helluva weird, because the only difference between the graphical and terminal modes would be the slightly different settings for the faces and such - all of the packages loaded and configuration are otherwise the same. What gives? Is the GUI version of Emacs so poorly optimized?
Emacs
Makes
All
Computers
Slow
forgive it for eating 9 GIGABYTES of my RANDOM ACCESS MEMORY, 4 GIGABYTES of my SWAP FILE
Don't care about "suckless" poorfags cope, I have 32GiB of RAM, never had issues with Emacs which is always opened while I'm using VM, FF or play a Steam videogame. I use Arch, BTW.
>>3
Are you suggesting that if I sacrifice even more memory on the altar of Emacs, Stallman will stop flirting with his boyfriend Eric Raymond and fix za olde text editor? For now I am using the curses version, it feels a lot snappier than the GUI. But I will miss the stretchy cursor...
I'm suggesting that I don't care about your poorfag issue. Works on my machine.
>>5
You don't care, yet you both reply, and bump the thread? You sound like you'd have a good shot at career in politics, dude.
Find the bug and contribute back to emacs
Bump for not caring about poorfag problems. Cheers!
>>7
I would, but it's not written in Scheme, so I can't...
Use Edwin
Eight
Megabytes
And
Constantly
Swapping
>>11
Totally irrelevant.
OP has far more than 8 megabytes of RAM.
Emacs ate all of my RAM
That's very greedy of Emacs.
You should write a RAM-eating program whose sole purpose is to prevent Emacs from eating more than its fair share of RAM. Your RAM-eating program would be competing against Emacs for RAM, resulting in less RAM usage for Emacs. This is a versatile solution for curbing excessive RAM usage.
>>13 made me chuckle
>>13,14
memory ballooning but ironic