BSL-crash report

Ben

when I open this tool, then crash.........

there is report:

Program Version: 5.0a SR-1 (5.0.1.0241)

Windows Version: 6.2.9200.0

Error ID: 185

Error detail: NullReferenceException: Object reference not set to an instance of an object.

System.NullReferenceException: Object reference not set to an instance of an object.

at Logos.WebBrowser.WebBrowserModel.GetBitmap()

at Logos.WebBrowser.Windows.WebBrowserControl.OnRender(DrawingContext dc)

at System.Windows.UIElement.Arrange(Rect finalRect)

at System.Windows.ContextLayoutManager.UpdateLayout()

at System.Windows.ContextLayoutManager.UpdateLayoutCallback(Object arg)

at System.Windows.Media.MediaContext.InvokeOnRenderCallback.DoWork()

at System.Windows.Media.MediaContext.FireInvokeOnRenderCallbacks()

at System.Windows.Media.MediaContext.RenderMessageHandlerCore(Object resizedCompositionTarget)

at System.Windows.Media.MediaContext.AnimatedRenderMessageHandler(Object resizedCompositionTarget)

at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)

at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)

at System.Windows.Threading.DispatcherOperation.InvokeImpl()

at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(Object state)

at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)

at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)

at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)

at System.Windows.Threading.DispatcherOperation.Invoke()

at System.Windows.Threading.Dispatcher.ProcessQueue()

at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)

at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)

at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)

at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)

at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)

at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)

at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)

at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)

at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)

at System.Windows.Threading.Dispatcher.PushFrame(DispatcherFrame frame)

at System.Windows.Threading.Dispatcher.Run()

at System.Windows.Application.RunDispatcher(Object ignore)

at System.Windows.Application.RunInternal(Window window)

at System.Windows.Application.Run(Window window)

at LDLS4.OurApp.InitializeAndRun(ReadOnlyCollection`1 listArgs, SingleInstanceManager sim)

at LDLS4.OurApp.Main(String[] astrArgs)

Find more posts tagged with

Comments

Dave Hooton

Your awesomium.log might be helpful (from just after a crash) - located in \Documents\Logos Log files. Please attach the file to your post using the paperclip icon.

Ben

https://community.logos.com/discussion/comment/434658#Comment_434658

Thanks Dave,

5141.awesomium.log

Patrick S.

https://community.logos.com/discussion/comment/434679#Comment_434679

That log does show a crash but to get the complete picture it would be good to have all logs. The following Wiki links have information:

http://wiki.logos.com/Windows_Troubleshooting#Diagnostic_Logs

and

http://wiki.logos.com/Diagnostic_Logging

One other point — if your Logos crashes and you are are going to post the log files, do not restart Logos 5 until you have created (and posted) the logs ZIP file. When you restart Logos 5 some valuable information in the log files may be overwritten.

Ben

https://community.logos.com/discussion/comment/434725#Comment_434725

That log does show a crash but to get the complete picture it would be good to have all logs. The following Wiki links have information:

http://wiki.logos.com/Windows_Troubleshooting#Diagnostic_Logs

and

http://wiki.logos.com/Diagnostic_Logging

One other point — if your Logos crashes and you are are going to post the log files, do not restart Logos 5 until you have created (and posted) the logs ZIP file. When you restart Logos 5 some valuable information in the log files may be overwritten.

Thanks reply, I don't know its crash, when I open BSL tool,then it's crash, this program told me that have a problem, we will close it.

I found logos error log file.

Ben

https://community.logos.com/discussion/comment/434729#Comment_434729

Thanks above all.

now I have found awesomium.dll cause crash.

Dave Hooton

https://community.logos.com/discussion/comment/434736#Comment_434736

Thanks above all.

now I have found awesomium.dll cause crash.

Is the problem fixed?

Ben

https://community.logos.com/discussion/comment/435170#Comment_435170

Thanks Dave,

Problem Solved.

look this method:http://community.logos.com/forums/t/59937.aspx?PageIndex=2