1202399 - Marionette shouldn't store crash reports in the temporary profile but under the application crash folder

Status: RESOLVED WONTFIX

(Remote Protocol :: Marionette, defect)

Description

[Henrik Skupin [:whimboo][⌚️UTC+2]]

Since we flipped with our Mozmill tests to Marionette, we no longer can analyze crash reports. Well, for now we don't have the symbol handling implemented, but did this manually by checking the application pending crash folder like "%appdata/mozilla/firefox/crash reports" on Windows.

Given that Marionette always creates a fresh temporary profile and minidumps are getting stored in that by default, those are lost because Marionette removes that profile after the run. Instead of using this profile for the minidump files, they should be installed into the application default dir.

Maybe this should only happen if no symbols are present and nothing can be printed to the console. Not exactly sure but this might affect our Firefox UI Tests for beta and release builds, which might not have symbols present.

Ted, given that by default (outside of automation) minidumps land in that application folder I wonder if we have a different strategy for automation. Is there a pref which controls the location? Or does Firefox usually move the minidumps over to the pending folder.

Comment 1

[Henrik Skupin [:whimboo][⌚️UTC+2]]

The appdata folder can be retrieved via "Services.dirsvc.get('UAppData', Ci.nsIFile).path". So in case marionette client needs the location it would be a matter of transferring it from Firefox.

Comment 2

[(not currently active) Ted Mielczarek]

This is controlled by the MOZ_CRASHREPORTER_NO_REPORT environment variable, which is set by mozrunner. bug 1200975 added a `show_crash_reporter=True` argument you could use.

Unfortunately the crash reporter dialog is what actually moves crash reports to the directory where they show up under about:crashes, so there's no built-in way to move them without having the dialog show up. If you want to handle these in automation without the dialog I suggest you make Mozmill tests set MINIDUMP_STACKWALK, and also the symbol path (you can pass a URL for that) and you will get a stack printed to the log like we do in our other tests that run in CI.

Comment 3

[Henrik Skupin [:whimboo][⌚️UTC+2]]

We no longer need anything like that given that our mozharness script has mozcrash support meanwhile. So it works great. I will close as wontfix.