Media Debugging Tips: Difference between revisions

drm edits
(clip)
(drm edits)
Line 94: Line 94:
# Within the profiler tab click the 'upload local p[rofile' button on the upper right side of the tab. Once the upload is complete, a drop down menu will open displaying the URL of the profile. Select this text and copy it.
# Within the profiler tab click the 'upload local p[rofile' button on the upper right side of the tab. Once the upload is complete, a drop down menu will open displaying the URL of the profile. Select this text and copy it.
# Share the URL of the profile for analysis with the engineer you are working with.
# Share the URL of the profile for analysis with the engineer you are working with.
Generating text based logs in a local folder -
# Open a command line console and browse to the install location for Firefox Nightly.
# On Windows, enter 'set MOZ_DISABLE_GMP_SANDBOX=1'(return)
# Launch Firefox using a clean profile from the command console (firefox.exe (return) or firefox.exe -p (return))
# In the browser, open a tab and view about:logging
# Enter 'timestamp,sync,GMP:5,EME:5' in the 'new log modules' text edit and click on 'Set Log Modules'
# Select the 'Logging to a file' radio button
# Choose an appropriate path for log output.<br/>Note, on Windows, change any default 'AppData\Local\' path to a 'AppData\LocalLow\' path so that content processes can access the file system. For example:<br/>C:\Users\(username)\AppData\LocalLow\Temp\emelogs
# Click the 'Set Log File' button.
# Click the 'Start Logging' button.
# Open a test tab and play the media past a point where the issue occurs.
# Close the test tab
# In about:logging, click 'Stop Logging'.
In the temp dir, you should get a few logs (something like 'emelogs.txt-child.23884.moz_log' and 'emelog.txt-main.23435.moz_log'. Attach logs to your Bugzilla report.
Confirmed users
1,982

edits