+1 888 340 6572
MultiCharts Project Management
previous_open_issue.png
Go to the previous open issue
previous_issue.png
Go to the previous issue (open or closed)
star_faded.png
Please log in to bookmark issues
bug_report_small.png
Open Bug report MC-1912

PowerLanguage Editor consumes a lot of memory

action_vote_minus_faded.png
0
Votes
action_vote_plus_faded.png
next_issue.png
Go to the next issue (open or closed)
next_open_issue.png
Go to the next open issue
Description

I believe there's a memory leak within the PowerLanguage Editor.
Having it open for last 2-3 hours and having two windows opened with two signals, I can see PLEditor.exe proc consuming 1.8GB of Memory, and CPU consumption at a constant 14%.
Strange, this was not catched in the test cycle, and could by quite annoying for the user.
Windows 7 Pro x64 (8GB RAM, 256SSD) MacBook Pro 15 retina machine (with bootcamp).
Using latest MC x64 beta (latest to date).

Steps to reproduce this issue

Use it for 3-4 hours. Compile 2-3 signals while having a chart open and do some optimization on your signals.

Comments (3)
#0
user-offline.png  Alex MultiCharts (Alex MultiCharts)
Feb 11, 2016 - 10:16

Please let us know if the issue is reproduced on a Windows computer, as we did not test MultiCharts with parallels and do not guarantee that it will work with no issues.

#1
user-offline.png  andb (andrei.reiand@gmail.com)
Mar 20, 2017 - 18:29

Print something in your code while optimizing - this is killing the editor.
I think the app should be smart enough - when optimization occurs, no printing should be done. Only when applying a strategy should print occur for troubleshooting purposes.

#2
user-offline.png  Alex MultiCharts (Alex MultiCharts)
Jun 07, 2017 - 08:54

1) "Use it for 3-4 hours. Compile 2-3 signals while having a chart open and do some optimization on your signals." - If you want us to test this case, please send us the Workspace, export of data used on it and the exact steps how to reproduce the issue to support@multichrats.com

2) "Print something in your code while optimizing - this is killing the editor.
I think the app should be smart enough - when optimization occurs, no printing should be done. Only when applying a strategy should print occur for troubleshooting purposes." - Print is used for script debugging, and that is why it works this way. If you want to disable printing when optimization is executed, add printing under the following condition:
if getappinfo (aioptimizing) = 0 then
If you print into Output and not in a file, then you just need to not open PL Editor while optimization is running.

History
Issue basics
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (2)
People involved
Times and dates
  • Posted at
  • Last updated
Issue details
  • Reproducability
    Not determined
  • Severity
    Normal
Attachments (1)
Commits (0)
There are no code checkins for this issue
Duplicate issues (0)
This issue does not have any duplicates