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
    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.
  • F
    F
    I´m not sure, if I have exactly the identical problem. (In my case I load logic, and everything is fine, until I load a Vienna Ensemble plugin, which claims to use 440 MB of samples, but in total I loose about 1,4 GB Ram) Would it help, if I send pictures of my activity monitor before and after loading VE?
  • cmC
    VSL Team
    cmC

    james, david: apples and pears .... while david reports to loose 800 MB in commit charge just by opening the VE you tell us abot (loosing?) 32 MB when loading solo strings.

    i wrote, that i could fix a similar issue david had removing a collection with obviously corrupt data.

    some mac guys tell us they notice increase of the _inactive_ memory (i posted already a link to what inactive memory is) - so where is the common denominator?

    sorry, either i'm too blind to see it or there is none.

    each operating system has some sort of memory management which can in mosT cases not be detirmined by an application.

     

    i would exclude reasons like chipset, memory, processor (except it is really faulty of course, but this would be another story) - more interesting would be *features* like pre-fetch, running services, pagefile settings and this kind.

     

    see the thread about XP giga and memory management: defined situations give defined results, and even those differ between identical machines sometimes. we should choose a more systematic approach, because you have to know i'm not the engineer responsible for setting up your machines guessing your details - i can run a defined series of test on the few machines i have under my control and we can discuss issues, ideas and solutions here.

     

    thx, christian

     

    ps: of course a screenshot with all relevant information from activity monitor/taskmanager helps ...

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

    I have to clarify my situation because I see it referenced incorrectly a few times.

    My RAM gets lost EVERYTIME I run ANY VSL product!

    It happens with VI, VE, and Directory Manager (DM).

    When I launch the VI or VE during start up they do a scan for locations of the data. I can hear my hard drives getting scanned. It happens after the syncrosoft dongle light goes on and off a few times then the Committed RAM skyrockets.

    It seems like its loading samples into RAM but I don't have any default patches or presets setup.

    When I launch the Directory Manager it happens when I hit the Scan button. I can hear it scan my hard drives
    and then the RAM skyrockets.

    Its loading samples into memory??? but why?

    If I shutdown the application the RAM never goes back down.

    If I relaunch any of the applications (VI, VE, or DM) then they launch without taking
    further RAM since the scan was already done previously.

    I have to reboot the machine to retrieve my lost RAM.

    Anyway, just wanted to clarify.

    Thanks,
    David
  • cmC
    VSL Team
    cmC

    david, is it still the same issue we started talking about (commit charge increases, but we don't see any process listed using it)?

    i had this too for a few hours but have not been able to get this (mis-)behaviour back so far ...

    christian

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

    Yes, its the same issue.

    Commit charge increases but the process list does
    not show anything using that much ram.

    Do you mean you experienced this behavior today?

    David
  • cmC
    VSL Team
    cmC

    no, not today - 3 pages ago ;-) http://community.vsl.co.at/forums/p/17099/122814.aspx#122814

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

    Ok, I figured that, but had to ask.
    David
  • F
    F
    Has anyone found a solution for this bug yet? Is there gone be an update soon?
  • D
    D
    This issue fizzled out into oblivian.

    Doesn't seem to be reproduceable by anyone at VSL
    so they can't test it.

    Hard to resolve if you can't reproduce.

    DM