Vienna Symphonic Library Forum
Forum Statistics

196,131 users have contributed to 43,014 threads and 258,392 posts.

In the past 24 hours, we have 0 new thread(s), 6 new post(s) and 175 new user(s).

  1. Home
  2. Sample Libraries
  3. Vienna Instruments Libraries
  4. Potential RAM leak with VI on XP64...at least on my system...anyone else?
  • K
    K
    This is my previous post that no one really responded to................ Maybe this will help!!............ Alright. First of all, I would like to say that I 'm not upset and I ABSOLUTELY LOVE VSL!!!! Ok, now that I got that out the way. I'm a new customer so I may be a lacking the expert knowledge. Ok, I've invested in a Mac Pro 2.66 Quad. I have 3gb so far. I am only running the Chamber Strings Collection. I am using Prottols as my Host. (ever since the new rtas). BUT I JUST CAN'T SEEM TO GET CONTROL OF FLOATING RAM. NOBODY RESPONDED TO MY FIRST BLOG SO I AM TYPING IN FULL TEXT DARNIT!!!!! I even tested it. My ram peaked at 2064mb. I loaded a simple matrix. Then I cleared it. When I cleared it, I never went back up to 2000mb. It peaked at 1664mb. Then I loaded a few patches and a matrix. After that I cleared it off. So when I checked my ram it showed 0 samples used and about 1400mb peak. I keep repeating the same steps with different combinations of patches and matrix files until I ended up with 300 mb WITH ABSOLUTELY ZERO SAMPLES LOADED. What am I doing wrong? eventually I couldn't even run my Protools because it had no space to work. Nothing could work in that matter. Even when I closed out VI and reopened it, the ram was still at the same spot. The only way that I could get my ram back was to restart my CPU. now thats not right is it? Am I not erasing the samples out of Ram correctly? Do I need to reload VSL. Whats the dealeo? Is it a Mac configuration issue? SOMEBODY PLEASE WRITE BACK THIS TIME!!!!!!!!!!!!!!!!!!! HELP! HELP!
  • D
    D
    Hi ktnujynisis,

    I'm sure VSL is looking into it.

    I'm frustrated too and would like an answer right away
    but its not that simple of a fix and needs some serious looking into.

    If we hang in there they will surely produce some fix or resolution.

    David
  • R
    R

    I haven't experienced the behavior described in this thread but I have noticed an odd behavior that might be related and, if so, might help to nail down the source of the problem.

    When I re-load all samples after optimizing, I very often wind up with MORE available RAM than before.  My swap file is set to 0, so it's not that the OS is just dumping stuff to the swap file.  The VI definitely does some strange things as far as memory goes...

    This happens using the VI as a plug-in in Cubase 4 under WinXP 32-bit with the /3GB switch. 

    rgames
  • D
    D
    Hi rgames,

    hmmmmm....just for the heck of it I'll try doing that tonight and see what happens.

    I did not have this problem until I upgraded to winXP64 though so I'm thinking there is
    some issue between the OS and the VI/VE.

    Thanks for your input!
    David
  • D
    D
    Hey cm,

    Any luck looking into this RAM issue?

    I know VSL is busy with a million other things but it would be nice to hear if this problem is being looked into.

    Herb has a WinXP64 machine. It takes 2 minutes to confirm this issue on a computer. Maybe he could check his system?

    In the meantime I have tested my RAM and complete system for defective conponents. Everything is running fine.

    Not sure why almost a GB of RAM is disappearing on launching of VI or VE but its to big of an amount to overlook.

    Oh, I also tried a suggestion by another member here to use the Learn/Optimize/Reset function but it did not have any impact.

    Thanks for you help!

    David
  • D
    D

    David, as I said before, it doesn't happen on my XP64 system.

    DG
  • D
    D
    Hi DG,

    Can you list your version of WinXP64, RAM amount, type and how many chips, and motherboard model?

    Sorry to be a pain but your help is greatly appreciated!

    Thanks,
    David
  • D
    D
    [quote=DM33]Hi DG,

    Processor(s)

    Number of processors 1
    Number of cores 2 per processor
    Number of threads 2 (max 2) per processor
    Name Intel Core 2 Duo E6700
    Code Name Conroe
    Specification Intel(R) Core(TM)2 CPU 6700 @ 2.66GHz
    Package Socket 775 LGA
    Family/Model/Stepping 6.F.6
    Extended Family/Model 6.F
    Core Stepping B2
    Technology 65 nm
    Core Speed 1600.0 MHz
    Multiplier x Bus speed 6.0 x 266.7 MHz
    Rated Bus speed 1066.7 MHz
    Stock frequency 2666 MHz
    Instruction sets MMX, SSE, SSE2, SSE3, SSSE3, EM64T
    L1 Data cache 2 x 32 KBytes, 8-way set associative, 64-byte line size
    L1 Instruction cache 2 x 32 KBytes, 8-way set associative, 64-byte line size
    L2 cache 4096 KBytes, 16-way set associative, 64-byte line size

    Chipset & Memory

    Northbridge Intel i975X rev. A0
    Southbridge Intel 82801GB (ICH7) rev. 01
    Graphic Interface PCI-Express
    PCI-E Link Width x16
    PCI-E Max Link Width x16
    Memory Type DDR2
    Memory Size 8192 MBytes
    Memory Frequency 333.3 MHz (4:5)
    CAS# Latency (tCL) 5.0 clocks
    RAS# to CAS# (tRDC) 5 clocks
    RAS# Precharge (tRP) 5 clocks
    Cycle Time (tRAS) 15 clocks
    Bank Cycle Time (tRC) 21 clocks

    System

    System Manufacturer
    System Name
    System S/N
    Mainboard Vendor Intel Corporation
    Mainboard Model D975XBX2
    BIOS Vendor Intel Corp.
    BIOS Version BX97520J.86A.2674.2007.0315.1546
    BIOS Date 03/15/2007

    Memory SPD

    Module 1 DDR2, PC2-5300 (333 MHz), 2048 MBytes, Kingston
    Module 2 DDR2, PC2-5300 (333 MHz), 2048 MBytes, Kingston
    Module 3 DDR2, PC2-5300 (333 MHz), 2048 MBytes, Kingston
    Module 4 DDR2, PC2-5300 (333 MHz), 2048 MBytes, Kingston

    Software

    Windows Version Microsoft Windows XP x64 Professional Service Pack 2 (Build 3790)
    DirectX Version 9.0c

    DG
  • D
    D
    DG,

    Thanks a million for providing that info! I will try to glean something of use from it tonight when I get home.

    David
  • D
    D
    [quote=DM33]DG,

    Good luck. [;)]

    DG
  • cmC
    VSL Team
    cmC

    david it seems i managed to screw up the machine during some tests and am finally in the boat with you :-/

    unfortunately i noticed this too late and can't reproduce the step where this issue happened now.

     

    there is no time left for playing around this week so i have to ask you for some more patience ...

    christian

     

    edit: you won't beleive it .... it seems the issue is related to corrupt sample data (a sector from a harddisk fails or similar)

     

    solution: open directory manager, remove all content, add some content

    (you should notice the memory is increasing to 800 MB only opening the DM without having any VE opened before)

    reboot - open VE ... back at 300 something ... (thx to george for the clever idea)

     

    after adding the corrupt data the effect returns ... isn't that weired?

    now we just need to find out what affects the taskmanager to show this amount of used memory even without any process listed ...

    and remember: only a CRAY can run an endless loop in just three seconds.
  • D
    D
    Hi cm,

    I will try this as soon as I get home.

    So, this problem occurs with just the DM open?! Wow, that is weird.

    I will remove all content and then add some back and see what happens.

    Should I reinstall the VI content from the DVD's? On this new computer I networked it
    to my old one and copied the data over. Was that a bad idea?

    I'll keep you posted, David
  • cmC
    VSL Team
    cmC

    probably it is less timeconsuming top find which collection contains the corrupted data than to re-install all, the one which is found to be responsible for the issue i would re-copy or re-install of course.

    christian

    and remember: only a CRAY can run an endless loop in just three seconds.
  • J
    J
    Thanks for tracking this down, Christian.
    I'll track down my corrupt library sometime this afternoon.

    J.
  • K
    K
    all right!! We're getting close
  • D
    D
    Hi cm,

    So, just to clarify.

    1) I empty the DM
    2) Add 1 volume of VSL data
    3) Close DM and relaunch DM and see what happens with RAM?
    4) If normal add another volume
    5) Repeat until Commit Charge in TM goes crazy
    6) Most recent volume added is corrupt, remove it from DM continue to next volume
    7) After all volumes done and corrupt ones discovered then only reinstall corruted volume(s)

    Right?

    If this works I will be ecstatic!

    Thanks cm!!!!
    David
  • cmC
    VSL Team
    cmC

    you forgot to reboot between 2) and 3) .. otherwise you wouldn't free the memory and see ... nothing ...

    and remember: only a CRAY can run an endless loop in just three seconds.
  • D
    D
    Ok. I'll reboot every time I add a volume.
    Its going to be a long process but hopefully it will take care of the problem.
    David
  • cmC
    VSL Team
    cmC

    ;-) of course you only need to reboot (maybe log off / log on is enough) if the memory goes up again more than normal ...

    and remember: only a CRAY can run an endless loop in just three seconds.
  • D
    D

    Hi cm,

    Here is my feedback:

    I cleaned out the DM and rebooted. Checked my Committed RAM in TM with nothing launched, its 225mb. Opened the DM, FireFox so I can type this, and the TM.  Lastly I open the Windows Explorer. My Committed RAM at this point is 253mb.

    Now, I drag and drop the VSL Percussion data folder of the Cube into the DM from Explorer. This folder is 51.3gb. My Committed RAM jumps to 357mb, thats 104mb. Normal? 

    Now, I will reboot and re-open the DM and do a scan and see what happens.

    I will edit this post when I'm back up...be back in 2 minutes. 

    Ok, I'm back.

    Launched TM, DM, and Firefox. Committed RAM is at 257mb. Only Percussion data is in DM. Clicking Rescan...Commited RAM jumps up to 358mb, pretty much the same as before.

    I'll add another data folder to the DM with the Percussion already there, this time Brass II which is 39gb. Committed RAM goes up to 441mb, thats a rise of another 83mb. 

    Adding Orch Strings II 18.9gb, now RAM jumps to 473mb, another 32mb.

    I'll finish off this drive and add the WoodWinds II which is 44.8gb, now RAM is at 546mb, a rise of 73mb.

    So I started with 225mb with nothing launched. Added Percussion, Brass II, Orch Str II, and WW II to the DM. Total of 154gb of data and my Committed RAM rose to 563mb, thats rise of 338mb. That can't be normal, right?

    If we minus the RAM it takes to run the DM we wind up with a Commintted RAM of 554 so its 329mb of vanished RAM.

    When I close DM the RAM is not released. I have to reboot to get it all back.

    One thing I did not mention is that I have previously loaded only one volume at a time into the DM and rebooted to see if one of the volumes was the problem. After checking and noticing the RAM was still jumping up is when I decided to write this. 

    This is driving me nuts!

    Any ideas?

    Like I said, the data files were copied from another computer to this one via ethernet. My other computer is a WinXP32 system that is now no longer used. I guess all my data could be corrupted from the copying but I bought the Vienna Bosendorfer recently and installed directly to this machineand I have the same problem with that as well.

    All my VSL data is spread across 3 internal seagate drives and no matter which drive I use to drop data folders in the DM the RAM goes up like this.

    What should I do?

    I'll try anything.

    David