Check OOM handling in MediaTransportHandlerSTS::GetIceLog
Categories
(Core :: WebRTC: Signaling, task, P3)
Tracking
()
| 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.
| Assignee | ||
Comment 1•5 years ago
|
||
| Reporter | ||
Comment 2•5 years ago
|
||
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 | ||
Comment 3•5 years ago
|
||
Updated•5 years ago
|
| Assignee | ||
Updated•5 years ago
|
Updated•5 years ago
|
Comment 4•5 years ago
|
||
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.
| Assignee | ||
Updated•5 years ago
|
| Reporter | ||
Comment 6•5 years ago
|
||
I think this was resolved as a duplicate (of the bug it was spawned from) accidentally. Shouldn't the patch attached just land?
| Assignee | ||
Comment 7•5 years ago
|
||
Yes, thanks Simon, this was indeed closed by mistake. Though, the patch shouldn't land as written.
Updated•1 year ago
|
Description
•