Listary 6 Beta 🎉

Thanks for reporting the issue. I’ll check it.

Thanks for reporting the issue. I’ll check it.

Hi Channing,
Any updates regarding the crash with Acrobat?
This is really getting frustrating because I use acrobat a lot!

Please let me know
Thanks,
David

I’ll try to ship a fix in the next release.

Well that is a bummer, I was eagerly waiting for Listary 6 and I needed the portable version.

I think it’s still important to keep the keywords mechanism. There are situations where you want to set a completely different keyword than the actual letters in the target’s name. I love the new implementation, with automatic fuzzyness that kicks in when you’ve selected a target a few times – but I don’t see why keywords had to go … one doesn’t need to exclude the other, or?

@Channing, any updates yet?
I am having to restart listary 5-10 times daily

Also, today Listary crashed twice with outlook. I was saving a file attachment to my computer and it crashed.

Note, all these crashes happen in the end, after I press OK on the dialog.
Until then, Listary worked fine.

1 Like

is there any idea for when this actually releases, as well as the documentation for addons, and/or the appearance change? I really liked the dark theme in 5, but I want to use the new stuff of the 6 beta.

is it possible to add feature to remember last launch/search?

You can press the up key.

great!! thanks… oh yea, btw is it possible to run powershell/cmd command from listary in the current build?

My entire system froze suddenly 10 minutes ago. When I force-rebooted the system, Listary has since refused to start with this error:

Application: Listary.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.InvalidOperationException
   at .()
   at .()
   at Listary.Core.ListaryApp.Start(System.String ByRef)
   at Listary.Main.App.OnStartup(System.Windows.StartupEventArgs)
   at System.Windows.Application.<.ctor>b__1_0(System.Object)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
   at System.Windows.Threading.DispatcherOperation.InvokeImpl()
   at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(System.Object)
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   at MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object)
   at System.Windows.Threading.DispatcherOperation.Invoke()
   at System.Windows.Threading.Dispatcher.ProcessQueue()
   at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
   at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
   at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
   at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
   at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
   at System.Windows.Application.RunDispatcher(System.Object)
   at System.Windows.Application.RunInternal(System.Windows.Window)
   at Listary.Main.App.Main()

I tried launching Listary manually, but the same error appeared. Event Viewer shows Listary triggering a second error at C:\WINDOWS\System32\KERNELBASE.dll , too:

Faulting application name: Listary.exe, version: 6.0.5.16, time stamp: 0x5cd6d83d
Faulting module name: KERNELBASE.dll, version: 10.0.18362.476, time stamp: 0x83c3d83a
Exception code: 0xe0434352
Fault offset: 0x000000000003a839
Faulting process id: 0x4384
Faulting application start time: 0x01d5a49a7beadd49
Faulting application path: C:\Program Files\Listary\Listary.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: c65b2825-8b0b-429c-9664-9eea84d3e4e4
Faulting package full name: 
Faulting package-relative application ID: 

Then, within moments after restarting, Bitdefender threw this virus protection message:

2019-11-26_15-47-58

I’m ready to uninstall & reinstall Listary 6, but 1) are there any more logs you’d need that could get deleted? and, 2) any reason why this happened and/or do we need to set an exception for Listary now in anti-virus programs?

Environment
Windows 10 Pro x64 1909 (18363.476)
Listary 6.0.5.16
Default Windows Explorer: no mods, no tweaks, etc.

Same here. Error started with latest win10 major update to 1909

1 Like

Yup, @Manuel. What anti-virus are you using? Defender or something else?

Just now, this bug hit another 1909 system (though no notification from Bitdefender). Not sure if it is caused by the 1909 update, though, as I updated a week ago and Listary 6 beta worked great.

@Channing Any workarounds for this crash? Haven’t been able to launch Listary 6 beta on either of my machines.

EDIT: hahah, in the middle of writing this post, Bitdefender sent the notification:

A real weird bug, to suddenly pop out of the blue. Listary, Windows, etc. worked fine for a week, even after updates. Maybe this was a Bitdefender update, then, which updated today on this system (will check version on 1st system soon):

Bitdefender Free 1.0.15.142 (Antimalware Engine 7.83010)
Listary 6.0.5.16
Windows 10 Pro x64 1909 (18363.476)
Default Windows Explorer: no mods, no tweaks, etc.

In fact the managed av internaly uses the bitdefender engine too.

1 Like

I had to whitelist listary as it got quarantined constantly by bitdefender. But now everything is working fine.

1 Like

OK, glad to hear that workaround worked.

Today, with the latest Bitdefender update, one 1909 system started launching Listary normally and ListaryHookHost32.exe is no longer flagged in the Bitdefender Quarantine. Will check the 1909 laptop tomorrow.

Working system, updated:

Bitdefender Free 1.0.16.144 (Antimalware Engine 7.83054)
Bitdefender Free 1.0.15.142 (Antimalware Engine 7.83010)
Listary 6.0.5.16
Windows 10 Pro x64 1909 (18363.476)
Default Windows Explorer: no mods, no tweaks, etc.

any ETA for the final version.

1 Like

App is crashing when adding a new filter in File Search:

It works if I run Listary Beta as administrator.