Bugzilla

:whimboo, I spent a bit of time looking into this today, and I haven't been able to get crashes saved/moved to the correct location. I've set the `MINIDUMP_SAVE_PATH` environment variable in multiple locations, but none of them seem to have an effect on where the crash dump file gets moved too or saved in. I am seeing the MINIDUMP_SAVE_PATH in the capabilities in a geckodriver log (it's also set in the process that the browser is started from):
```
17:22:43     INFO -  raptor-browsertime Info: 1708708963430	webdriver::server	DEBUG	-> POST /session {"capabilities":{"firstMatch":[{}],"alwaysMatch":{"browserName":"firefox","pageLoadStrategy":"none","moz:fir ... linux-gnu/dist/bin/firefox","args":["-no-remote"],"env":{"MINIDUMP_SAVE_PATH":"/home/sparky/crashes"}},"webSocketUrl":true}}}
```

I see the minidumps being produced in the temporary profile folder that geckodriver produces, but the folder gets deleted before the minidumps get moved or saved elsewhere.

Do you know what I might be missing here?

:whimboo, I spent a bit of time looking into this today, and I haven't been able to get crashes saved/moved to the correct location. I've set the `MINIDUMP_SAVE_PATH` environment variable in multiple locations, but none of them seem to have an effect on where the crash dump file gets moved too or saved in. I am seeing the MINIDUMP_SAVE_PATH in the capabilities in a geckodriver log though (it's also set in the process that the browser is started from):
```
17:22:43     INFO -  raptor-browsertime Info: 1708708963430	webdriver::server	DEBUG	-> POST /session {"capabilities":{"firstMatch":[{}],"alwaysMatch":{"browserName":"firefox","pageLoadStrategy":"none","moz:fir ... linux-gnu/dist/bin/firefox","args":["-no-remote"],"env":{"MINIDUMP_SAVE_PATH":"/home/sparky/crashes"}},"webSocketUrl":true}}}
```

I see the minidumps being produced in the temporary profile folder that geckodriver produces, but the folder gets deleted before the minidumps get moved or saved elsewhere.

Do you know what I might be missing here?