Launching via session file (.lxj) or double clicking session file leads to crash

Sep 28, 2015 at 6:52 PM
Edited Sep 28, 2015 at 6:55 PM
Using the latest version, when trying to launch a session file (either with LogExpert not running or already launched) leads to a crash:

Invalid Content: ActiveContent must be one of the visible contents, or null if there is no visible content.

InvalidOperationException
at WeifenLuo.WinFormsUI.Docking.DockPane.set_ActiveContent(IDockContent value)
at WeifenLuo.WinFormsUI.Docking.DockContentHandler.Activate()
at WeifenLuo.WinFormsUI.Docking.DockContentHandler.SetParent(Control value)
at WeifenLuo.WinFormsUI.Docking.DockContentHandler.SetPane(DockPane pane)
at WeifenLuo.WinFormsUI.Docking.DockContentHandler.SetPaneAndVisible(DockPane pane)
at WeifenLuo.WinFormsUI.Docking.DockContentHandler.SetDockState(Boolean isHidden, DockState visibleState, DockPane oldPane)
at WeifenLuo.WinFormsUI.Docking.DockContentHandler.set_PanelPane(DockPane value)
at WeifenLuo.WinFormsUI.Docking.DockPane.InternalConstruct(IDockContent content, DockState dockState, Boolean flagBounds, Rectangle floatWindowBounds, DockPane prevPane, DockAlignment alignment, Double proportion, Boolean show)
at WeifenLuo.WinFormsUI.Docking.DockPane..ctor(IDockContent content, DockState visibleState, Boolean show)
at WeifenLuo.WinFormsUI.Docking.DockPanelExtender.DefaultDockPaneFactory.CreateDockPane(IDockContent content, DockState visibleState, Boolean show)
at WeifenLuo.WinFormsUI.Docking.DockPanel.Persistor.LoadFromXml(DockPanel dockPanel, Stream stream, DeserializeDockContent deserializeContent, Boolean closeStream)
at WeifenLuo.WinFormsUI.Docking.DockPanel.LoadFromXml(Stream stream, DeserializeDockContent deserializeContent, Boolean closeStream)
at LogExpert.LogTabWindow.RestoreLayout(String layoutXml)
at LogExpert.LogTabWindow.LoadProject(String projectFileName, Boolean restoreLayout)
at LogExpert.LogTabWindow.LogTabWindow_Load(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(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)


I can load the session just fine by using the File -> Load Session ... menu.

This problem does not exist with 1.5 / 4446.

Any ideas?
Developer
Sep 28, 2015 at 8:32 PM
first of all thanks for the message, but I struggled to reproduce this behavior, could you please give some infos e.g.
  • OS
  • How many open files
  • Any filter created tabs
  • Large files?
  • Some files missing?
  • Columnizer
  • Version (I assume you use 1.6.0?)
  • Wich version you created the session file?
Steps to reproduce (Assuming, please correct me if something missing/wrong)
  1. Open some files
  2. Save Session
  3. Close Logexpert
  4. Start logexpert with doubleclick on lxj
  5. Error
Greetings and have fun with grammar and spelling fails
Zarunbal
Sep 28, 2015 at 8:46 PM
Sure, here are the answers:
  1. Win 7 - 64-bit fully patched.
  2. No open files originally; one file to be opened by the session via UNC share.
  3. No filter created tabs.
  4. No large files (one file ~800k).
  5. No missing files.
  6. Columnizer is the RegEx Columnizer, built 8/27/2012 (maybe by me)?
  7. Version 1.5 / 5493
  8. Session file was saved using 1.5 / 4446 but resaved using 1.5 / 5493.
Reproduction 1
  1. Open a file via UNC path (\server\share\logfile.log).
  2. Change columnizer to use the regex columnizer with custom details (I can send this to you if needed.)
  3. Save session.
  4. Close LogExpert.
  5. Double click on lxj.
Error in first comment of this thread.

LogExpert stays running but the log file/session is not loaded; you are just left with a blank LogExpert window after the error dialog.
Sep 28, 2015 at 8:51 PM
Same thing happens with the 1.6 alpha.
Developer
Sep 28, 2015 at 9:38 PM
thanks for the infos, I will try to reproduce this behavior or if this doesn't work check the history of the changes. I hope to get started at the weekend. There waits a busy week for me ...

Greetings and have fun with grammar and spelling fails
Zarunbal
Developer
Oct 4, 2015 at 9:06 PM
After some hours of testing and swearing I have a scenario that leads in all my tests to the error ...

So my steps to reproduce this error are:
  1. Remove or rename following folders:
    • %appdata%/logexpert
    • c:\Users\<user>\Documents\LogExpert\
  2. Open a file
  3. Activate Regex Columnizer
  4. Save Session e.g. test01.lxj
  5. Close Logexpert
  6. Remove extra lxp file in c:\Users\<user>\Documents\LogExpert\ created for the session
  7. Open session file (Logexpert open with blank window)
  8. Open same file
  9. Save session e.g. test02.lxj
  10. There opens another "Logwindow" focus this one (could be the file wich failed to load on first attempt)
  11. Save session e.g. test02.lxj
  12. Close Logexpert
  13. Open Session file
  14. Error
Next step will be to trace down the bug and fix it ;) One of my candidates to check is this "ghost log window" that appears after saving the session.

Greetings and have fun with grammar and spelling fails
Zarunbal
Dec 17, 2015 at 5:17 PM
Any updates?

Thanks &
Cheers,

Toby
Developer
Feb 11, 2016 at 9:20 PM
not that good updates, this problem got me some serious headcaches. I found some more problems that need to be fixed first. Before I can start with this problem.

Greetings
Zarunbal
Feb 23, 2016 at 8:17 PM
Thanks for the update. I'm sticking with the older version for now.