We are seeing exactly the same crash in NetAdvantage 2010.2, did this issue get investigated?

This happens infrequently and we are working on reliable reproduction steps. I have raised a support issue as well. Will report back when I have further details

Hello,

Are there any news / solutions / workarounds for this issue? Some clients of our software encounterd the same exception recently. Also infrequently as described above.

Regards

Thorsten

This post is 12 years old, and it does not appear that the original customer who reported it, or anyone else along the line, ever followed up and reported it directly to us, so it doesn't looks like it's ever been investigated. 

From the call stack here, it appears that a RibbonGroup is becoming visible (or invisible) and the ToolbarsManager is trying to determine if it should be processing the mouse input notification. It does this in case it becomes visible (or is hidden) directly under the mouse so it can synch up whether it should be hot-tracked or not. 

Is your application using threads? This could be getting out of synch if your application is using multiple threads and not properly marshalling the data. 

I can't immediately see any case in which it should be blowing up, but the RibbonGroup in question is referencing it's own Ribbon and ToolbarsManager, so it's possible that there's a bug here. 

Is the call stack your users are getting exactly the same as the one listed here? 
It's tough to fix a problem we cannot reproduce, but I don't think it could hurt for us to put some null checks into this method to ensure it doesn't blow up. 

Hello Mike,

the stack trace from our client is nearly the same as in the old post above:

<InnerExceptions>
<InnerException ExceptionType="System.NullReferenceException">
<Number>0</Number>
<Message>Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.</Message>
<Source>Infragistics4.Win.UltraWinToolbars.v19.2</Source>
<TargetSite>Boolean PreventMouseInputNotification(Infragistics.Win.UIElementInputType)</TargetSite>
<Class>Infragistics.Win.UltraWinToolbars.RibbonGroup</Class>
<Assembly>Infragistics4.Win.UltraWinToolbars.v19.2, Version=19.2.20192.198, Culture=neutral, PublicKeyToken=7dd5c3163f2cd0cb</Assembly>
<Method>PreventMouseInputNotification</Method>
<StackTrace>
<StackTraceElements Count="1">
<StackTraceElement Number="1"> bei Infragistics.Win.UltraWinToolbars.RibbonGroup.PreventMouseInputNotification(UIElementInputType inputType)
bei Infragistics.Win.UltraWinToolbars.RibbonGroupUIElement.WantsInputNotification(UIElementInputType inputType, Point point)
bei Infragistics.Win.UIElement.PointInElement(Point point, Boolean excludeOverlappingSiblings, Boolean ignoreClipping, Boolean honorInputType, UIElementInputType inputType)
bei Infragistics.Win.UIElement.ElementFromPoint(Point point, Boolean ignoreClipping, UIElementInputType inputType, Boolean honorInputType, Boolean excludeOverlappingSiblings)
bei Infragistics.Win.UIElement.ElementFromPoint(Point point, Boolean ignoreClipping, UIElementInputType inputType, Boolean honorInputType, Boolean excludeOverlappingSiblings)
bei Infragistics.Win.UIElement.ElementFromPoint(Point point, Boolean ignoreClipping, UIElementInputType inputType, Boolean honorInputType, Boolean excludeOverlappingSiblings)
bei Infragistics.Win.UIElement.ElementFromPoint(Point point, Boolean ignoreClipping, UIElementInputType inputType, Boolean honorInputType, Boolean excludeOverlappingSiblings)
bei Infragistics.Win.UIElement.ElementFromPoint(Point point, Boolean ignoreClipping, UIElementInputType inputType, Boolean honorInputType, Boolean excludeOverlappingSiblings)
bei Infragistics.Win.UIElement.ElementFromPoint(Point point, Boolean ignoreClipping, UIElementInputType inputType, Boolean honorInputType, Boolean excludeOverlappingSiblings)
bei Infragistics.Win.UIElement.ElementFromPoint(Point point, Boolean ignoreClipping, UIElementInputType inputType, Boolean honorInputType, Boolean excludeOverlappingSiblings)
bei Infragistics.Win.UIElement.ElementFromPoint(Point point, Boolean ignoreClipping, UIElementInputType inputType, Boolean honorInputType, Boolean excludeOverlappingSiblings)
bei Infragistics.Win.ControlUIElementBase.SyncMouseEntered(Boolean triggerMouseLeavesOnly, UIElementInputType inputType, Boolean ignoreLastElementEntered)
bei Infragistics.Win.ControlUIElementBase.ProcessVisibleChanged(Object sender, EventArgs e)
bei Infragistics.Win.Utilities.ProcessEvent(Control control, ProcessEvent eventToProcess, EventArgs e)
bei Infragistics.Win.UltraControlBase.OnVisibleChanged(EventArgs e)

Maybe that helps.

Thanks and regards

Thorsten

Hi Thorston, 

I have asked our support team to create a case for this issue and write up a bug for developer review so we can add some null checks to this message. 

Since we cannot reproduce the exception or test it, there's a small chance that this is just a symptom of a larger problem. But it seems likely that this is just a rare edge case where the controls is hitting this code before the RibbonGroup has had it's backward pointers to the ribbon or ToolbarsManager initialized and the null checks should fix it. 

Hi Mike, we have seen in the latest version that the problem is unfortunately still not fixed. The scenario described above still occurs with us from time to time. Can you say something about the current status and whether there are still plans to implement the security check against null?

Is it possibly better to create an official support request as a customer?

Yours sincerely, Thorsten Pontow.

Thanks Mike!