https://bugs.winehq.org/show_bug.cgi?id=50227
--- Comment #14 from Frank franksauer@cox.net --- (In reply to Anastasius Focht from comment #13)
How does the 64-bit .NET indexer process behave on Windows in the same situation (assuming same Logos 9.x installation/dataset)? Some bugs aren't necessarily Wine bugs but application ones.
Thanks for all the info Anastasius!
The exact same install on Windows 10 has no issue indexing at all. Works perfectly and substantially faster.
The thing that stands out to me, is there is absolutely no file activity going on with Logos 9 on wine, during the indexer process. Typically, I can keep a file manager open to the applicable folders for the 3 primary indices that Logos creates and watch the indexer working. By working, I mean that the index folders would start with two file and there would be activity on these files as the indexer is indexing the resources. So, there would be growth from MBs up to GBs depending on this size of a library. Eventually, when the process is complete, there are 9 files in each of the Index Folders. At this time, the indexer is doing nothing beyond running - there is no file activity at all.