I've been having some problems with Windows Photos applications for a while.
The problem is that if you start opening images from a single folder containing a LOT of them, a sub process (or at least it is in the Windows Photos tree in Task Manager) called Runtime Broker starts consuming just enormous amounts of RAM. And I mean like after opening just like ~20-30 different images it may consume up to 3 GB of RAM. If you keep on opening images, then it will finally run over 4 GB and simply crash taking Windows Photos with itself.
Is there any way to fix that and if not, then how can I provide a bug report for this issue to be fixed?
And, please, do not send me to the Windows Response Center (or whatever it is called there), as my report is trashed there for who knows how long.
Recent Comments