Mremoteng: Error when clicking in Search bar

Created on 2 Mar 2017  路  5Comments  路  Source: mRemoteNG/mRemoteNG

Just downloaded 1.75 Final .msi
When clicking in the Search bar field, the error in screenshot appeared.
Attached error log

errorlog.zip

image


See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

*** Exception Text ***
System.NullReferenceException: Object reference not set to an instance of an object.
at mRemoteNG.UI.Controls.ConnectionTree.OnMouse_SingleClick(Object sender, MouseEventArgs mouseEventArgs)
at System.Windows.Forms.Control.OnMouseClick(MouseEventArgs e)
at System.Windows.Forms.ListView.WmReflectNotify(Message& m)
at System.Windows.Forms.ListView.WndProc(Message& m)
at BrightIdeasSoftware.ObjectListView.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

|Operating system | Windows 7 x64 |
|mRemoteNG version| 1.75 Final |

Bug

All 5 comments

Fix will be available in the next release. Cant believe I never encountered this error over months of testing : \

@sparerd Any chance you could re-release v1.75 with the fix? Rather than waiting months for v1.76.

Yea, we may end up doing that. This one is annoying, but the app will continue working without issue by clicking 'continue'. We'll wait a few days to ensure we didnt miss any other bugs.

@sparerd Agreed. This one is annoying and we should get a quick fix out. I have some ideas on how to make some minimal changes to our release pipeline to make it easier for us to issue small updates like this.

@kmscode 馃憤 that would be great

Was this page helpful?
0 / 5 - 0 ratings

Related issues

sparerd picture sparerd  路  3Comments

LIyoai picture LIyoai  路  4Comments

agiz10 picture agiz10  路  4Comments

senseof94 picture senseof94  路  4Comments

pfjason picture pfjason  路  4Comments