N7 Beta10 Crashing on startup

[pauly139]

Hi

Have NT7 B10 32bit running on W7.

Around 90% of the time NT7 crashes on startup when it is loading available connections. I only have one connection which is Zenfire via Mirus futures.

Those times when it does start it can connect to zenfire ok.

This makes it virtually unusable for me.

Rgds
Paul.

[NinjaTrader_Dierk]

Please be specific on the issues you're experiencing. What kind of message are you getting?

[pauly139]

Hi

The standard windows message

'NinjaTrader has experienced a problem....'

which appears when an application crashes.

I've uninstalled NT7, removed it's \documents\Ninjatrader 7\... entries, rebooted my machine, and am now trying a reinstallation. This time I won't import my 6.5 data and see how it goes.

I'll let you know what happens.

Paul.

[pauly139]

Message is..

Ninjatrader has detected a problem and needs to shut down. Information has been written to the trace file. Please restart Ninjatrader and send us an email.....

Tried to send email however I received an 'unable to connect to SMTP server' message.

Paul.

[NinjaTrader_Dierk]

Could you please paste the relevant sections regarding the exceptions you experience from the trace file located in <my documents>/NinjaTrader7/trace here? Thanks

[pauly139]

haha - NT7 hasn't crashed in the last 30 mins or so, maybe the gremlins got scared off!!

As soon as it happens again I'll post the trace log.

Rgds
Paul

[NinjaTrader_Dierk]

The relevant info still is in the trace file. I would be of value if you could look and paste here. Thanks

[pauly139]

Trace attached

[WES107]

Had same problem as Pauly139 below, same error as #4, I uninstalled nt7 and the documents folder, reinstalled and migrated data no problem then started building default chart and added WoodiesCCI indicator that comes with B10. When I was done with the settings I got another standard error as in #4 below. Here is the relevant part of the trace file but it refers to Woodiespivots which I did not load at all.

