The CBV tool panel will not REMAIN open after updating to B5. I can open CBV, but after a few moments the panel closes for no reason. Anyone else experiencing this?
Experienced crash with Copy Bible Verses panel open
8228.B5-Crash-CBV.zip
Crash Report included - console messages has some stack traces.
Keep Smiling [:)]
Mine worked flawlessly. I was able to use the "Copy" button and then paste manually into TextEdit, then tried the "Copy & Paste" button to copy the passage into Word, and it opened Word and pasted.
KSFJ
Looks like the app ran out of memory trying to malloc. Since we're 32-bits, this happens at around 2.37 GB of Active Memory used. Any idea how you got the app into that scenario?
KSFJ Crash Report included - console messages has some stack traces. Looks like the app ran out of memory trying to malloc. Since we're 32-bits, this happens at around 2.37 GB of Active Memory used. Any idea how you got the app into that scenario?
Resource competition among 14 applications - with 16 GB Ram installed, using 64 bit kernel with 5 applications running 32 bit:
In Camino, Google Chrome and FIrefox had several tabs open - more memory used.
Posted crash after choosing Logos 4 layout with many panels and 3 Bible Word Studies - before studies done, closed 2 of them, then opened Copy Bible Verses - looked at several CBV formats and couple bibles - crash (memory competition). At time, remember Activity Monitor showing active memory around 2.37 MB.
Note: closing all applications does not release all active memory - restarting Mac does.
Thanks - learned need to watch Active Memory.
I am correct in guessing the the reason why it is 32 bit and not 64 is because of the sharing of most code between the mac and pc versions?
Also, long term, is there any goal in eventually becoming 64 bit to remove this potential issue of running the software too hard and causing it to hang up?
I would think, especially with people with large 27" imacs, that it may be easy to have enough windows open to run the system too hard and fill that memory cap. Is that a logical concern for people with larger screens, that would naturally have 4 times as many windows open as someone with a 13" laptop?
More ore less.
This wouldn't actually resolve the problem. The real issue at stake here is that we have some memory leaks that we need to track down and eliminate. Switching to 64-bit would only increase the amount of time required to leak all of your memory (making your machine much more painful to use in the meantime).
As for a correlation between monitor size and program usage, most of the memory comes from the number of tabs open, as opposed to tabs displayed—and I've seen some very full tab bars in screenshots. In any case, both Tom and I have 30" monitors, and everyone else on the Mac team has at least two 20" monitors, so we push the app (on that axis) as hard as anyone else.
I still cannot use CBV, the panel goes away after sometime. Any solution? Same behavior in Beta 6.
If you post logs (instructions, along with a video, are pinned to the top of this forum), we'll have a much higher likelihood of finding and fixing the bug that's affecting you.
