Announcement
Collapse
No announcement yet.
Partner 728x90
Collapse
NinjaTrader
FYI - The Control Center and NinjaScript Output windows dead locked
Collapse
X
-
Hello zacharydw00,
Have you reported the behavior to the author that has uploaded this script?
You have mentioned you added prints. Is there a specific line of code that is causing this behavior to be reproducible?
-
I found the Wave Trend indicator. The name of the listing should be changed to match the indi. name displayed on the chart.
WaveTrend v2 8-20-2019 corrected tag name error WaveTrend is a fast moving, sensitive oscillator with smoothing that is quick to react on crossovers and does its best not to lag price changes. Not much is known about WaveTrend, but it is very popular in MetaTrader. It acts like a tight hugging Jurik JMA or Arnaud‐Legoux […]
Leave a comment:
-
Hi Chelsea,
I've attached the indicator in case you are curious. It may have come from Futures.io. It's just another common oscillator spin-off. Just the simplest of Ninjascript coding. No UI threading, or SharpDX. I doubt this indicator could be the cause. As mentioned before, I think this is a random fluke.
ThanksAttached Files
Leave a comment:
-
Hello zacharydw00,
I didn't find in the User App Share section of the NinjaTrader Ecosystem. Have you contacted the author of the script to report the behavior?
If the script is accessing the UI thread, the most often reason this happens is due to using Dispatcher.Invoke() instead of .InvokeAsync().
Climbing memory may indicate a broken loop or logic that is causing recursion.
I would recommend debugging the script to find where the issue is coming from. (Including confirming if a documented NinjaScript method is causing an issue)
Leave a comment:
-
FYI - The Control Center and NinjaScript Output windows dead locked
I little background on what I was doing. I was looking at the WaveTrendV2 indicator, from the App Share, and reviewing the code. I added some simple Print() statements so I could review some data on the Output window. I customized the indicator colors and saved a default indicator template. After that I added the native Drawing Tool Tile indicator to the chart, so I could mark things. So after customizing the chart, not the chart Properties, I went to the Control center and saved the workspace, and that is when the Control Center and Output window locked up. The chart and NinjaScript Editor were still working fine.
Other info- There were three other workspaces open in the background not being used. The Untitled had nothing, and the other two workspaces had about 4 charts in each workspace.
- The data feed was connected, but there is no data on Saturdays.
- As I'm writing this I noticed the memory usage for Ninja is continuously climbing about 1MB every couple of seconds. It has reached 4,900MB.
Tags: None
Latest Posts
Collapse
Topics | Statistics | Last Post | ||
---|---|---|---|---|
Started by CortexZenUSA, Today, 12:53 AM
|
0 responses
1 view
0 likes
|
Last Post
by CortexZenUSA
Today, 12:53 AM
|
||
Started by CortexZenUSA, Today, 12:46 AM
|
0 responses
1 view
0 likes
|
Last Post
by CortexZenUSA
Today, 12:46 AM
|
||
Started by usazencortex, Today, 12:43 AM
|
0 responses
5 views
0 likes
|
Last Post
by usazencortex
Today, 12:43 AM
|
||
Started by sidlercom80, 10-28-2023, 08:49 AM
|
168 responses
2,265 views
0 likes
|
Last Post
by sidlercom80
Today, 12:05 AM
|
||
Started by Barry Milan, Yesterday, 10:35 PM
|
3 responses
12 views
0 likes
|
Last Post Yesterday, 11:58 PM |
Leave a comment: