Sorry, Zack, there's nothing that can be done about this that I am aware of. As you noted, this is a heap size limit imposed by the Java Virtual Machine (VM), which is what runs Tracker. Tracker uses the following algorithm when it launches:

1. commands the VM to start with the desired heap size
2. if the VM throws a heap size error reduce the requested heap size by 5% and repeat
3. the command will succeed with a size very near the maximum allowed, which is what you saw.

I don't know why the VM will not give you more heap when you have 32GB of memory. Maybe somebody else on this list knows?  Maybe a Java preference?

Doug


> I'm new to using this tool and am trying to allocate
> a lot of memory to it so my tracks will be faster
> (I need to track a long 4k60 video). I set my preferred
> memory (I've tried both in the main menu and in the
> prefs file) but when I start/restart tracker it says:
> "tracker could not be started with memory 8000mb.
> preferred memory was reduced to 1542mb"
>
> I set 8000
> as a test, but anything greater than ~1500 gets reduced.
> I have 32gb of ram and tracker is the only program
> running.
>
> Is there anything I can to to fix this to
> allocate more?
>
> Thanks,
> Zack
>
> EDIT: it throws these
> errors:
>  - failed to start with memory size 8000MB
> due to the following errors:
>       Invalid maximum
> heap size: -Xmx8000m
>       The specified size exceeds
> the maximum representable size.
>       Error: Could
> not create the Java Virtual Machine.
>       Error:
> A fatal exception has occurred. Program will exit.