Windows 10 photo viewer memory leak - Anyone else get this?

[Mussels]

Any time i leave an image open for a few hours, i come back to see crazy RAM usage like this, has anyone else had this happen?

I usually only notice because it causes lag in other programs, then task manager reminds me i dared to leave a jpeg in a viewer

 

[robot zombie]

Ooof. That's kind of impressive. I wonder what makes it do that.

I can't remember the last time I used Window's built in viewer. Always used infranview. Maybe not the prettiest but definitely one of the more stable and featured, not to mention light. Never looked back.

 

[biffzinker]

Ah yes the new fangled Universal Windows apps. I thought you might of been referring to the older Photo Viewer from Windows 7. It's still present in Windows 10 but requires a regedit addition to re-associate ext types for the old viewer.

 

[Mussels]

i had two open and lost 10GB of ram, but i couldnt load TPUcapture to get a snippet without closing one -.-

 

[puma99dk|]

In my Windows 10 Pro the Photo viewer app will crash sometimes doesn't matter if it's my playback video it support or images it's annoying to be honest.

I properly have to say this is looking though images not just having one opened.

 

[Toothless]

I'll open one and leave it open to see if I can get the same results.

 

[biffzinker]

Would toggling its ability to run in the background help?

https://answers.microsoft.com/en-us...ory-leak/3ab66be7-4d9c-4d67-b847-7347853dfcf5

 

[Bill_Bright]

Running (viewing) an image now.

9:58:45 0% CPU, 175.2MB Memory.

 

[Easy Rhino]

Leave it to microsoft to over complicate something like a photo viewer...

 

[newtekie1]

Just popped a jpg open in Photos, currently it is using 52.8MB. I'm going to leave it open and I'll check back in an about an hour and see what it is using.

 

[_L_]

I had that the other day, never noticed until I finished playing a game - I minimised it and it didn't close, went onto task manager and saw 24gb/32gb ram being used XD

 

[Bill_Bright]

Leave it to microsoft to over complicate something like a photo viewer...

Amazing how people automatically blame Microsoft when the problem has not even been identified. Or at this point, even duplicated.

9:58:45 0% CPU, 175.2MB Memory
10:47:10 0% CPU, 173.2MB Memory - so ram usage has even gone down! (though I would suggest 2MB is negligible).

 

[puma99dk|]

Amazing how people automatically blame Microsoft when the problem has not even been identified. Or at this point, even duplicated.

9:58:45 0% CPU, 175.2MB Memory
10:47:10 0% CPU, 173.2MB Memory - so ram usage has even gone down! (though I would suggest 2MB is negligible).

We ain't testing with the same image and since there isn't 2 pc's that are the same we will always get different results.

 

[qubit]

tsk tsk Mussels, what did I saw about looking at all that pron?

 

[Easy Rhino]

Amazing how people automatically blame Microsoft when the problem has not even been identified. Or at this point, even duplicated.

9:58:45 0% CPU, 175.2MB Memory
10:47:10 0% CPU, 173.2MB Memory - so ram usage has even gone down! (though I would suggest 2MB is negligible).

I'm referring to the App itself.

 

[Bill_Bright]

We ain't testing with the same image and since there isn't 2 pc's that are the same we will always get different results.

Irrelevant. The image does not matter. It is static (not changing or animated) so the resources needed to display it should not change. So the issue is the viewing program and we are both using the same program.

And, assuming Mussels is using one of the systems indicated in his System Specs, he, like me, is using Windows 10 Pro. So same OS.

Therefore, regardless the image, it should NOT continue to consume system resources. And on my system here, it is not.

10:16:19 0% CPU, 173.6MB Memory

I'm referring to the App itself.

What difference does that make? It is a very easy, basic, and to your Microsoft comment, uncomplicated program to use. It is not intended to be a graphics designer's or professional photographer's tool of choice.

 

[newtekie1]

It's been open 2 hours and still sitting at 48MB.

 

[nomdeplume]

Thought I fixed this when I switched to the classic photo viewer. Last week the W10 photo app accidentally got updated when I removed a restriction momentarily to update something else. AV started popping up with all these requests for network access. It uninstalled itself when I blocked its efforts through the third and final channel it tried to use. Went to open a photo and there was no app, POOF!

So I reinstalled it through the M$ store and it resumed the same needy behaviors and RAM usage. After I blocked it and switched to classic I forgot all about it. Just opened a folder with 5 photos and clicked through them a half dozen times. 8% RAM usage.

 

[Toothless]

Mine gets to about 1.5gb and starts to dump usage. Goes between 900mb and 1.5gb quite a bit.

 

[eidairaman1]

Bug report Microsoft

 

[FordGT90Concept]

I opened a picture that is 2 MB in size. Photos is using 432.6 MiB. I closed it and opened it again because that's ridiculous, 80 MiB now. Same picture in ye olde mspaint is 81 MiB. Same picture in Paint 3D is 114.5 MiB. The picture is 3552 x 2000, 72 dpi, 24-bit color depth which comes to 21.312 MB of raw data, 28.416 MB if we include alpha color (which it most likely has in memory). The memory consumption is stable for all three programs.


I wonder if your JPEG has malicious code in it or there's something specific about that picture that's causing an overflow.


Minimized? Maximized? Windowed?

I minimized it and it dropped to 70 MiB, now windowed again, it's up to 105 MiB. I minimized and restored it a few times, it already crept up to 144.3 MiB shrinking a little but growing a lot on each cycle.


Can click "..." in the corner and "Send Feedback" to report the issue to Microsoft.

 

[R-T-B]

What difference does that make?

Customer preferences should always make a difference.

I'll use it the day I can zoom with the mousewheel.

 

[Mussels]

the photo was a JPEG of my drivers licence i used for proof of ID for a rental application, might be relevant that i printed a copy of that document and then left it open?

 

[AltCapwn]

Go into start menu then click "settings" (the gear icon), go into Privacy, Background apps and disable everything .

You won't have memory leak issue afterwards.

 

[FordGT90Concept]

the photo was a JPEG of my drivers licence i used for proof of ID for a rental application, might be relevant that i printed a copy of that document and then left it open?

Or it might be GPU. I left it open after it hit 144 MiB (from window/minimize/window/minimize) and it's slowly falling in memory use (down to 140.9 MiB now).

Since some are reporting it happening and some aren't, I wonder if it is a display driver issue, especially in NVIDIA drivers. I run AMD here and I'm not seeing it. Looks like 50/50 on NVIDIA cards above. Could be a specific driver version causing the leak.