Vienna Symphonic Library Forum
Forum Statistics

196,053 users have contributed to 43,014 threads and 258,388 posts.

In the past 24 hours, we have 2 new thread(s), 18 new post(s) and 144 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?
  • D
    D
    I'm wondering why its only happening on so few systems.
    Only a couple of people have mentioned the problem.

    I would think it would be a bigger problem. It must be something
    wrong with our specific systems. May RAM type or bad RAM or errors
    on the hard drives.

    I'm going to re-install my OS tonight along with the VI/VE and data.
    I don't have much installed on this machine yet since I just got it.
    I'll keep this thread posted.

    Good luck!
    David
  • cmC
    VSL Team
    cmC

    keep in mind i only proceeded as described above to return to *normal behavior* ..

    although before i uninstalled LCC, VI, VE because i assumed the problem here.

     

    uninstall always means here a clean uninstall from control panel - add/remove software making sure no processes are running followed by a reboot.

     

    bad RAM is no probable reason IMO, you would rather get *could not read* or *could not write* at adress 0x1234567 or something similar.

    a failing harddrive (loosing and incompletely re-assigning sectors) would be a possible reason though.

    christian

    and remember: only a CRAY can run an endless loop in just three seconds.
  • D
    D
    Ok here is another update.

    I re-installed WinXP64 just in case it would help and because I have so
    much time on my hands :-)

    Well, I have the same problem as before, no change. I have used Check Disk on 2 of the 3
    drives which I have also formatted. I have only made this test from the 3rd drive which I have
    not run Check Disk on or formatted. I will do that tonight.

    If none of my current testing works I will install WinXP 32-bit version and see if the problem goes
    away. If it does then it points to my particular WinXP 64 installation.

    I just can't tell if I'm experiencing a VSL issue or a computer hard/software issue.

    The problem points to the Directory Manager. Everytime it scans the data folders my RAM goes bizerk.

    cm any help yet?

    David
  • D
    D

     I hope no one forgot about me.I'm still having this vansihing RAM problem.

    I installed Vista-64 thinking it would show some more info than XP64

    or it would behave differently but its the same with one change.

    It does the DM scan once the system has booted to the desktop!

    Why in the world would it do that?

    Weird thing is that if I turn virtual memory on it does it when I run

    the DM but when I turn VM off then the RAM vanishes right after

    bootup, within a minute.

    Is there some sort of Indexing or database being built? 

    David
  • cmC
    VSL Team
    cmC
    last edited
    last edited

    david, unfortunately i don't even understand this statement

    @DM33 said:

    It does the DM scan once the system has booted to the desktop!

    earlier i reported that i don't like VISTA because it starts with 680 MB memory usage on a *naked* system, which goes down after some minutes to ~ 320 MB (VISTA 32 on a 2 GB machine here) - on the same machine XP32 with an unhealthy amount of applications installed starts with ~ 260 MB memory usage.

    i'd assume VISTA 64 behaves similar and moves some of the memory used at startup to the virtual memory area (if activated only of course)

    btw: have you already found which collection has been responsible for the excessive comit charge? here it have been the solo strings ...

    christian

    ps: i just noticed the ADD FOLDER in the Directory Manager is working recursive now on XP64

     

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

    Hi cm,

    Sorry, that statement was meant to say "Does the DM do a scan once the system has booted up to the desktop?".

    On Vista64 it was doing just that but it was the Vista SuperFetch function. I disabled it and that issue went away.

    Unfortunately my vanishing RAM problem has not gone away.

    I have done a reinstall of WinXp64, hated Vista. I have also chk dsk'ed all my drives and tested my RAM chips for errors and found no problems, everything is fine.

    For testing I rebooted the system, launched the TM and VI, and the RAM shot up just like before. It did not go up as much as before but I only

    have 1 volume installed with 12 to go.

    Copying Orch Str I as I write this and will install that ASAP.

    Will report back to you.

    BTW, I have optimized this machine as I do all my machines but this is the first time I'm using WinXP64. Do you think the optimizations have anything to do with my problem?

    Here is the list of optimizations:

    http://www.musicxp.net/tuning_tips.php

    Let me know what you think or what I could try next.

    Can you explain what SHOULD be happening in regards to RAM when I launch the VI?

    How much RAM should the VI take when it launches and does a data scan for on an Extended Cube system?

    Mine seems to take a GB of RAM. It did not do this on my WinXP32 system.

     

    David

    P.S. - Just finished installing the Orch Str I volume. Rebooted. Only have 2 volumes installed: Chamber Strings and Orch Str I.

    On bootup Commit Charge was at 210mb, after launching VI, not VE, my Commit Charge went upto 416mb. When I close VI

    it only comes back down to 370mb. Why not back to 210mb? 
  • D
    D
    Hey cm,

    I have not heard a response from you or VSL tech support, I sent them a message

    a few days ago to them. My RAM problem occurs whether I have 1 volume or 2 or 3...RAM still disappears.

    I can't imagine that all my volumes or drives are corrupted.

    It only happens with the launch of DM, VI, or VE.

    I bought more RAM so I could just bypass this problem for now but I would like to
    get my 800mb of RAM back.

    I upgraded to 8gb of RAM on the machine but to lose 10% mysteriously just by launching
    anything related to VSL is to much IMO.

    I know you guys are busy with many things and I'm a patient guy but it would be nice to know
    that someone at VSL is working on this.

    Thanks,
    David
  • cmC
    VSL Team
    cmC

    david, reading you mentioned optimization according to musicXP i decided to not continue because of lack of time.

    however i just ha´d a look on their reworked site and found many of the tweaks i thought to remember (a series of registry hacks) have luckily disappeared.

    as a sidenote: i don't understand *Turn off System Restore on all Drives* - i would rather be happy if system restore is active on my system drive, although i also switch it off on all audio drives ... anyway

     

    we can't get the few XP64 systems we currently have available to behave as you describe, so there is nothing to investigate and report unfortunately .... the short intermezzo as mentioned above was immediately gone after removing the corrupt sample data.

     

    if you find the time please check out the famous sysinternal tools and keep us updated if you notice something suspicious

    http://www.microsoft.com/technet/sysinternals/Processesandthreadsutilities.mspx

     

    christian

     

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

    I'll checkout the Microsoft utilities, thanks for the link!
    I was not aware of them.

    Anyone have any suggestions on what to try next?
    This is such an unusual problem. I can't find anything on the web
    for a solution.

    I got new RAM chips yesturday and the problem still
    exists so its not bad RAM.

    This just has to be a VSL issue. No other application behaves this way.

    Hopefully the MS utilities will bring some hidden issue to view.

    Thanks,
    David
  • K
    K
    Im still having the exact same issue. Mine is pretty severe. Sometimes I'll can start off with 1gb missing before I touch anything. Give me a week, I'm gonna show the screen shots. And I am using a Mac Pro
  • D
    D
    last edited
    last edited

    @ktnujynisis said:

    Im still having the exact same issue. Mine is pretty severe. Sometimes I'll can start off with 1gb missing before I touch anything. Give me a week, I'm gonna show the screen shots. And I am using a Mac Pro

    So what does that have to do with XP64?

    DG
  • cmC
    VSL Team
    cmC

    possibly ktnujynisis is running XP64 on a macPro? the mac people here don't allow me to do so ;-)

    and remember: only a CRAY can run an endless loop in just three seconds.
  • K
    K
    same problem... different OS. Which obviously disconnects the problem to the operating systems or he OS's type.................??????????????!!!!!!!!!!!!!!!!??????????!!!!!!!!!!!!!!!!
  • K
    K
    I give up
  • D
    D
    last edited
    last edited

    @cm said:

    possibly ktnujynisis is running XP64 on a macPro? the mac people here don't allow me to do so 😉

    Actually I know someone who does, but it was a real PITA to get to work. I think that they only did it to prove a point!

    DG
  • D
    D
    last edited
    last edited

    @ktnujynisis said:

    same problem... different OS. Which obviously disconnects the problem to the operating systems or he OS's type.................??????????????!!!!!!!!!!!!!!!!??????????!!!!!!!!!!!!!!!!

    Memory handling is so different for XP and OSX that you cannot deduce a connection I'm afraid. Mind you, you did say disconnect, thereby stating that the problem is not connected to the OS. [6]

    DG
  • F
    F
    last edited
    last edited

    @DM33 said:

    I'm wondering why its only happening on so few systems.
    Only a couple of people have mentioned the problem.

    I would think it would be a bigger problem. It must be something
    wrong with our specific systems. May RAM type or bad RAM or errors
    on the hard drives.

    David
    Just to let you know: I´m having the same problem on a G5 2 GHz Dual with Mac OS 10.4.1 and Vienna Ensemble. I hope the support is working on this, since adressing more Ram was one of the new features of Vienna Ensemble!
  • J
    J
    I have to admit that it would be nice to know what's come of this problem. I haven't messed around with it lately, but I was having the same issue on my X64 system. I managed to make it completely reproducible, by emptying my Directory Manager, then loading instruments one folder at a time. The memory "loss" would increase proportionately to the size of the folder loaded, with the Flute Ensemble, for example, only losing about 3 MB, while the Violin Solo lost a whopping 32 MB.
    Christian has referred to this as a data corruption problem with the samples themselves, but that's not too comforting either, as data corruption is a pretty major issue, and is generally caused by something. So the next obvious questions is, what's corrupting the data? And is there any way of tracking it down? Do we really just go ahead and spend x hours re-installing the whole library, in the hopes that it *might* fix the problem? Also, why does the problem manifest itself incrementally, as I described above, as I add folders? Does that mean each folder is somehow corrupted on my system?

    Lots of questions, with very few answers. I can only assume they are, in fact, working on trying to track down the problem, and will post something when they have a better picture of what's going on.

    J.
  • D
    D
    Hi jbm,

    Thanks for your post. We need more people to mention this problem if they are having it.

    I can't get any answers from VSL, although cm has tried to offer advice for which I am grateful.

    VSL seem not to be able to reproduce it this problem. The one time they experienced it it was traced to a corrupt solo strings folder.

    I have reinstalled winxp64. Then deleted my VSL content which is spread across 3 drives and reinstalled
    all my 14 volumes.

    With each volume install I checked the Directory Manager and each time I lost a little more memory.
    Exactly as you describe. With some volumes losing much more RAM then others.

    Can all of my discs be corrupt? They are all new and I ran chk dsk on every drive before installing the volumes.
    Did not find even a single error.

    Can all the VSL discs be corrupt? I store them in a dark, cool place and have only installed them once before.
    Plus I have bought Bosendorfer, App Strings, and Elements besides the cube and they exhibit the same problem.

    Last night I ran PerfMon, thanks to cm for informing me of it. Its quit a handy tool but it just showed me
    that my RAM was being used not where it went.

    I'll keep trying new things and hope something works. As it is I'm losing around 800mb of my 8gb of RAM.

    Thanks,
    David
  • J
    J
    last edited
    last edited

    @DM33 said:

    VSL seem not to be able to reproduce it this problem. The one time they experienced it it was traced to a corrupt solo strings folder.


    Oh, okay. I didn't realize they had traced it to a specific folder. But nevertheless, there shouldn't be a problem with a brand new install. The installer should be checking for errors, and should fail if any occur. I wonder if it could even be something as tricky to pinpoint as a particular drive and motherboard/chipset combination? Sounds far-fetched, but just in case:

    Asus P5K-Premium
    Seagate Barracuda 7200.10 series

    J.