You have to isolate the problem. This means documenting the conditions under which the problem can be consistently reproduced. Break down it down into possible causes and rule them all out, 1 by 1. A good place to start is with the distro, with a question along the lines of this:
Do you see the problem on distros other than Slackware (debian/centos etc) ? If Yes: - The problem is isolated to the application if No: - The problem is isolated to Slackware Use the information from the answer above to formulate a follow-up question. Rinse, repeat, and continue until you either find the root cause of the problem or decide to go do something else ;) Based on the information you've given about the nature of the problem, I could make educated guesses about the root cause. But even IF my assumptions are correct, I still need to go through and isolate the problem if I want to actually solve it. I'll fire it up on my system tonight and see if I notice any odd behavior when searching for an address. On Mon, Dec 2, 2019 at 2:23 PM Rich Shepard <[email protected]> wrote: > I started this thread a while ago and would like to explore further what > might be causing google earth to crash when navigating to an entered > address, but not when zoomed and panned to the same address. > > It must be connected to the CPU (Ryzen7) or motherboard (Asus Prime > X470-Pro9) hardware or libraries in Slackware-14.2/x86_64. The kernel is > 4.19.84. > > What tests or trials could I do to try to isolate the reason GE mis-behaves > this way? Are there diagnostic tools that might be applied? > > Regards, > > Rich > _______________________________________________ > PLUG mailing list > [email protected] > http://lists.pdxlinux.org/mailman/listinfo/plug > _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
