I was changing Bibles to determine the language and canon of each when the browser became unresponsive. When it finally became responsive again it crashed while changing the Bible from ESV to SBLGNT
3122.VerbumIndexer.zip
This may not be related to the crash, but your log shows that you have a lot of Visual Filter documents that are enabled by default. Deleting these documents (or editing the documents to only search within resources you're not typically opening) may greatly improve Verbum's overall performance.
The single worst VF is heading:*
But others you have include:
(or editing the documents to only search within resources you're not typically opening)
I have already done this as well as limiting the range against which they are applied. That fixed the start up time many months ago. Because I use Verbum primarily for the development of lessons, the Visual Filters are essential for creating illustrations. There are actually only 28 visual filters as I have given priority to multi-use filters where they can be clear. Features that have visual filters to teach how to use them include:
I would argue that these and many similar to them would best be provided by Faithlife as they are essential tools in learning to understand Faithlife coding.
But yes, when I get a bit of time, I will go through them again -- including building new ones -- to insure they have minimal impact on performance.
I was changing Bibles to determine the language and canon of each when the browser became unresponsive. When it finally became responsive again it crashed while changing the Bible from ESV to SBLGNT 3122.VerbumIndexer.zip
MJ,
The devs told me that the logs indicate your system ran out of memory.
and here I thought 16 GB physical memory and 18.2 GB virtual memory would be enough ...
It will probably depend on what else is running.