2010-02-24 21:24:16:246 in OnUnhandledThreadException
2010-02-24 21:24:16:246 ********* exception trapped *********
2010-02-24 21:24:16:246 Object reference not set to an instance of an object.
2010-02-24 21:24:16:246 at NinjaTrader.Indicator.WoodiesPivots.InvalidateNow( )
at System.Windows.Forms.Control.InvokeMarshaledCallba ckDo(ThreadMethodEntry tme)
at System.Windows.Forms.Control.InvokeMarshaledCallba ckHelper(Object obj)
at System.Threading.ExecutionContext.runTryCode(Objec t userData)
at System.Runtime.CompilerServices.RuntimeHelpers.Exe cuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
at System.Threading.ExecutionContext.RunInternal(Exec utionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ExecutionContext.Run(ExecutionCon text executionContext, ContextCallback callback, Object state)
at System.Windows.Forms.Control.InvokeMarshaledCallba ck(ThreadMethodEntry tme)
at System.Windows.Forms.Control.InvokeMarshaledCallba cks()

[NinjaTrader_Dierk]

pauly: Could you please uninstall the 3rd party software EAProtected.dll, restart NT and see if the issue is resolved? Thanks

[NinjaTrader_Dierk]

wes: your problem is different and related to the Pivots and WoodiesPivots only. Please hold off using them for now. We're looking into. Thanks

[NinjaTrader_Dierk]

wes: please try this:
- uninstall NT7
- clear your browser cache
- install again from link you got provided

Issue should be gone then

[pauly139]

I totally uninstalled again, removed all asociated data, then installed without the EA DLL. I also didn't migrate any data from 6.5

No crashing.

Installed the EA DLL. Still no crashing.

The only times I have had the instability is when I have migrated my 6.5 data. This happened twice (2 installations with migration, 2 without).

I had around 3.5GB of replay data. However with the Historical Data Manager it was easy enough to replace that.

I'll let you know if the crashing reappears.

[NinjaTrader_Dierk]

Sounds good. Glad it's working for you.

[pauly139]

OK NT7 is now proving very unstable - crashed 3 times in the last 30 mins or so.

Trace and screenshot attached. Note that this last crash is with EAProtected.DLL assembly removed.

[NinjaTrader_Dierk]

This line indicates that you still had the EA software installed, which resulted in a crash:
2010-02-25 09:08:00:305 Loading 3rd party C:\Users\Paul\Documents\NinjaTrader 7\bin\Custom\EAProtected.dll...

In addition there appears to be in issue with indicators (e.g. the MACDBBLinesTS_v3). What you have reproducible scenarios? Thanks

[pauly139]

If you have another look at the trace you will see that it covers 3 crashes. The third crash was after EAProtected.dll was removed, so it can't have been the culprit that time.

To reproduce all I do is start NT7 and leave it running for 10 mins...

[NinjaTrader_Dierk]

Which is what I'm saying...

Om crash 3: what would be your exact setup?

[pauly139]

I have only 2 charts, a 233 tick and 610 tick charting ES 03-10. Each chart has 3 indicators:

Keltner bands
Lin.reg
MACDBB

Using zenfire via Mirus Futures

[NinjaTrader_Josh]

pauly139,

Can you please provide us with the MACDBB indicator you are currently using? Thank you.

[pauly139]

Here you go...

[pauly139]

Can someone please advise whether this issue is still being investigated, whether a problem was found with the supplied indicator, or whether a problem was found in NT7. This will help me decide where to spend my time.

Thanks.

[KBJ]

I gave a quick look at it and noticed that it has a complicated/extensive Plot method, and some of the undocumented interfaces for the Plot method have changed in V7. I had some indicators that were working in Beta 5 and 6 that broke in either Beta 7 or 8, so I suppose this could be another one.

In spite of the fact that I consider the undocumented V7 interface for the Plot method to be superior to that used in versions 6.0 and 6.5, it might be worthwhile for the NinjaTrader staff to consider supporting the portion of the 6.x interface involving the values of base.ChartControl.LastBarPainted and base.ChartControl.BarsPainted.

There were so many 6.0 and 6.5 indicators that were derived from one-another based on these values of base.ChartControl.LastBarPainted and base.ChartControl.BarsPainted, that in my opinion, it would be a good investment of time if these two values were maintained compatibly for V7.

In the long run, the time investment to do this additional support might be less than all the cutting and pasting oUnsf "that's not a supported feature" that will be generated once this becomes a public beta, as there are many indicators in the forums download section which rely on this interface and all of them will break.

Just something to think about.

[NinjaTrader_Dierk]

Can someone please advise whether this issue is still being investigated, whether a problem was found with the supplied indicator, or whether a problem was found in NT7. This will help me decide where to spend my time.

Thanks.
We're investigating that issue and will let you know as it's resolved.

[NinjaTrader_Dierk]

I gave a quick look at it and noticed that it has a complicated/extensive Plot method, and some of the undocumented interfaces for the Plot method have changed in V7. I had some indicators that were working in Beta 5 and 6 that broke in either Beta 7 or 8, so I suppose this could be another one.

In spite of the fact that I consider the undocumented V7 interface for the Plot method to be superior to that used in versions 6.0 and 6.5, it might be worthwhile for the NinjaTrader staff to consider supporting the portion of the 6.x interface involving the values of base.ChartControl.LastBarPainted and base.ChartControl.BarsPainted.

There were so many 6.0 and 6.5 indicators that were derived from one-another based on these values of base.ChartControl.LastBarPainted and base.ChartControl.BarsPainted, that in my opinion, it would be a good investment of time if these two values were maintained compatibly for V7.

In the long run, the time investment to do this additional support might be less than all the cutting and pasting oUnsf "that's not a supported feature" that will be generated once this becomes a public beta, as there are many indicators in the forums download section which rely on this interface and all of them will break.

Just something to think about.
Please take a close look at the NT7 "code breaking" section to understand on how to handle your scenario.

[NinjaTrader_Dierk]

Can someone please advise whether this issue is still being investigated, whether a problem was found with the supplied indicator, or whether a problem was found in NT7. This will help me decide where to spend my time.

Thanks.
I believe we isolated the cause of trouble. A fix will be available with next update. Thanks for reporting.

[pauly139]

Great to hear. Thanks for the update.

Paul.

[KBJ]

Please take a close look at the NT7 "code breaking" section to understand on how to handle your scenario.
Yes, I've read that several times.

My scenario is handled. I've fixed all the indicators that my group currently uses, and it was a pain in the butt.

There are a number of other indicators that are found posted on this forum that will all break, and I understand that code that should reference GetXByBarIdx and GetYByValue must be changed. However, that's no reason to break the bar iteration interface, when it's a simple change to not break it.

I was just trying to give you a suggestion that might help prevent many more postings on this topic. But it's your product so feel free to ignore any and all helpful suggestions that I make.

Sometimes I get the feeling that you don't really read my postings. Or that you just read the first sentence and assume that you know what the rest of its going to say and then just give me a quick answer. Well I guess that's better than when you completely ignore my suggestions altogether.

[NinjaTrader_Dierk]

Thanks for your feedback.

[pauly139]

Hi
I'm pleased to report that Beta 11 doesn't crash with this indicator (sent to you earlier in this thread).

However something else very strange is happening with it - when scrolling back through history the indicator starts to paint itself incorrectly. Pressing F5 fixes it until you scroll back some more, and then it paints incorrectly again.

If you want me to send the indicator in again let me know.

[NinjaTrader_Josh]

Please send it in again Pauly39. Thank you.

[pauly139]

Here you go.

[NinjaTrader_Jason]

Hello Pauly139,

I tested the indicator on my end, however when I scrolled the chart the dots remain on top of the black lines that are part of the indicator.

Could it be the line in your screenshot is a line from the cross hair?

Can you please create a new chart and check again.