Power editor locking-memory usage

Questions about MultiCharts and user contributed studies.
jl12
Posts: 220
Joined: 29 Jun 2007
Has thanked: 10 times
Been thanked: 9 times
Contact:

Power editor locking-memory usage

Postby jl12 » 01 Jan 2012

When a signal that is already applied to a chart is edited and reverified power editor usually locks for a few minutes.

Every time I verify The PLEditor memory usage goes up -about 40 mb- but never comes down.

Running optimisations can also cause the power editor to freeze and may add a gig to PlEditor
memory usage.

See processes attachment

After reboot its ok for a while then the problem re-occurs.
Attachments
plmemory.png
(103.13 KiB) Downloaded 394 times

User avatar
Henry MultiСharts
Posts: 9165
Joined: 25 Aug 2011
Has thanked: 1264 times
Been thanked: 2957 times

Re: Power editor locking-memory usage

Postby Henry MultiСharts » 03 Jan 2012

Please try to compile your scripts in “Fast Compilation” mode.
Attachments
Fast Compilation.png
(33.15 KiB) Downloaded 388 times

User avatar
JoshM
Posts: 2195
Joined: 20 May 2011
Location: The Netherlands
Has thanked: 1544 times
Been thanked: 1565 times
Contact:

Re: Power editor locking-memory usage

Postby JoshM » 03 Jan 2012

When a signal that is already applied to a chart is edited and reverified power editor usually locks for a few minutes.

Every time I verify The PLEditor memory usage goes up -about 40 mb- but never comes down.
During complication or just after the script is compiled? If it happens after the script is compiled, but while the 'new version' loads, it can also be caused by printing a lot of data to the PowerLanguage Editor output log. That would cause the PLEditor.exe to go "insane"; if you have a coding error in your script (say, an large array sorting on each bar update), you'll see the normal MultiCharts.exe consuming a lot of memory and CPU (Edit: which also seems to happen in your case).

jl12
Posts: 220
Joined: 29 Jun 2007
Has thanked: 10 times
Been thanked: 9 times
Contact:

Re: Power editor locking-memory usage

Postby jl12 » 04 Jan 2012

JoshM
Thanks for the advice there was a print statement buried in the code since removing this the problem has not re-occurred


Return to “MultiCharts”