Open Bug 1769219 Opened 2 years ago Updated 2 years ago

[QM_TRY] Use process_id, stack_id and frame_id to determine propagation stacks

Categories

(Core :: Storage: Quota Manager, task)

task

Tracking

()

People

(Reporter: jstutte, Unassigned)

References

(Blocks 1 open bug)

Details

Now that we have the process_id, frame_id and stack_id, we can easily reconstruct propagation stacks by aggregating on process_id, thread_id and stack_id and sorting by the frame_id. This would entirely replace the current heuristics and give perfect results (unless there were data transfer problems). Until we modernize all uses of QM_TRY, we will need to support both formats, though.

Summary: Use stack_id and frame_id to determine propagation stacks → Use process_id, stack_id and frame_id to determine propagation stacks
Summary: Use process_id, stack_id and frame_id to determine propagation stacks → [QM_TRY] Use process_id, stack_id and frame_id to determine propagation stacks
You need to log in before you can comment on or make changes to this bug.