Vlad
This morning I had an occurence where the behavior was not consistent. For some reason even with Orion still active over night, no sluggishness during or after the login.
What I'm thinking/wondering is if this may be related to the state of specific tabs, which are loaded/active etc.?
Sorry if it is a stupid question, but is there any "tab index" or similar page where one can see an inventory of open tabs and with the current state of the tab? I'm thinking this could be tied to a specific web page behavior and such a tab state inventory would over a number of tests allow to find the most likely candidate to be causing the issues...
Edit: Found the reference to ~/Library/Application\ Support/Orion/Defaults/browser_state.plist
in the Orion FAQ/Technical Information, but seeing as that file is only 40 bytes, I really don't think that it's keeping the current state of tabs...
The named_windows.plist
does look a bit more promising though.
Edit2: Upon every log in, I will try to perform the following to build a record of tab states over time:
cp ~/Library/Application\ Support/Orion/Defaults/named_windows.plist ~/Documents/bugreports/orion-tabstate/named_windows-`date +%Y-%m-%d-%H%M%S`.plist
Edit3: Refining above even further, as I also realized it would be good with some type of metadata about how long the computer has been sleeping at the point the plist was copied as well.
So, full command line as follows:
mkdir ~/Documents/bugreports/orion-tabstate/`date +%Y-%m-%d-%H%M%S` && cd "$_" ; cp ~/Library/Application\ Support/Orion/Defaults/named_windows.plist ./ ; pmset -g log | grep -e " Sleep " -e " Wake " | tail -100 > pmset.log
(Not properly formatted above; After "Sleep" and "Wake" there is actually double space characters to improve the filtering)
And to break it down:
mkdir ... && cd "$_"
creates a new folder with date and time as name, and immediately changes directory to the last argument of the mkdir command (making the newly created folder the working directory).
cp
simply copies the named_windows.plist
into the the working directory.
pmset -g log
retrieves the power management settings log grep
ing it for sleep and wake events and saving the tail
(last) 100 log rows output into pmset.log
in the working directory.
- 100 is an arbitrary number which may or may not have to be tweaked later on...