Open Bug 1631386 Opened 5 years ago Updated 1 year ago

Check OOM handling in MediaTransportHandlerSTS::GetIceLog

Categories

(Core :: WebRTC: Signaling, task, P3)

task

Tracking

()

REOPENED
Tracking Status
firefox-esr68 --- wontfix
firefox75 --- wontfix
firefox76 --- wontfix
firefox77 --- wontfix
firefox78 --- fix-optional

People

(Reporter: sg, Assigned: ng)

References

Details

Attachments

(1 file)

Bug 1628715 identified that the return value of a fallible call to nsTArray::AppendElement was discarded. It was changed to crash in this case for the time being. It should be checked if a different error handling should be done here.

Actually, it would be preferrable to call SetCapacity once outside the loop, since the number of elements which will be added is known. This avoids repeated reallocations of the array, and ensures that there can't be a failure within the loop.

Assignee: nobody → na-g
Status: NEW → ASSIGNED
Priority: -- → P2

There's a r+ patch which didn't land and no activity in this bug for 2 weeks.
:ng, could you have a look please?
For more information, please visit auto_nag documentation.

Flags: needinfo?(na-g)
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Flags: needinfo?(na-g)
Resolution: --- → DUPLICATE

I think this was resolved as a duplicate (of the bug it was spawned from) accidentally. Shouldn't the patch attached just land?

Status: RESOLVED → REOPENED
Flags: needinfo?(na-g)
Resolution: DUPLICATE → ---

Yes, thanks Simon, this was indeed closed by mistake. Though, the patch shouldn't land as written.

Flags: needinfo?(na-g)
Priority: P2 → P3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: