utime called from nsJAR::Extract in content process of Firefox desktop

REOPENED
Unassigned

Status

()

P3
normal
REOPENED
2 years ago
a year ago

People

(Reporter: tedd, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: sblc4, sb-addons, tpi:-, crash signature)

(Reporter)

Updated

2 years ago
Crash Signature: [@ libc-2.19.so@0xeafa7 ]
nsJAR::Extract invoked from JS in a content process?  Could this be an add-on doing that?

Updated

2 years ago
Flags: needinfo?(twalker)
Only one crash reported so far, it looks like: bp-95bb7505-4343-4955-abb6-2e0182160811

Updated

2 years ago
Whiteboard: [sb?] → sblc2, sb-addons
Still only one crash ever reported.
Flags: needinfo?(twalker)
Whiteboard: sblc2, sb-addons → sblc2, sb-addons, tpi:-
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
See Also: → bug 1322784
…Bugzilla, why did you do that.  (This should either be a dup of 1322784 if it's about utime in general, or resolved WFM/Invalid/Incomplete/something if it's specifically about nsJAR in particular and it hasn't shown up again, but not FIXED.)
Status: RESOLVED → REOPENED
Resolution: FIXED → ---

Updated

2 years ago
Whiteboard: sblc2, sb-addons, tpi:- → sblc4, sb-addons, tpi:-

Updated

2 years ago
Status: REOPENED → RESOLVED
Last Resolved: 2 years ago2 years ago
Resolution: --- → WONTFIX
Resolution: WONTFIX → WORKSFORME
I found a few new nsJAR crashes on crash-stats.
Status: RESOLVED → REOPENED
Crash Signature: [@ libc-2.19.so@0xeafa7 ] → [@ libc-2.19.so@0xeafa7 ] [@ libc-2.25.so@0xddb97 ] [@ libc-2.24.so@0xdae87 ]
Resolution: WORKSFORME → ---
Summary: Seccomp sandbox violation: sys_utime called in content process of Firefox desktop → utime called from nsJAR::Extract in content process of Firefox desktop
Crash Signature: [@ libc-2.19.so@0xeafa7 ] [@ libc-2.25.so@0xddb97 ] [@ libc-2.24.so@0xdae87 ] → [@ libc-2.19.so@0xeafa7 ] [@ libc-2.25.so@0xddb97 ] [@ libc-2.24.so@0xdae87 ] [@ libc-2.23.so@0xdaa57 ]

Updated

a year ago
Priority: -- → P3

Updated

a year ago
OS: Unspecified → Linux
You need to log in before you can comment on or make changes to this bug.