1342 Crash - OOM

[therube]

1342, x86

Everything had used up 1.8 GB of RAM

don't know that i've ever run into that type of memory usage before

only started using Thumbnails, & not that often at that, & i set up
a separate -instance for that

don't know if it's a simply "OOM" issue (as in you're pushing things
& ought to use x64 instead), or if there's some other issue about


i set a directory to scan
not that big at that
only 7880 objects

XL thumbs
& i was simply paging down through them


oddly, even though i've "crashed", i might not have actually "crashed"
(not sure, yet)
once the dialog came up i /thought/ that's it
but in fact i can still do stuff, like get a count of files,
the only thing is that it is no longer rendering thumbs

heh, OK, so i did actually crash
closing the crash dialog & there she went
.

Everything 1342 OOM, TOM-THUMB.png (2.75 KiB) Viewed 90895 times

Mixed Mode Size - why it does not work - i was looking for something BIG, never say 1.8 GB.png (11.75 KiB) Viewed 90894 times

.

(I've not seen 1343 yet.)

[horst.epp]

What did you expect where this amount of data should be stored ?
For testing I scrolled thru a medium thumbnail view of about 7000 jpg pictures without any problems or crashes.
Of course thre must be enough RAM available for such an operation.
I my test case Everything used about 4 GB memory.

In praxis I would never use such a view as I can't make anything usefull with 7000 thumbnails.
______________________________________________________
Windows 11 Home x64 Version 22H2 (OS Build 22621.1555)
Everything 1.5.0.1343a (x64)
Everything Toolbar 1.0.5.0

[NotNull]

(I've not seen 1343 yet.)

1343 fixes property indexing. I would not be surprised if this also could cause the symptoms you describe.

[tuska]

(I've not seen 1343 yet.)

To be honest, I don't understand why reports are made about possible bugs
where the latest version of Everything is NOT used.

[void]

This is a common issue with x86 and showing a large number of thumbnails.
The x86 version can only allocate 2 GB of RAM.
Once exceeded, you will see this crash/OOM dialog.



Each thumbnail uses 262KB of RAM.

Periodically close the Everything search window to free up memory allocated for thumbnails.
Limiting the number of cached thumbnails is on my TODO list.



I recommend the x64 version for viewing a large number of thumbnails.

[therube]

Just for reference, only cause I tried...

So IrfanView (x86) at up 2.8 GB of RAM, then settled back down to 1.4 GB, then finally dropped to 45 MB - once I closed the thumbnail window.

IrfanView did not crash, but it also did not fully load all the thumbs.
.

Everything - IrfanView got up to 3 GB before dropping 2o 1.4 GB but never finished loading thumbs to 45 MB after closing thumb window.png (20.09 KiB) Viewed 90729 times

[therube]

> What did you expect where this amount of data should be stored ?

I didn't expect anything.
Had no clue.
Only telling what happened.

> why reports are made about possible bugs where the latest version of Everything is NOT used

Can't report what you don't have.
And I didn't have. So...

[therube]

IrfanView did not crash, but it also did not fully load all the thumbs.

That is not correct.
IV will (or so far has) loaded all the thumbs thrown at it.

(What happens is that it loads a certain number, "initially", if you will, then as you scroll down further, it loads more...

What was happening is that when I saw not loaded thumbs, I thought 'it did not fully load all' - but that was because I had held the left-mouse [clicked] on the scrollbar, & while still clicked, thumbs [temporarily] stopped loading. Release the click, & thumbs again loaded, fully.)