Device: Surface 3Logos Bible Software 7.1 SR-2 (7.1.0.0040)OS: Windows 10 Home 64-bit (1607). CPU: Intel(R) Atom(TM) x7-Z8700 CPU @ 1.60GHzRAM: 4.00 GBDisplay 1: Surface Display 10.8” display (1920 x 1280); Aspect ratio: 3:2Display 2: Dell E2715H 27" IPS LED Monitor (1920 x 1080)Display Adapter: Intel(R) HD Graphics
Description: Logos has display, performance, and stability problems particularly when the program window(s) are maximized. The software runs much better when I stretch windows manually to more-or-less fill the screen but stop short of maximizing them (e.g., by clicking that little, iconic square in the upper-right corner of the window, by using the "WIN + Up-Arrow" shortcut, or by dragging the window to the top-center of the screen). These issues may be related in part to how Logos handles the size and resolution of certain displays/monitors. I recall earlier this year that Microsoft's OneNote Extension for Google Chrome had somewhat similar problems, which they were eventually able to resolve shortly after making that connection.
Here are some of the specific problems I'm experiencing (particularly with the window maximized):
1. When right-clicking on a word or other unit, the context menu will stutter while trying to populate—often appearing with a black outline/trimming around its border—and will often subsequently disappear altogether (see image 1 of 2 below). 2. Similar glitches can be seen when left clicking on a word while using the information tool and/or when hovering over a word while viewing the reverse interlinear popup display (at the bottom of the panel) (see image 2 of 2 below). 3. This also seems related to problems with panels and tabs resizing (e.g., as reported in this thread: BUG: Panel sizing affects tab label formatting causing high CPU usage and delay). 4. Media resources often cause Logos to become unresponsive and sometimes crash (e.g., 1000 Bible Images, BiblePlaces.com Image Library, Encyclopedia Britannica: Noet Edition (Media), etc.). Minimizing the window can help prevent it from crashing. 5. These problems also seem to impact other aspects of the program, such as searches in general and media searches in particular. 6. When a Logos window is maximized on my left display (Dell E2715H), a portion of the window (just a tiny, minute sliver) can be seen on the leftmost edge of my right display (Surface 3). This itself is no bother and may be more of a calibration issue. I only mention it in case it happens to have any relevance whatsoever.
I don't have time to provide logs at the moment; however, here are couple screenshots that I captured for starters:
I have a couple log files.
Log file 1: Logos 7 Context Menu Delay and Collapse
Layout: With the first log file, I started with a blank layout and then opened several tools and resources. On my left, Dell monitor, I had a maximized window with the information panel on the left and the LHB on the right, along with the ESV displayed via the "multiple resources". I also had Discourse Features (Hebrew) enabled. On my right, Surface 3 monitor, I had my main Logos window maximized, as I recall, with a small note file called "Temp: Genesis Notes", which contains just six notes (e.g., "Test note"; "Test note 2"; etc.). I may have also had a lexicon open (e.g., DBL Hebrew). I performed a few basic actions with the same basic setup.
As an aside, this and related problems occur with all sorts of setups—including various tools, visual filters, options toggled on or off (e.g., "multiple resources"), and resources of various sizes, kinds, and quantities. Sometimes it happens when I'm trying to add a note to a document.
Problem: When I right-clicked on a word in LHB (or it could have been a short phrase or verse), the context menu delayed, failed to finish populating, and collapsed. In general, such stalling can affect every window, panel, and menu in Logos. It is also often accompanied by various degrees of scrolling lag.
2110.Logos 7 Context Menu Delay and Collapse.log
Log file 2: Logos 7 Stalls Opening Media Resources
Layout: With the second log file, I again started with a blank layout. On my right, Surface 3 display, I had the main Logos window maximized. On my left, Dell display, I had my library window maximized.
Problem: I searched for "media" in my library window and took turns individually opening and closing 1000 Bible Images, Bibleplaces.com Image Library, and Compton's Encyclopedia (Media). These are a few of the media resources with which I've encountered problems. It can also occur, for example, in searches. Anyway, after opening them, Logos's CPU usage jumped as high as 80–90+% for a while and then often leveled out to 30–40+%. Logos's memory usage jumped to 700–900+ MB.
After the final instance of opening 1000 Bible Images in the right panel on my right display, I hit CTRL+F11 to open it in its own window. Logos 7 then tried to open a maximized window on my left, Dell display. It stalled for probably at least 10 minutes or longer. (I didn't know Logos had such ridiculously, awesome hangtime! ) It had stalled probably at least by 6:04PM (CST)—since I didn't catch the exact start-time—and continued until 6:14PM. A while after I finally tried to close the window (by clicking on the "X" in the upper-right corner of the window), Logos stopped stalling, and the window didn't actually close. There was also no crash this time, although I have encountered them in the past when Logos is left to stall. Minimizing or restoring the window can help preempt it.
Note: The logs look awfully busy. I wonder if there are background processes slowing things down. In the first log, there may be some expensive visual filters running at the start that I shut off. I typically have most or all notes and custom visual filters turned off.
5734.Logos 7 Stalls Opening Media Resources.log
I hope this information helps!
It would be helpful to know if any of these issues occur with the second (Dell) monitor disconnected.
Dave===
Windows 10 & Android 8
Dave Hooton: It would be helpful to know if any of these issues occur with the second (Dell) monitor disconnected.
Thanks, Dave, I had originally meant to address that. Indeed, these issues do occur with the external, Dell monitor disconnected. I just recreated the same problem opening 1000 Bible Images on just my Surface 3 display. First it stalled opening into a right panel. Then after right-clicking and selecting "open tab in a new window" it stalled for a few minutes or so, opening into a non-maximized window. See the logs and two additional screenshots below.
The other problems, such as those with the context menu, I also recall occurring without maximized windows—although I find it generally runs a lot better if I do not maximize them.
4857.Logos 7 Stalls Opening Media Resources on Surface Display.log
I'm going to delete and clean up a bunch of user generated collections to see if that helps speed things up somewhat, although I think the display issues go well beyond mere startup speed. They occur at any time.
Adam Olean: Display Adapter: Intel(R) HD Graphics
Display Adapter: Intel(R) HD Graphics
In some measure I have seen problems similar to yours when using systems with weak graphics adapters - or adapters with insufficient memory. Whatever your baked in intel graphics chipset is, with only 4GB in the machine, I'd wager that not much of your memory is allocated to graphics alone.
I have no idea why it should be different when stretched -vs- maximized unless the maximizing requests screen draws differently.
At any rate - would it be possible to go into the computer's BIOS at boot and allocate more ram to the graphics?
Sarcasm is my love language. Obviously I love you.
Adam Olean:Thanks, Dave, I had originally meant to address that. Indeed, these issues do occur with the external, Dell monitor disconnected. I just recreated the same problem opening 1000 Bible Images on just my Surface 3 display. First it stalled opening into a right panel. Then after right-clicking and selecting "open tab in a new window" it stalled for a few minutes or so, opening into a non-maximized window.
This is particularly sluggish on my laptop i7 5500U with integrated graphics. It is somewhat more responsive using the higher performance graphics card with 2 GB VRAM. So i can imagine how slow/unresponsive it would be with an Atom processor and integrated graphics.
TCBlack: Adam Olean: Display Adapter: Intel(R) HD Graphics In some measure I have seen problems similar to yours when using systems with weak graphics adapters - or adapters with insufficient memory. Whatever your baked in intel graphics chipset is, with only 4GB in the machine, I'd wager that not much of your memory is allocated to graphics alone. I have no idea why it should be different when stretched -vs- maximized unless the maximizing requests screen draws differently. At any rate - would it be possible to go into the computer's BIOS at boot and allocate more ram to the graphics?
Thanks, TCBlack. I'll keep that in mind. I've started first with purging costly, user-generated collections and several layouts. That should help performance all-around and then to see what underlying issues remain.
I was wondering the same about maximizing the screen. That's why a similar bug for Microsoft's OneNote extension came to mind, although, of course, their underlying causes could be almost entirely unrelated.
Dave Hooton: Adam Olean:Thanks, Dave, I had originally meant to address that. Indeed, these issues do occur with the external, Dell monitor disconnected. I just recreated the same problem opening 1000 Bible Images on just my Surface 3 display. First it stalled opening into a right panel. Then after right-clicking and selecting "open tab in a new window" it stalled for a few minutes or so, opening into a non-maximized window. This is particularly sluggish on my laptop i7 5500U with integrated graphics. It is somewhat more responsive using the higher performance graphics card with 2 GB VRAM. So i can imagine how slow/unresponsive it would be with an Atom processor and integrated graphics.
The Atom X7's specs are a little misleading in that it actually runs up to 2.40GHz, only throttling down if it runs hot for too long. It's certainly no i7, and would be particularly poor for performing much rendering and other extended, data-heavy tasks. I generally find its relatively slow storage to be its primary choke-point for my mostly modest purposes (although it's noticeably faster than my old HDD, which isn't saying too much!).
If its sluggish with you setup, then hopefully Faithlife will continue to optimize Logos performance—assuming there aren't other underlying glitches/bugs at work. The Logos Web App is worth watching too.
Adam Olean: Dave Hooton: It would be helpful to know if any of these issues occur with the second (Dell) monitor disconnected. Thanks, Dave, I had originally meant to address that. Indeed, these issues do occur with the external, Dell monitor disconnected. I just recreated the same problem opening 1000 Bible Images on just my Surface 3 display. First it stalled opening into a right panel. Then after right-clicking and selecting "open tab in a new window" it stalled for a few minutes or so, opening into a non-maximized window. See the logs and two additional screenshots below.
Device: Surface 3Logos Bible Software 7.7 SR-1 (7.7.0.0018)OS: Windows 10 (1703)CPU: Intel(R) Atom(TM) x7-Z8700 CPU @ 1.60GHzRAM: 4.00 GBDisplay 1: Surface Display 10.8” display (1920 x 1280); Aspect ratio: 3:2Display 2: Dell E2715H 27" IPS LED Monitor (1920 x 1080)Display Adapter: Intel(R) HD Graphics
The problems described in this thread haven't been resolved, so I found some time to produce new log files. I had previously optimized Logos 7 earlier this year by breaking up large, complex note files that link to more than one resource; deleting many documents (e.g., collections, visual filters, etc.); and redirecting other visual filters to resources that I do not use often. The log files should be a lot cleaner now. I also ran Logos Windows Profiler if that information is necessary. (I previously had some Event Logs but haven't had time to upload them, so I'll start fresh here.)
Here's a log file in which I opened Logos, typed "1000" into the command box, and hit enter to open the resource "1,000 Bible Images". It stalled for under a minute, as I recall, after which I right-clicked its tab and selected "open tab in a new windows" just as described above. It stalled for a few minutes opening into a maximized window on my Surface display but did not crash. Sometimes in the past it would stall more than ten minutes, so this is an improvement at least.
Here are the logs followed by a screenshot:
1856.Logos Stalls Opening Media Resource 1000 Bible Images 2.log
This section should be of particular interest with a number of WPF warnings and errors, which can be compared with older logs:
2017-07-21 13:09:54.2740 7 Info LibraryCatalogIndex Searching for all records matching: 10002017-07-21 13:09:55.0025 28 Info ProfilingAppCommand Waited 10 seconds for profiler to attach; self-attach state is Inactive.2017-07-21 13:09:55.9813 28 Info ProfilingAppCommand Waited 11 seconds for profiler to attach; self-attach state is Inactive.2017-07-21 13:09:56.7126 1 Info AppCommand (Timed) Executing command: Resource|Id=LLS:1000BBLIMG|Placement=a2017-07-21 13:09:56.7512 1 Info PanelViewModel Applying panel settings for Preferences: Locator=false|TextSize=14.6666666666666662017-07-21 13:09:56.7692 1 Info PanelViewModel Navigating panel to: Id=LLS:1000BBLIMG2017-07-21 13:09:56.7762 1 Info PanelViewModel Applying panel settings for Bookmark: Id=LLS:1000BBLIMG2017-07-21 13:09:56.8380 1 Info ResourcePanelViewModel Updating 1 ResourceViewModels for host: LLS:1000BBLIMG with configuration: LLS:1000BBLIMG2017-07-21 13:09:56.9685 7 Info ProfilingAppCommand Waited 12 seconds for profiler to attach; self-attach state is Inactive.2017-07-21 13:09:57.2308 1 Info PanelViewModel Applying panel settings for Preferences: Contents=true|Locator=false|MultiViewEnabled=true|MultiViewLayoutIsVertical=false|Position=Article%3dIMAGE.527%7cArticleLength%3d2%7cContext%3d%2520%250a%7cOffset%3d0%7cOffsetInContext%3d0%7cResource%3dLLS:1000BBLIMG%7cVersion%3d2016-04-22T20:41:45Z2017-07-21 13:09:57.9513 28 Info ProfilingAppCommand Waited 13 seconds for profiler to attach; self-attach state is Inactive.2017-07-21 13:09:59.0457 6 Info ProfilingAppCommand Waited 14 seconds for profiler to attach; self-attach state is Inactive.2017-07-21 13:09:59.1858 1 Info MediaResourceDisplay Navigating from article 0 to 526 (Display Article: Article=IMAGE.527|Resource=LLS:1000BBLIMG|Version=2016-04-22T20:41:45Z)2017-07-21 13:09:59.7603 1 Info PanelViewModel Got panel settings for History: Id=LLS:1000BBLIMG|Position=Article%3dIMAGE.527%7cArticleLength%3d2%7cContext%3d%2520%250a%7cOffset%3d0%7cOffsetInContext%3d0%7cResource%3dLLS:1000BBLIMG%7cVersion%3d2016-04-22T20:41:45Z2017-07-21 13:10:00.0550 34 Info ProfilingAppCommand Waited 15 seconds for profiler to attach; self-attach state is Inactive.2017-07-21 13:10:00.4811 1 Warn WpfDataBinding System.Windows.Data Warning: 40 : BindingExpression path error: 'OpenLogosMediaItem' property not found on 'object' ''MediaResourceDisplay' (HashCode=7711478)'. BindingExpression:Path=Model.OpenLogosMediaItem; DataItem='MediaResourceControl' (Name='OurMediaResoureControl'); target element is 'Grid' (Name='PART_LayoutRoot'); target property is 'MergedCommandBindings' (type 'Object')2017-07-21 13:10:00.9699 7 Info ProfilingAppCommand Waited 16 seconds for profiler to attach; self-attach state is Inactive.2017-07-21 13:10:01.7466 8 Info UpdateStageBase Stopping work thread for DiscoveryUpdateStage queue.2017-07-21 13:10:01.9505 7 Info ProfilingAppCommand Waited 17 seconds for profiler to attach; self-attach state is Inactive.2017-07-21 13:10:03.0489 34 Info ProfilingAppCommand Waited 18 seconds for profiler to attach; self-attach state is Inactive.2017-07-21 13:10:04.0288 33 Info ProfilingAppCommand Waited 19 seconds for profiler to attach; self-attach state is Inactive.2017-07-21 13:10:04.7059 31 Info ProfilingAppCommand Profiler attached successfully.2017-07-21 13:10:04.7139 31 Info ProfilingAppCommand Starting profiler2017-07-21 13:10:04.7309 31 Info ProfilingAppCommand Started profiler.2017-07-21 13:10:09.9477 1 Info AppCommand (13.23s) Executing command: Resource|Id=LLS:1000BBLIMG|Placement=a2017-07-21 13:10:19.9552 20 Info SyncManager Requesting sync on all sync clients2017-07-21 13:10:20.5796 20 Info SyncClient Found 1 items to submit for HistorySyncItem2017-07-21 13:10:20.5886 20 Info SyncClient (Timed) Submitting 1 of 1 items.2017-07-21 13:10:20.8628 20 Info SyncClient (267ms) Submitting 1 of 1 items.2017-07-21 13:10:20.8787 20 Info SyncClient Integrated 1 successes, 0 conflicts, and 0 errors.2017-07-21 13:10:20.8897 20 Info SyncClient Downloading items for HistorySyncItem2017-07-21 13:10:21.0688 20 Info SyncClient New last known milestones: {"itemMilestone":"102462"}2017-07-21 13:10:21.2629 20 Info SyncManager Finished requesting sync on all sync clients.2017-07-21 13:10:32.0022 20 Info SyncManager Requesting sync on all sync clients2017-07-21 13:10:34.0913 20 Info SyncClient Downloading items for HistorySyncItem2017-07-21 13:10:35.2480 20 Info SQLite Profile 599ms in history.db for: COMMIT2017-07-21 13:10:35.4112 20 Info SyncClient Unchanged last known milestones: {"itemMilestone":"102462"}2017-07-21 13:10:35.5705 1 Info OurTiledFrame OurTiledFrame got the keyboard focus, so setting focus to the active panel.2017-07-21 13:10:35.8129 20 Info SQLite Profile 363ms in history.db for: insert or replace into SyncInfo (Key, Value) values (@Key, @Value)2017-07-21 13:10:36.4665 20 Info SyncManager Finished requesting sync on all sync clients.2017-07-21 13:10:44.9218 1 Info FloatingWindow Floating window activated: LDLS4.FloatingWindow2017-07-21 13:10:46.6427 1 Warn WpfResourceDictionary System.Windows.ResourceDictionary Warning: 9 : Resource not found; ResourceKey='DescriptionAreaForegroundBrush'2017-07-21 13:10:46.6617 1 Warn WpfResourceDictionary System.Windows.ResourceDictionary Warning: 9 : Resource not found; ResourceKey='DescriptionAreaForegroundBrush'2017-07-21 13:10:46.6777 1 Warn WpfResourceDictionary System.Windows.ResourceDictionary Warning: 9 : Resource not found; ResourceKey='DescriptionAreaForegroundBrush'2017-07-21 13:10:49.0636 1 Warn WpfResourceDictionary System.Windows.ResourceDictionary Warning: 9 : Resource not found; ResourceKey='DescriptionAreaForegroundBrush'2017-07-21 13:10:49.0836 1 Warn WpfResourceDictionary System.Windows.ResourceDictionary Warning: 9 : Resource not found; ResourceKey='DescriptionAreaForegroundBrush'2017-07-21 13:10:49.1016 1 Warn WpfResourceDictionary System.Windows.ResourceDictionary Warning: 9 : Resource not found; ResourceKey='DescriptionAreaForegroundBrush'2017-07-21 13:10:51.4680 35 Info LibraryCatalogIndex Rebuilding library catalog index.2017-07-21 13:13:43.4483 35 Info LibraryCatalogIndex (Timed) Attempting to replace index 'C:\Users\Agolean\AppData\Local\Logos\Data\rsg5t2sg.3bw\LibraryCatalog/catalog' with new index 'C:\Users\Agolean\AppData\Local\Logos\Data\rsg5t2sg.3bw\LibraryCatalog/r5gpbmse.nnd'.2017-07-21 13:13:45.0700 35 Info FileSystemIndexInfo Replacing C:\Users\Agolean\AppData\Local\Logos\Data\rsg5t2sg.3bw\LibraryCatalog/catalog with C:\Users\Agolean\AppData\Local\Logos\Data\rsg5t2sg.3bw\LibraryCatalog/r5gpbmse.nnd2017-07-21 13:13:45.8752 35 Info LibraryCatalogIndex (825ms) Attempting to replace index 'C:\Users\Agolean\AppData\Local\Logos\Data\rsg5t2sg.3bw\LibraryCatalog/catalog' with new index 'C:\Users\Agolean\AppData\Local\Logos\Data\rsg5t2sg.3bw\LibraryCatalog/r5gpbmse.nnd'.2017-07-21 13:13:45.9462 35 Info LibraryCatalogIndex Library catalog indexing completed; firing event.2017-07-21 13:10:51.9147 1 Warn WpfResourceDictionary System.Windows.ResourceDictionary Warning: 9 : Resource not found; ResourceKey='DescriptionAreaForegroundBrush'2017-07-21 13:13:48.9673 1 Warn WpfResourceDictionary System.Windows.ResourceDictionary Warning: 9 : Resource not found; ResourceKey='DescriptionAreaForegroundBrush'2017-07-21 13:13:48.9963 1 Warn WpfResourceDictionary System.Windows.ResourceDictionary Warning: 9 : Resource not found; ResourceKey='DescriptionAreaForegroundBrush'2017-07-21 13:13:50.6353 11 Info LibraryCatalogIndex Searching for all records matching: series:"Notes on Linguistics"2017-07-21 13:13:51.9540 1 Info MainWindow MainWindow activated.2017-07-21 13:13:52.1018 1 Info FloatingWindow Floating window activated: LDLS4.FloatingWindow2017-07-21 13:14:03.5712 1 Info FloatingWindow Floating window activated: LDLS4.FloatingWindow2017-07-21 13:14:04.6716 1 Warn WpfResourceDictionary System.Windows.ResourceDictionary Warning: 9 : Resource not found; ResourceKey='DescriptionAreaForegroundBrush'2017-07-21 13:14:04.6913 1 Warn WpfResourceDictionary System.Windows.ResourceDictionary Warning: 9 : Resource not found; ResourceKey='DescriptionAreaForegroundBrush'2017-07-21 13:14:04.7507 1 Warn WpfResourceDictionary System.Windows.ResourceDictionary Warning: 9 : Resource not found; ResourceKey='DescriptionAreaForegroundBrush'2017-07-21 13:14:05.6988 1 Warn WpfResourceDictionary System.Windows.ResourceDictionary Warning: 9 : Resource not found; ResourceKey='DescriptionAreaForegroundBrush'2017-07-21 13:14:05.7198 1 Warn WpfResourceDictionary System.Windows.ResourceDictionary Warning: 9 : Resource not found; ResourceKey='DescriptionAreaForegroundBrush'2017-07-21 13:14:05.7418 1 Warn WpfResourceDictionary System.Windows.ResourceDictionary Warning: 9 : Resource not found; ResourceKey='DescriptionAreaForegroundBrush'2017-07-21 13:14:05.9167 1 Info PanelViewModel Got panel settings for History: Id=LLS:1000BBLIMG|Position=Article%3dIMAGE.527%7cArticleLength%3d2%7cContext%3d%2520%250a%7cOffset%3d0%7cOffsetInContext%3d0%7cResource%3dLLS:1000BBLIMG%7cVersion%3d2016-04-22T20:41:45Z2017-07-21 13:14:05.9400 1 Info PanelViewModel Got panel settings for Preferences: Contents=true|Locator=false|MultiViewEnabled=true|MultiViewLayoutIsVertical=false2017-07-21 13:14:06.1564 13 Info ResourceCollectionManager (Timed) Updating collection cache.2017-07-21 13:14:06.9205 1 Warn WpfResourceDictionary System.Windows.ResourceDictionary Warning: 9 : Resource not found; ResourceKey='DescriptionAreaForegroundBrush'2017-07-21 13:14:06.9376 1 Warn WpfResourceDictionary System.Windows.ResourceDictionary Warning: 9 : Resource not found; ResourceKey='DescriptionAreaForegroundBrush'2017-07-21 13:14:06.9636 1 Warn WpfResourceDictionary System.Windows.ResourceDictionary Warning: 9 : Resource not found; ResourceKey='DescriptionAreaForegroundBrush'2017-07-21 13:14:07.0718 13 Info ResourceCollectionManager (909ms) Updating collection cache.2017-07-21 13:14:07.8104 1 Warn WpfResourceDictionary System.Windows.ResourceDictionary Warning: 9 : Resource not found; ResourceKey='DescriptionAreaForegroundBrush'2017-07-21 13:14:07.8269 1 Warn WpfResourceDictionary System.Windows.ResourceDictionary Warning: 9 : Resource not found; ResourceKey='DescriptionAreaForegroundBrush'2017-07-21 13:14:07.8509 1 Warn WpfResourceDictionary System.Windows.ResourceDictionary Warning: 9 : Resource not found; ResourceKey='DescriptionAreaForegroundBrush'2017-07-21 13:14:07.8959 1 Info ResourceViewTracker Saving at client request.2017-07-21 13:14:08.1171 1 Info MainWindow MainWindow activated.2017-07-21 13:14:13.6825 1 Info MainWindow MainWindow activated.2017-07-21 13:14:14.3450 11 Info LibraryCatalogIndex Searching for all records matching: 10002017-07-21 13:14:17.5136 11 Info LibraryCatalogIndex Searching for all records matching: Stop2017-07-21 13:14:18.0585 20 Info SyncManager Requesting sync on all sync clients2017-07-21 13:14:18.4242 20 Info SQLite Profile 309ms in PreferencesManager.db for: select SyncId from Preferences where SyncState = @SyncState2017-07-21 13:14:18.6770 20 Info SyncClient Found 1 items to submit for PreferencesSyncItem2017-07-21 13:14:19.1176 20 Info SyncClient (Timed) Submitting 1 of 1 items.2017-07-21 13:14:19.2728 20 Info SyncClient (145ms) Submitting 1 of 1 items.2017-07-21 13:14:19.2998 20 Info SyncClient Integrated 1 successes, 0 conflicts, and 0 errors.2017-07-21 13:14:19.3928 20 Info SyncClient Downloading items for PreferencesSyncItem2017-07-21 13:14:19.5384 20 Info SyncClient New last known milestones: {"itemMilestone":"1000689153"}2017-07-21 13:14:19.6940 13 Info LibraryCatalogIndex Searching for all records matching: Stop Profiling2017-07-21 13:14:19.8431 20 Info SyncManager Finished requesting sync on all sync clients.2017-07-21 13:14:20.9979 1 Info AppCommand (Timed) Executing command: Profiling|Kind=Stop2017-07-21 13:14:21.0059 1 Info ProfilingAppCommand Executing profiling command with Kind=Stop and State=Started2017-07-21 13:14:21.0149 1 Info ProfilingAppCommand Stopping profiling.
I edited the above description to update my Logos Bible Software version: Logos Bible Software 7.7 SR-1 (7.7.0.0018). Hopefully that didn't throw anyone off!
It would be useful to repeat that with v 7.8, due to be released next week, as that includes some significant performance improvements. You can download the current RC3 version if you go to the Desktop Beta forum as it is very stable.
Dave Hooton: It would be useful to repeat that with v 7.8, due to be released next week, as that includes some significant performance improvements. You can download the current RC3 version if you go to the Desktop Beta forum as it is very stable.
Thanks, Dave! I had considered that. Will do.
Device: Surface 3Logos Bible Software 7.8 (7.8.0.0029)OS: Windows 10 (1703)CPU: Intel(R) Atom(TM) x7-Z8700 CPU @ 1.60GHzRAM: 4.00 GBDisplay 1: Surface Display 10.8” display (1920 x 1280); Aspect ratio: 3:2Display 2: Dell E2715H 27" IPS LED Monitor (1920 x 1080)Display Adapter: Intel(R) HD Graphics
This time I installed Logos 7.8 RC3, restarted my computer, and then opened and closed Logos once before running diagnostic logging. I followed the same procedure as a before opening Logos to a blank layout, starting the Profiler, typing "1000" into the command box, and hitting enter on the 1000 Bible Images media resource. It took about thirty seconds before 1000 Bible Images opened and rendered fully in my main window, although it was still a bit sluggish at first. Then after right-clicking its tab and selecting "Open in a Floating Window", Logos stalled for almost six minutes displaying the message "Not Responding" for most of that time (after I left-clicked on the window to focus/activate it). The window filled the screen but wasn't quite maximized, so I maximized it and then moved it across my displays (e.g., WIN + SHIFT + Left/Right/Up/Down). I then closed the window, stopped Logos Profiler, and closed the program.
Here are the logs and another lovely screenshot (this time a snowy blizzard theme!):
8306.Logos 7 Stalls Opening Media Resource 1000 Bible Images 3.log
We already have an open case for slow performance when opening 1000 Bible Images (and we have recreated the problem locally). I'll add a link to this thread in the case notes so that we can post and update when the issue is resolved.
Andrew Batishko | Faithlife software developer
Andrew Batishko (Faithlife): We already have an open case for slow performance when opening 1000 Bible Images (and we have recreated the problem locally). I'll add a link to this thread in the case notes so that we can post and update when the issue is resolved.
Thank you, Andrew. Also be sure to note that 1000 Bible Images is not the only resource that has these or similar problems. I provided similar examples earlier in the thread. Hopefully whatever problems you are able to resolve with this resource will benefit other resources and related aspects of the software as well.
I also used Logos Profiler, so if you would like more detailed logs just let me know.
Media resources in general can be problematic, but 1000 Bible Images is a particularly good example of the problem.
The use of the Logos Profiler doesn't actually do much good without the full profiling data. This information is not contained in the regular log file, and can be very large. In this case, we are able to easily recreate the problem with media files, so no profiling data is needed.
As indicated on the thread regarding the tabs "dancing", there is a case open for that. I have no information as to when or if this will be fixed. Unless this activity is happening at the same time as your other reported issues, then it is completely unrelated. If it's happening at the same time, then it is extremely likely to be the cause of the other performance issues.
Andrew Batishko (Faithlife): Media resources in general can be problematic, but 1000 Bible Images is a particularly good example of the problem. The use of the Logos Profiler doesn't actually do much good without the full profiling data. This information is not contained in the regular log file, and can be very large. In this case, we are able to easily recreate the problem with media files, so no profiling data is needed. As indicated on the thread regarding the tabs "dancing", there is a case open for that. I have no information as to when or if this will be fixed. Unless this activity is happening at the same time as your other reported issues, then it is completely unrelated. If it's happening at the same time, then it is extremely likely to be the cause of the other performance issues.
Great, thanks for the clarification. This all makes good sense.
I may follow-up and try to get fresh logs on the context menu's stalling and collapsing, assuming I still encounter that issue with the latest version. It's different than the "dancing" tabs, which I don't recall seeing for a while.