Skip to main content

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: Real World V2 (& refacets) memory issues (Read 1232 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Real World V2 (& refacets) memory issues

My issues are largely pointing to REFACETS, but would love any advice from the braintrust here.

v2 32bit : will not startup if REFACETS is used. Hangs at startup ~30min (thanks!) until mem shoots past 3.8gb and crashes with no reports.
v2 32bit screenshot : (upgraded over existing 161 portable) using facets and most of my v.161 components (not SMP!) startsup and uses about 2.2GB when media library status hits idle. (If SMP is used, launches at ~2.8 and will crash within 10-15 tracks played)
v2 64bit screenshot : (FRESH portable install-scanning to add my Libary takes ~18hours to reach "idle") using REFACETS and *fewer* components uses 5+GB mem when media library status hits idle.

Question 1: does this seems normal? this is the 64bit panacea, 5gb+ for a music player - why the HUGE discrepancy betw 32/64?

Question 2: what is with REFACETS memory usage? (doesn't even support images yet!)


Re: Real World V2 (& refacets) memory issues

Reply #2
Just curious: what windows shell are you using?  Wondering if that might be a variable in the equation.

Re: Real World V2 (& refacets) memory issues

Reply #3
windows shell are you using?

as in sys info?

OS Name:                   Microsoft Windows 11 Home
OS Version:                10.0.22621 N/A Build 22621
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Standalone Workstation
OS Build Type:             Multiprocessor Free
System Manufacturer:       HP
System Model:              HP Laptop 17-cp3xxx
System Type:               x64-based PC
Processor(s):              1 Processor(s) Installed.
                           [01]: AMD64 Family 25 Model 80 Stepping 0 AuthenticAMD ~2000 Mhz
BIOS Version:              Insyde F.06, Thu 5/23/2024
Total Physical Memory:     11,627 MB
Available Physical Memory: 4,416 MB
Virtual Memory: Max Size:  34,155 MB
Virtual Memory: Available: 20,619 MB
Virtual Memory: In Use:    13,536 MB

Re: Real World V2 (& refacets) memory issues

Reply #4
I didn't notice a custom shell. The dark mode of Process Explorer just looks like that, if that's what's being referred to.

How many tracks are there in your media library? How much memory is used by a library viewer is usually roughly proportional to that.

v2 32bit : will not startup if REFACETS is used. Hangs at startup ~30min (thanks!) until mem shoots past 3.8gb and crashes with no reports.
The 32-bit version is limited to 4GB of memory, so yes you will run into problems if that limit is reached.

Question 1: does this seems normal? this is the 64bit panacea, 5gb+ for a music player - why the HUGE discrepancy betw 32/64?
I don't know that there's a discrepancy in your figures, since the 64-bit figure is with ReFacets, and the 32-bit version with ReFacets died when it approached 4GB. But it's normal for a 64-bit version of a program to use a bit more memory compared to a 32-bit version, as memory addresses and certain other values are 8 bytes instead of 4 bytes. (The difference for two portable installations I just created was 10%, so not a drastic difference.)

.

Re: Real World V2 (& refacets) memory issues

Reply #5
I didn't notice a custom shell. The dark mode of Process Explorer just looks like that, if that's what's being referred to.

Whoops, yes, that was what made me ask the question. Apologies, mjm716! :)

 

Re: Real World V2 (& refacets) memory issues

Reply #6
Quote
Question 1: does this seems normal? this is the 64bit panacea, 5gb+ for a music player - why the HUGE discrepancy betw 32/64?
I don't know that there's a discrepancy in your figures, since the 64-bit figure is with ReFacets, and the 32-bit version with ReFacets died when it approached 4GB. But it's normal for a 64-bit version of a program to use a bit more memory compared to a 32-bit version, as memory addresses and certain other values are 8 bytes instead of 4 bytes. (The difference for two portable installations I just created was 10%, so not a drastic difference.)

Well, there are differences for some people because v2 caches ALL tags from a file without any possibility to limit this behavior or omit specific tags. So while V1 had a memory limit per tag, which was set at the "LargeFieldsConfig.txt" file, v2 simply goes wild. This may not be a problem for some people, but it's a clear problem with large libraries (which worked fine on v1 under 4gb) or libraries which include a lot of tags (not needed within foobar context). These same configurations on V2 go over 4gb and crash on x32 or simply use too much ram (and time) on x64.

This kind of discrepancy and undesired behavior has been reported before multiple times.
https://hydrogenaud.io/index.php/topic,125541.msg1040000.html#msg1040000

That's said, it may well be Refacets has additional problems with large libraries, but this problem originates in the way tags are cached in V2.