This is most probably a false alarm, caused by having a topmost frame as ERROR right after the WARNING that would have invalidated this stack:
```
{
"submit_timeabs": 1619180038043,
"session_start_time": "2021-04-23T11:13:00",
"submission_date": "2021-04-23",
"build_id": "20210422190146",
"client_id": "0971cb28-0187-4451-a259-940168b6fcde",
"session_id": "417ffb72-8c2e-4aca-9e3f-39ad86ea8cce",
"event_timestamp": 4581,
"seq": 10,
"context": "Initialization::TemporaryStorage",
"source_file": "dom/quota/ActorsParent.cpp",
"source_line": "4739",
"severity": "WARNING",
"result": "NS_ERROR_FILE_IS_LOCKED"
},
{
"submit_timeabs": 1619180038043,
"session_start_time": "2021-04-23T11:13:00",
"submission_date": "2021-04-23",
"build_id": "20210422190146",
"client_id": "0971cb28-0187-4451-a259-940168b6fcde",
"session_id": "417ffb72-8c2e-4aca-9e3f-39ad86ea8cce",
"event_timestamp": 4581,
"seq": 11,
"context": "Initialization::TemporaryStorage",
"source_file": "dom/quota/ActorsParent.cpp",
"source_line": "4739",
"severity": "ERROR",
"result": "NS_ERROR_FILE_IS_LOCKED"
},
```
We could mitigate this, if we include `severity` in the identifier of a stack. Currently we have only the combination of revision + source + line + errorcode.
Bug 1708138 Comment 1 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
This is most probably a false alarm, caused by having a topmost frame as ERROR right after the WARNING that would have invalidated this stack:
```
{
"submit_timeabs": 1619180038043,
"session_start_time": "2021-04-23T11:13:00",
"submission_date": "2021-04-23",
"build_id": "20210422190146",
"client_id": "0971cb28-0187-4451-a259-940168b6fcde",
"session_id": "417ffb72-8c2e-4aca-9e3f-39ad86ea8cce",
"event_timestamp": 4581,
"seq": 10,
"context": "Initialization::TemporaryStorage",
"source_file": "dom/quota/ActorsParent.cpp",
"source_line": "4739",
"severity": "WARNING",
"result": "NS_ERROR_FILE_IS_LOCKED"
},
{
"submit_timeabs": 1619180038043,
"session_start_time": "2021-04-23T11:13:00",
"submission_date": "2021-04-23",
"build_id": "20210422190146",
"client_id": "0971cb28-0187-4451-a259-940168b6fcde",
"session_id": "417ffb72-8c2e-4aca-9e3f-39ad86ea8cce",
"event_timestamp": 4581,
"seq": 11,
"context": "Initialization::TemporaryStorage",
"source_file": "dom/quota/ActorsParent.cpp",
"source_line": "4739",
"severity": "ERROR",
"result": "NS_ERROR_FILE_IS_LOCKED"
},
```
We could mitigate this, if we include `severity` in the identifier of a stack frame. Currently we have only the combination of revision + source + line + errorcode.