Is your feature request related to a problem? Please describe.
Launching with workbench on Linux systems will bypass the jemalloc configuration setup. Without this, the memory management does not perform well and repeated loading and clearing of large workspaces can cause freezing/crashing as the memory fills up.
There are currently two problems:
mantidworkbench is not an entry point on Windows and macOS
the workbench entry point is not optimal on Linux
Describe the solution you'd like
On Linux there is a mantidworkbench script that configures jemalloc parameters, and other things. We should really be using that for all Linux launches to take advantage of jemalloc. The ideal solution would be:
both workbench and mantidworkbench are entry points on all OS
jemalloc is configured when launching with either entry point on Linux
Is your feature request related to a problem? Please describe. Launching with
workbenchon Linux systems will bypass thejemallocconfiguration setup. Without this, the memory management does not perform well and repeated loading and clearing of large workspaces can cause freezing/crashing as the memory fills up. There are currently two problems:mantidworkbenchis not an entry point on Windows and macOSworkbenchentry point is not optimal on LinuxDescribe the solution you'd like On Linux there is a
mantidworkbenchscript that configuresjemallocparameters, and other things. We should really be using that for all Linux launches to take advantage ofjemalloc. The ideal solution would be:workbenchandmantidworkbenchare entry points on all OSjemallocis configured when launching with either entry point on Linux