BRADLEY? What is up with Verbum memory use

Most of the time my memory use ranges between 35-45% ... but with surprising frequency Verbum goes nuts eating up memory and finally crashing.

To reproduce (one pattern I've identified):

open esv with link set a and propositional outline filter
open high definition esv with link set a
open esv-ce with link set a and discoourse filter
set to Romans 1:16
focus on propositional outline tile; take screen shot
focus on high definition tile; take screen shot
focus on discourse tile ... well try, it becomes unresponsive
watch memory use grow and grow
crash

Note files were cleared before Verbum was reopened so the logs are reasonably pure to this scenario.

5383.VerbumError.zip

Find more posts tagged with

Comments

Bradley Grainger (Logos)

This is the final line in your log before the crash:

(11m 36.2s) Populating filter cache for heading:*

Maybe it's not using up all the memory, but it is spending an enormous amount of CPU time and slowing down the program. Wildcard searches, particularly for "*", are not optimised. I strongly recommend deleting that visual filter document.

(Other than that, it's very hard to diagnose RAM usage from a log file, so I don't have any other suggestions

Rosie Perera

5383.VerbumError.zip

Very bizarre/amusing that my computer seems to think that .zip file was a Microsoft Solitaire theme. ??? I didn't install MS Solitaire Collection (it probably came with my computer).

Not your or Logos's fault. Just sharing it here for the humor value. Will bring it up with Microsoft.

MJ. Smith

https://community.logos.com/discussion/comment/1147048#Comment_1147048

I strongly recommend deleting that visual filter document.

The only filters intentionally on are Logos application filters - in making sure that no filters were on unintentionally, I noticed that the Factbook filter in the ESVCE led to the program becoming unresponsive and eventually to a crash.

.8473.VerbumError-2.zip

Wildcard searches, particularly for "*", are not optimised

AFAIK I have not been foolish enough to have such a filter - it certainly is not intentionally turned on. a couple of years ago I was a victim of a beta bug that turned filters on but ESVCE is a new resource on which I have not manually turned anything except the Discourse filter.

MJ. Smith

https://community.logos.com/discussion/comment/1147051#Comment_1147051

Just sharing it here for the humor value. Will bring it up with Microsoft.

That's what I get for using an ASUS ROG --- clearly biased towards gaming. [:D]

Rosie Perera

https://community.logos.com/discussion/comment/1147066#Comment_1147066

Just sharing it here for the humor value. Will bring it up with Microsoft.

That's what I get for using an ASUS ROG --- clearly biased towards gaming.

Got the answer already (psst, I didn't really bring it up with Microsoft, but with some Microsoft alumni friends of mine).

Here's the explanation of what was wrong:

"Websites and web browsers use MIME types to determine the file type, not the extension. In this case, the web server is returning the correct MIME type, application/x-compressed. In the registry, on my Windows 10 machine, this MIME type has the extension .solitairetheme8 mapped to it (see HKEY_CLASSES_ROOT\MIME\Database\Content Type\application/x-compressed). Firefox looks up the MIME type in the registry, sees the solitaire extension, and thinks it's a solitaire theme pack. I don't know what wrote this registry key, but I'm guessing it's the solitaire installer. The file downloads correctly as zip in Chrome (mac/pc) and Safari. It seems Firefox is doing the 'correct' thing but it's broken for most windows users.

BTW, to fix this, you'll have to edit the registry. Go to HKEY_CLASSES_ROOT\MIME\Database\Content Type\application/x-compressed key and change the 'Extension' value to '.zip'. Then Firefox will correctly ask you if you want to open the file with Explorer [actually for me it's WinZip] instead of Solitaire. And hopefully this doesn't break Solitaire 😃"

I looked where he said, and sure enough, my registry had .solitairetheme8 in there. Editing that fixed it.

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/1147064#Comment_1147064

AFAIK I have not been foolish enough to have such a filter

The log shows that the program is executing it, therefore it must exist on your system.

Find that Visual Filter document and delete it (don't just uncheck it in the Visual Filters menu).

Then see if the RAM issue is resolved.

MJ. Smith

https://community.logos.com/discussion/comment/1147109#Comment_1147109

The problem first appeared when testing the Factbook filter in beta. It did not occur concurrently with any changes in user filters. I will simply turn the Factbook filter off everywhere and see if the problem disappears.

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/1147154#Comment_1147154

OK, but if you ever want to stop your CPU fans for spinning up for twelve minutes whenever you open a resource, feel free to follow my suggestion, too. [:)]

MJ. Smith

https://community.logos.com/discussion/comment/1147159#Comment_1147159

If it happens, I certainly will.

Dave Hooton

https://community.logos.com/discussion/comment/1147064#Comment_1147064

in making sure that no filters were on unintentionally, I noticed that the Factbook filter in the ESVCE led to the program becoming unresponsive and eventually to a crash.

That crash was the same as the previous one - from a user VF for heading:* that is on ESV, not ESVCE. I couldn't get that type of message by turning on the Factbook filter in ESV.

MJ. Smith

https://community.logos.com/discussion/comment/1147510#Comment_1147510

Thanks Dave