crazy memory consumption

[derAbgang]

I have 16-cores with 32GB memory running windows 7 x86_64 and Notion4 64 bit (latest update).

Here are the completely repeatable steps:

1) reboot machine
2) start VEP5 load entire orchestral template
-> 5GB memory "in use"
3) start PlogueBidule (64 bit)
4) start Notion4 and choose a project using the VEP5 template
-> while the 'Loading plugins" splash is displayed, Notion4 starts gobbling up memory until all 32GB are exhausted, paging begins and I have to reboot -- nice

My assumption is that PlogueBidule has something to do with it, in particular, something with Rewire (slave/host).
I can't really say for sure but it is ridiculous. Maybe it is Notion4 (started stand-alone) thinking it is a rewire slave because PlogueBidule can be a rewire host and this infinite loop of trying to load VEP5, PlogueBidule trying to load Notion4 happens -- my only theory at the moment.

Not opening PlogueBidule first and then starting Notion4 loads the project in < 1s.

Crazy ...

David

[wcreed51]

If you're using VEP, why would you need Bidule?

[derAbgang]

If you're using VEP, why would you need Bidule?

VEP (server) only exposes audio outputs to its VST(i) (usually on a client machine), Bidule is the Plugin container exposing audio outputs to my interface.

Code: Select all

CLIENT:
bidule [ VST(i) ]  => audio interface
           |
SERVER:    |
           |
          VEP (no audio interface)


Now I don't usually use both bidule and notion on the client at the same time; notion will load the VEP VSTi by itself but I just happened to leave bidule open when starting notion and notion went (repeatable) bonkers.

[wcreed51]

VEP send the audio outputs of the VSTi back to the host, which in turn sends to the audio interface...