Closed Bug 1599507 Opened 6 years ago Closed 4 years ago

Crash in [@ std::vector<T>::_M_emplace_back_aux<T>]

Categories

(Core :: DOM: Networking, defect, P2)

Unspecified
Linux
defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: netoeuler, Unassigned)

References

Details

(Keywords: crash, Whiteboard: [necko-triaged])

Crash Data

This bug is for crash report bp-dd7c7597-3693-4cba-80fb-88d130191126.

Top 10 frames of crashing thread:

0 libxul.so libxul.so@0x3e92a00 
1 libxul.so libxul.so@0x3d0409f 
2 libxul.so libxul.so@0x3ec39f5 
3 libxul.so libxul.so@0x6ef65af 
4 libxul.so libxul.so@0x3e57e06 
5 libxul.so libxul.so@0x3d0409f 
6 libxul.so libxul.so@0x107b32f 
7 memfd:pulseaudio (deleted) memfd:pulseaudio @0xdf00007 
8 libxul.so libxul.so@0x3e57645 
9 libxul.so libxul.so@0x107b32f 

No symbols in this crash report, it is likely not actionable as-is.

See Also: → 1600026

We've got partial symbols now (no source files or lines), updating the signature.

Crash Signature: [@ libxul.so@0x3e92a00 | libxul.so@0x3d0409f | libxul.so@0x3ec39f5 | libxul.so@0x6ef65af | libxul.so@0x3e57e06 | libxul.so@0x3d0409f | libxul.so@0x107b32f | memfd:pulseaudio (deleted)@0xdf00007] → [@ std::vector<T>::_M_emplace_back_aux<T>]
Summary: Crash in [@ libxul.so@0x3e92a00 | libxul.so@0x3d0409f | libxul.so@0x3ec39f5 | libxul.so@0x6ef65af | libxul.so@0x3e57e06 | libxul.so@0x3d0409f | libxul.so@0x107b32f | memfd:pulseaudio (deleted)@0xdf00007] → Crash in [@ std::vector<T>::_M_emplace_back_aux<T>]

I've looked a bit through the crashes and this seems to be affecting mainly ESR68 on Debian. The crashes aren't very helpful since we don't have files & line information. It might be that the signature is over-generic because of that and it's catching unrelated crashes.

I have 3 Firefox in Debian 9 (70, ESR, Dev) and all of them start to crash suddenly. I made a fresh install of Debian 9, updated the Kernel, but the crashes still persists. Now I'm using ESR 68.2.0esr (already came installed) and all this bugs that I reported came from it.
There's something more that I can provide that can help to find the cause of this issue?

From what I can tell, this is happening due to mozilla::dom::network::ConnectionProxy::Create, so I'm putting into Core :: Networking for triage.

Component: General → Networking
Product: Firefox → Core
Component: Networking → DOM: Networking
Priority: -- → P2
Whiteboard: [necko-triaged]
You need to log in before you can comment on or make changes to this bug.