Closed Bug 1564921 Opened 5 years ago Closed 5 years ago

Crash in [@ nsZipArchive::BuildSynthetics]

Categories

(Core :: Networking: JAR, defect)

68 Branch
Unspecified
Android
defect
Not set
critical

Tracking

()

RESOLVED DUPLICATE of bug 1550815
Tracking Status
firefox68 --- affected

People

(Reporter: marcia, Unassigned)

Details

(Keywords: crash, regression)

Crash Data

This bug is for crash report bp-e522eb14-6020-4f93-80b9-e6f510190710.

Seen while looking at Fennec 68 release crashes. This regression may have been in 67 cycle, but is much more prominent in early 68 crashes: https://bit.ly/2YHdCmW/. APIs range from 16-28 and are spread across a wide variety of devices.

Comments are not particularly useful.

Some of the code was touched in Bug 1551183 during the 68 cycle.

Top 10 frames of crashing thread:

0 libxul.so nsZipArchive::BuildSynthetics modules/libjar/nsZipArchive.cpp:766
1 libxul.so nsZipArchive::FindInit modules/libjar/nsZipArchive.cpp:550
2 libxul.so nsJAR::FindEntries modules/libjar/nsJAR.cpp:233
3 libxul.so mozilla::AddonManagerStartup::EnumerateJAR toolkit/mozapps/extensions/AddonManagerStartup.cpp:633
4 libxul.so mozilla::AddonManagerStartup::EnumerateJARSubtree toolkit/mozapps/extensions/AddonManagerStartup.cpp:661
5 libxul.so NS_InvokeByIndex xpcom/reflect/xptcall/md/unix/xptcinvoke_arm.cpp:167
6 libxul.so XPCWrappedNative::CallMethod js/xpconnect/src/XPCWrappedNative.cpp:1157
7 libxul.so XPC_WN_CallMethod js/xpconnect/src/XPCWrappedNativeJSOps.cpp:943
8 libxul.so js::InternalCallOrConstruct js/src/vm/Interpreter.cpp:535
9 libxul.so Interpret js/src/vm/Interpreter.cpp:590

Nhi - Can you take a look when you get a chance to see if this is in the correct component? Thanks!

Flags: needinfo?(nhnguyen)

Michal, could you have a look please?

Flags: needinfo?(nhnguyen) → needinfo?(michal.novotny)

The cause is IMO the same as in bug 1550815, it just crashes at different place.

Status: NEW → RESOLVED
Closed: 5 years ago
Flags: needinfo?(michal.novotny)
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.