I'm not sure why you had to make 4 separate posts, but let me see if I can answer some of these.
no not computer memory nor processor...
I'm still not sure what it is you are running, whether it's XP, or Win7, 32bit, 64bit, You never really made it clear, but I can tell you that Slic3r uses memory and processor to do it's thing. I suspect that the same problems you had printing the simple parts for the Atlas 3D printer are surfacing here as well.
remove degenerate faces' is what I used. it also has values you can set
That has nothing to do with polygon reduction. Worse yet, it's a function that usually distorts the surface and creates more problems that it solves. It will remove a face which it thinks sits on a degenerate edge, removes it, which creates additional degenerate edges, removes those, and so on, then fills the surfaces without any though to the original; shape.
I never use that function, I'd rather leave them in place as they don't affect the model in any adverse ways. Perhaps this is why you're having such problems with your models. You let NetFabb "fix" them and instead it messes them up.
another thing that loads space in files is lots of changes made over several times. it saves things like old parts posistions etc.
Well, the first part is true, making changes over time, it will affect the final size of the file, it could be larger, or smaller.
STL is a pretty simple format, it stores triangle information, their relative scale, and location from origin, that's it. The scale and location information doesn't take up any space to speak of, the data is very small (a few KB). It's the number of triangles that take up space. So the more "refined" a mesh is, the more triangles it has, so the larger the file is. If your file blimps out of proportion, it's because it got more triangles.
apps like a Slicer and related programs to it have buffer limits and cache limits in them and when they are reached just loading the file then no room left to modify it.
Sorry, but it doesn't look like it. The fact that I can load and slice a 200MB file is proof of it. There might be a limit, probably imposed by the amount of available RAM and scratch space on your HDD, but you shouldn't see it with a small file like the one you originally mentioned.
Bottom line, you're having the same problems here, that you had printing the Atlas 3D parts. There you refused to acknowledge that the problem is at your end, and blamed the STL files, even when everybody was telling you there was nothing wrong with them. Here you look at Slic3r as the culprit, when really it's something else on your end.
I don't think you'll ever be rid of any of your issues until you face the fact that there's something else wrong with your system as a whole, and start overhauling it from scratch.
To print or, 3D print, that is the question...
SD3 printer w/too many mods, Printrbot Simple Maker Ed., FormLabs Form 1+
AnyCubic Photon, Shining 3D EinScan-S & Atlas 3D scanners...
...and too much time on my hands.