x

Search in
Sort by:

Question Status:

Search help

  • Simple searches use one or more words. Separate the words with spaces (cat dog) to search cat,dog or both. Separate the words with plus signs (cat +dog) to search for items that may contain cat but must contain dog.
  • You can further refine your search on the search results page, where you can search by keywords, author, topic. These can be combined with each other. Examples
    • cat dog --matches anything with cat,dog or both
    • cat +dog --searches for cat +dog where dog is a mandatory term
    • cat -dog -- searches for cat excluding any result containing dog
    • [cats] —will restrict your search to results with topic named "cats"
    • [cats] [dogs] —will restrict your search to results with both topics, "cats", and "dogs"

[Closed] ShaderCompileWorker eats memory like crazy

During initial editor startup when it compiles lots of shaders, I observe ShaderCompileWorker processes steadily growing up to 2GB+ RAM each while they compile shaders (after what I have to shutdown editor due to insufficient RAM). On Windows, ShaderCompileWorker are almost always under 100MB. So, is it a leak that should be fixed or there is a really strong reason why OpenGL shader compilation should take 20x RAM more than DirectX?

Product Version: Not Selected
Tags:
more ▼

asked Dec 12 '14 at 10:57 PM in Linux

avatar image

Slonopotamus
195 7 12 15

(comments are locked)
10|2000 characters needed characters left
Viewable by all users

The question has been closed Dec 14 '14 at 03:36 AM by amigo for the following reason:

The question is answered, right answer was accepted


1 answer: sort voted first

I thought that we had these leaks sorted out way back when...

There were couple of major leaks in hlslcc that we patched, but come to think of it after submitting so many PRs I don't remember if that specific one was ever incorporated or not.

If you have the time and inclination, please send a PR with a fix and I'll pest0r RCL to add it in. SCW should definitely not eat 2GB+ of RAM.

more ▼

answered Dec 13 '14 at 12:24 AM

avatar image

amigo
1.1k 53 33 90

avatar image Slonopotamus Dec 13 '14 at 09:49 AM

I thought that we had these leaks sorted out way back when...

I don't believe others who play with UE on Linux don't notice 3-5 (depending on number of cores) processes each eating 2GB+ RAM.

Whatever, I'l try to valgrind this beast.

avatar image amigo Dec 13 '14 at 04:01 PM

We ran SCW through valgrind and found couple of major memory leaks in hlslcc. They were patched in my 4.4-linux branch, and iirc I did submit PR upstream to Epic for those.

I'm not sure what happened afterwards, as Epic made further changes to SCW and more integration of hlslcc into the engine occurred as well.

avatar image amigo Dec 13 '14 at 07:44 PM

I forgot to include a link to my branch, so here is the commit for the hlslcc leaks identified back in 4.4 days https://github.com/3dluvr/UnrealEngine/commit/f9911a3f713409add857ea3869d100ff7cf11ea3

avatar image Slonopotamus Dec 13 '14 at 09:23 PM

Thanks, I'll work on pushing this upstream.

(comments are locked)
10|2000 characters needed characters left
Viewable by all users

Follow this question

Once you sign in you will be able to subscribe for any updates here

Answers to this question