I'm sometimes experiencing unusual delays/hanging in the UI (since .34). No actual crashes, just weird sluggishness/freezes in the GUI, usually with the Windows blue circle whirling. Affecting three different PCs. Had no such issues before .34.
--At startup, main startup pane displaying album covers is sometimes black for several seconds.
--Selecting Tools > Options; sometimes a delay of up to 8 seconds before Options dialog appears (very weird)
--Sometimes: up to approx. 15 seconds waiting for main application window to appear upon launch.
--At startup, entire GUI 'stretches' vertically a little bit while hanging (blue circle whirling), for approx. 4-5 seconds, then returns to normal; have seen this come and go with different versions over the years, esp. on tablets.
I notice these most on an older MS Surface Pro 4 tablet, a slower system. However, each of the above-noted effects present on faster, desktop PCs too, although with shorter durations (divide by 2 or 3).
In case it matters:
--Each system I use is a Portable install(*).
--Windows Defender is completely disabled/excluded
*--Regarding use of Portable mode:
User "Thouston" reported same/similar observations, also stating that he is not using a portable installation, in the .37 release thread:
https://yabb.jriver.com/interact/index.php/topic,127742.0.htmlUser "Peter_T" reported same/similar observations, evidently not using a portable installation, in the .34 release thread:
https://yabb.jriver.com/interact/index.php/topic,127629.0.htmlThe reasons I prefer portable installations are two:
1. I periodically regress Windows PC system partition(s) to a last-known good state, using partition imaging software. This is a quick, failsafe approach to avoid, e.g., problems caused by bad Windows updates, or other system/application issues which would be too time consuming to research and problem-solve on their own. Portable applications 'installed' on a non-system partition are not affected by this. If I regress a system partition to a last-known good state, my portable applications remain exactly as they last were; all their updates and/or settings where I want them. Independence.
2. The same concept as #1 above, but applied reciprocally to the portable application(s): I can close a portable application, ZIP the whole 'install' folder, thereby capturing a convenient regression-point for just that application. E.g., before updating MC, I regress to the last known good ZIP of the portable install, apply the update to that, update the library, and ZIP again. I do this with all my portable applications. Indeed: MC's automatic backup and manual restore is robust, but the portable folder ZIP is a no-brainer, absolute 'capture' of the state of the entire application and library. This approach, e.g., lets me 'back-step' gracefully from a beta update, or an experimental VST plugin, reverting in seconds to the previous successful/preferred state with a couple clicks -- not requiring use of the Windows uninstall/reinstall facility/routine(s), and setting aside any possibility of troublesome leftovers/fragments in the Windows registry.
It's about having total independence between system administration and application administration (those that can be operated portably), and independent backup imaging and restoring of both as well.
The support for bona fide portable operation in JRiver MC is one of the key reasons I value it so highly.
Author
Topic: GUI phenomena -- first appeared in .34 (Read 786 times)