+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
feature_request_small.png
Open Feature request MC-536

Set the LARGEADDRESSAWARE flag when compiling MultiCharts

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

It is not uncommon for your users to run out of memory. If you set the LARGEADDRESSAWARE flag in the MultiCharts executable, more memory becomes available to the program, changing the memory available from around 2GB to around 3-4GB depending on whether Windows is 32 or 64 bit. One of your users posted on the forum that he had set this flag with a modification to the executable and has noticed no adverse side affects while doubling the memory available to the program from 1.8GB to 3.6GB. It would be best if the flag were set with an option that runs an executable patcher, since a user's system should have over 3GB of RAM to work properly with this option. Has the most gain on a 64bit operating system.

Steps to reproduce this issue

-Run MultiCharts.exe. Note the amount of Virtual Memory available to the program in the Task Manager.
-Using an executable flag setting program, set the LARGEADDRESSAWARE flag of MultiCharts.exe (directions in your forum, search for LARGEADDRESSAWARE).
-Run MultiCharts.exe. Note the amount of Virtual Memory available to the program has increased substantially.

Comments (1)
#0
user-offline.png  Dave (Dave)
Feb 15, 2012 - 20:26

The issue is solved in MC 8.0 64 bit

History
Issue basics
  • Type of issue
    Feature request
  • Category
    Usability
  • Targeted for
    MultiCharts 8.0 (RELEASED)
  • Status
    Released
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
    Low
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