+1 888 340 6572
MultiCharts Project Management
Go to the previous open issue
Go to the previous issue (open or closed)
Please log in to bookmark issues
Closed Feature request MC-682

Annoying pop-up window "Your PC is running out of memory"

Go to the next issue (open or closed)
Go to the next open issue
icon_info.png This issue has been closed with status "Released" and resolution "Not determined".

The pop-up window "Your PC is running out of memory" is always coming back. This is really annoying. I want it to go forever. This information could be shown in a small information field next to the "Authorized" area (but not blinking or anything annoying). Another possibility would be to add a "never show again" checkbox in the warning window.

Steps to reproduce this issue

Just load a 1-min chart with 3 years of data or a 10-second chart with some months of data. The window appears and will never go away. It will blink you nuts.
In my case, the window appears after I have opened the strategy performance report on a strategy with 3 years of 1-min bars (bid and ask). Even after I have closed the strategy performance report, the window stays there. So there also must be a memory hole in the strategy performance report.

Comments (2)
user-offline.png  MultiCharts Support (MultiCharts)
10 de nov de 2011 - 20:12

After 64 bit release, no alert message will be there.

user-offline.png  MultiCharts Support (MultiCharts)
07 de abr de 2017 - 14:18

It can be also disabled in the Registry. Find HKEY_CURRENT_USER\Software\TS Support\YOUR MULTICHARTS VERSION\MemoryMonitor path and set PhysicalMemory to 0.

Issue basics
  • Type of issue
    Feature request
  • Category
  • Targeted for
    MultiCharts 9.1 (RELEASED)
  • Status
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (3)
People involved
Times and dates
  • Posted at
  • Last updated
Issue details
  • Resolution
    Not determined
  • Severity
Attachments (0)
There is nothing attached to this issue
Commits (0)
There are no code checkins for this issue
Duplicate issues (0)
This issue does not have any duplicates