Announcement
Collapse
No announcement yet.
Partner 728x90
Collapse
NinjaTrader
Heavy Load - UI Unresponsive when hovering on a Workspace
Collapse
X
-
Heavy Load - UI Unresponsive when hovering on a Workspace
On a heavily loaded system (lots of charts and indicators) a situation occurs in which one can click on the Workspaces menu heading on control center, and the list of workspaces drops down immediately. However, normally, when one hovers the mouse over a specific workspace, a sub-menu pops up that has the options to Save or Save As - this does not happen or does not happen for a long time. If one instead clicks on the workspace (as if to switch to it) that happens immediately, and if one clicks off of the Workspaces menu the menu closes immediately. The one thing that does not happen correctly is it does not pop up the menu that has Save and Save As on it, or it does not do so until you move the mouse around and wait a very long time.Tags: None
-
Hello QuantKey_Bruce ,
Thank you for reaching out.
I was not able to reproduce this on my end. I tested on the latest version 8.1.3.1.
The "Save / Save / Close / Remove"
Options are showing up immediately/statically on any active Workspace as well as any "background" workspace that is open.
Inactive workspaces will only show "remove"
Typically, when basic.default functions sometimes works and sometimes they do not, it is either an installation issue, or an case where customizations/heavy workspaces are affecting the platforms UI and general rendering. The exact cause of this type of behavior would be hard to determine.
I would recommend a repair to your NinjaTrader 8 platform to try correcting this behavior. To complete a repair, do the following:- Shut down NinjaTrader 8
- Go to your computer's Control Panel > Programs & Features (Note: search for 'Control Panel' to find it within the Windows Start Menu. This will be a different window than the Settings page)
- Left-click once on NinjaTrader 8 > select 'Repair' above the list of available programs
- Restart the platform after it finishes repairing, and test for this behavior again.
- Here is a video I made for your reference: https://www.screencast.com/t/5RH7MjuaQiG
Please me know the results of this test. If the same occurs after the repair:
Next try testing your platform in Safe Mode to verify if this behavior is caused by a 3rd-party add-on or is isolated to your Workspace using the steps below. Safe Mode will prevent NinjaTrader from:- Loading workspaces and connecting on start-up.
- Loading custom assemblies (3rd-party add-ons and NinjaScripts)
- Getting instrument updates from the server
- Go to the Windows Start Menu
- Search for NinjaTrader > select 'NinjaTrader (Safe Mode)'
- Once you have opened the platform in Safe Mode, you may manually connect to your Data Provider from the Connections dropdown
Once you are connected, open a new chart with no custom bar types, indicators, or templates and test for issues. Does the behavior persist on this blank Workspace in Safe Mode?
If not, please try opening your previous workspace from the Control Center > Workspaces dropdown. It may already appear as open. Hit 'close' and do not save, then re-open it again for your windows to appear. You will notice that no 3rd-party add-ons are available in Safe Mode. Does the behavior return to your regular Workspace in Safe Mode?
If not, restart NinjaTrader normally, and test for the behavior on your Workspace normally once more with your 3rd-party add-ons available. If the issue returns, we suggest rebuilding your workspace. Keep track of each add-on you implement to identify the cause of the behavior should it return. If the issue does not resurface, it confirms the error was isolated only to your other Workspace.
We also suggest backing up your workspace (Tools > Export > Backup) so you may restore a working version if the issue returns. Additional information about backups may be read here in our Help Center.
Please let us know the results of this test. We look forward to your response.
Erick P.NinjaTrader Customer Service
Comment
-
You're missing the fact that this only happens under heavy load. What did you do in your test scenario to simulate a heavy CPU load? This happens in situations in which there are 50+ windows open streaming 24+ futures contracts over several time frames, each running a number of indicators. The machine in question has 16 CPUs and is usually about 10% CPU usage but occasionally higher in fast market conditions.
If there are only a few windows open running only a few indicators, this never happens.
Comment
Latest Posts
Collapse
| Topics | Statistics | Last Post | ||
|---|---|---|---|---|
|
Started by argusthome, 03-08-2026, 10:06 AM
|
0 responses
60 views
0 likes
|
Last Post
by argusthome
03-08-2026, 10:06 AM
|
||
|
Started by NabilKhattabi, 03-06-2026, 11:18 AM
|
0 responses
39 views
0 likes
|
Last Post
|
||
|
Started by Deep42, 03-06-2026, 12:28 AM
|
0 responses
21 views
0 likes
|
Last Post
by Deep42
03-06-2026, 12:28 AM
|
||
|
Started by TheRealMorford, 03-05-2026, 06:15 PM
|
0 responses
23 views
0 likes
|
Last Post
|
||
|
Started by Mindset, 02-28-2026, 06:16 AM
|
0 responses
51 views
0 likes
|
Last Post
by Mindset
02-28-2026, 06:16 AM
|

Comment