- Edited
What information I should collect in order to usefully report occassional glitches? Especially after 172.2-RC came out, I've been using Orion as my primary browser. Though I still have issues on Mojave for streaming (Netflix and that other website reported elsewhere), it feels good for day-to-day use. When I do run across glitches I'd like to usefully report them but not sure what would be useful to capture and report at first pass. Othewrise I'm just posting notes about some weird thing that happened and went away after I restarted.
As a few recent examples,
- Became very sluggish (entering text almost went letter by letter)
- High memory usage (when I restart with same windows, Memory Used and/or Swap is GBs less)
- Audio garbled (this happened on Youtube where it could play the video but the audio was garbled until I refreshed the window and eventually restarted the browser)
- Window opens behind existing tabs (occassionally I'll use a keyboard shortcut to open a new window and it flickers and then sends it to the back and keeps the last window on top -- Command-` brings me back to the new window I had intended to start using)
These things rarely produce a crash so no crash report to collect and send. Then as I am often in the middle of something when these things happen, I can't just stop to report it and keep things on hold while we work through the issue.
Should I proactively get a list of Orion processes? Run Sample Process or Spindump on one of the them?
