RuntimeBroker (now Shell Infrastructure Host) high RAM usage

Some time ago I noticed that if I start opening images using the default Photos application of Windows 10 from a folder that contains a lot of them (I then created on another notebook a folder with 32000 of random PNG an JPG images of around 1000*1000 resolution to test it), the system process RuntimeBroker (now it is called Shell Integration Host in 1803 update) starts consuming a lot of RAM - around 100-150 MB per opened image. So after opening like 10 images, this process eats 1GB+ of RAM. If I continue opening images, then after some time this process will crash and take down Photos down too.

I wanted to ask if I'm the only one with such a behavior? If somebody else could try replicating this issue?
Thanks in advance!

Seems like nobody have the same problem?
Can someone at least help me check it?

Some time ago

The 'problem' isn't relevant to 1803, as you prefaced it.

It would seem the problem is related to the creation of thumbnails for the countless images in the folder. Any file manager that has to accept that task would struggle. I use XNView whose main draw is to present files as images. Because of the program's struggle, I turned off thumbnail creation. I did the same with Windows 10.

pyramid10 said:

I turned off thumbnail creation. I did the same with Windows 10.

@pyramid10 How?

From the File Explorer Ribbon, select View/Options--change.

In the Dialogue Box that comes up, select the View tab, and there at the top of the list for Files and Folders: Always show icons, never thumbnails.

pyramid10 said:

The 'problem' isn't relevant to 1803, as you prefaced it.

It would seem the problem is related to the creation of thumbnails for the countless images in the folder. Any file manager that has to accept that task would struggle. I use XNView whose main draw is to present files as images. Because of the program's struggle, I turned off thumbnail creation. I did the same with Windows 10.

Thumbnails are not a problem - they are created and drawn correctly and without problems. Explorer itself sees no problems neither in memory consumption, nor in crashing.

However, the "modern" Photos application, to be more precise the system process Runtime Broker, causes that huge memory leak.

So anyone else has the same problem or?

I would really appreciate it if someone could test the described behavior.

Can someone recommend me a forum or chat where I can ask to help me with testing this issue?

I'm still looking for someone to help me with this.