Out of memory, Clipboard operation did not succeed, WL freezes up. These issues happened on separate occasions, within the same day.

1. 'Out of memory' error when trying to test a strategy on a data set of six stocks wiht 5-minute data (ca 130,000 bars ea).
NOT connected to internet.

2. 'Clipboard operation' errors (2), when editing a strategy, trying to copy a series (Bars.Count) to another line. Two strategies loaded - neither very complicated. The one not being edited had a chart open with 5-minute data. Third WL app loaded: Neuro-Lab, but idling.
NOT connected to internet.

3. Freeze-up while connected to internet, streaming data on single ticker (SPY) enabled. Could not close or minimize WL, nor any of its external windows (indicators, fundamentals, quickref, user guide). Had to end process in task manager. Several other apps running were unaffected.

I have a copy of the last clipboard error details, ca 22 KB. If you want it, tell me how to send it to you.

Eb

1 - Check out the Knowledge base for an in-depth explanation and solutions existing for a long time:

Out of memory problems.

2 - Not necessarily a WL6 error. Might be a conflict with another background process that works with the clipboard e.g. a clipboard utility or remote desktop session (they typically share the system clipboard).

3 - Can you reproduce it with sure? If so, how exactly? Are you sure it's not a temporary glitch of your network connection? or (for example) a message box that somehow got hidden and prevents you from closing or minimizing WL (typical with "optimization complete" messages on multi-monitor configurations)? Is there a screenshot?

Re: log - Could you paste the exception message only, cutting out the part that deals with loaded assemblies?

Here is the code that generates the clipboard error,
which is the default New Strategy code, with some additions I'm trying to add and test, but each time I try to copy the "Bars.Count;" piece to the first option in SCREEN switch, when I copy the code to the clipboard, I get the error. I condensed the default indentations to make it fit w/o wrapping. I was trying to test if the preprocessor directives would work in WealthScript, but
suspect they may be part of the problem. Tell me it isn't so.

CODE:
Please log in to see this code.

Here are the exception messages:

CODE:
Please log in to see this code.

Eb

QUOTE:
1 - Check out the Knowledge base for an in-depth explanation and solutions existing for a long time:

Out of memory problems.

I checked out the link, which basically says

QUOTE:
Required RAM = Number of stocks * number of bars * number of data series (typically 6: DateTime + OHLCV) * 8 bytes

The problem I experienced: 6 stocks * 1320000 bars * 6 data series * 8 bytes = 380,160,000 bytes


My system reports 5.8 GB available (2,218 MB in use, 5,847 MB Available), there must be a different source for this problem.

I wasn't able to duplicate the error the way you described, at least on this PC / OS. Will not claim that I've used all of C# preprocessor directives in WealthScript strategies (that's not true) but most of them like ifs and regions worked.

Seems like an exception happening inside QWhale Editor (the 3rd party editor component that powers the Wealth-Lab's editor). And it sounds like the problem might be caused by some conflicting process working with clipboard in the background. There can be lots of candidates so only you can find it.

Yes, must be a different source then. If that's a particular strategy that produces OOM errors, then start by examining its code for a programming inefficiency. For example, it's easy to do by creating DataSeries in the loop, or some more subtle error - but that's not possible to tell without reviewing the code.