To immediately update to the current beta enter the Update Now command. Otherwise, the app will automatically update the next time it's scheduled to check for updates.
Release Notes
Mac
Windows
I'm not getting the expected behavior with the Logos Windows Profiler Utility.
I followed the instructions through step 4 exactly as is in the instructions. I did steps 5 and 6 slightly different because my extraction utility is different. I did, however, extract all files to the folder C:\Users\Public\Downloads\LogosProfilerSupport as indicted in the instructions.
I updated Logos to 7.7 Beta 1 (7.7.0.0005).
I then followed the instructions in "Step 2: How to Get the Log File" but no window opened with a folder selected (as indicated in the instructions).
I also did not see any new folders in the folder C:\Users\Public\Downloads\LogosProfilerSupport (the new folder for the Profiler) or in C:\Users\timhe\Documents\Logos Log Files (where log files in the past were saved).
Doesn't the Profiler Utility need to be installed or launched after step 6 in the instructions so it is ready for the commands from Logos?
I did, however, extract all files to the folder C:\Users\Public\Downloads\LogosProfilerSupport as indicted in the instructions.
The instructions are wrong. It should be:
C:\Users\<Username>\Downloads\LogosProfilerSupport
You can see where it's looking by examining the usual logs for a line like:
2017-05-08 22:54:52.5389 1 Error ProfilingAppCommand Couldn't find profiler support files in C:\Users\RandyW\Downloads\LogosProfilerSupport
Thank you Randy.
Extracting the Profiler to C:\Users\<Username>\Downloads\LogosProfilerSupport as you noted did the trick. I now get an open window with a zip folder selected when I stop the profiling.
Will there also be a profiler for Mac?
Yes, one already exists as part of the Logging Utility: https://www.logos.com/support/logos5/mac/problem
(Use the "Sample" button to collect a performance sample.)
I did steps 5 and 6 slightly different because my extraction utility is different. I did, however, extract all files to the folder C:\Users\Public\Downloads\LogosProfilerSupport as indicted in the instructions.
The instructions were intended to illustrate the results of simply extracting to the default folder used by the "Extract All..." command, not prescriptive about the folder name. [:)]
But I see how this could be confusing and we'll make Logos 7.7 Beta 2 also check that public downloads folder for the support files (since it doesn't really hurt to check an additional location).
The instructions were intended to illustrate the results of simply extracting to the default folder used by the "Extract All..." command, not prescriptive about the folder name.
But it is prescriptive as Logos expects it in my Downloads folder! I don't use a 'default' folder for downloads and I use Firefox. The instructions require clarifcation about the intended download location.
But I see how this could be confusing and we'll make Logos 7.7 Beta 2 also check that public downloads folder for the support files
With Logos installed in two user accounts on my notebook \Public\Downloads would be a convenient single location.
I think the instructions should be extractor-agnostic, stating requirements/locations rather than clicks on screens that may not match the user's utility.
I've added a clarification to Step 5.
Question:
Does using the profiler also install a folder called "JetBrains" ?
I ran the utility, found the file (as expected) and next to it was a folder called "JetBrains" with a time stamp near the time stamp of the profile. Either I have a problem (malware?), or JetBrains is part of the profile utility in some way.
Explanation please?
Thanks in advance.
JetBrains makes the dotTrace profiling software used for the utility: https://www.jetbrains.com/profiler/
I'm not sure where you're seeing that folder though. There are a lot of JetBrains* files extracted from the utility zip file in the downloads directory, but I haven't seen any created in the output folder after the trace.
Actually, I do see a JetBrains directory in the Temp folder (the parent of the output directory). Is that what you're referring to? Either way this is safe and a normal part of the utility.
Yes. That's what I'm seeing.
Thanks for the explanation.
