Closed Bug 1977272 Opened 1 year ago Closed 1 year ago

Fuzzing debug builds crash on startup

Categories

(Core :: JavaScript Engine, defect, P3)

defect

Tracking

()

RESOLVED FIXED
142 Branch
Tracking Status
firefox-esr128 --- unaffected
firefox-esr140 --- unaffected
firefox140 --- unaffected
firefox141 --- unaffected
firefox142 --- fixed

People

(Reporter: tsmith, Unassigned)

References

(Blocks 1 open bug, Regression)

Details

(Keywords: pernosco, regression, Whiteboard: [fuzzblocker])

Fuzzing debug builds crash on startup. Many of the stacks point at but are not limited to jit, gc and other js related code.

STR:

  • Launch a fuzzing debug build with the following prefs js file. Non-optimized builds seem to be less or not affected.

The following prefs.js file seems to be required.

user_pref("network.proxy.autoconfig_url", "data:text/plain,function FindProxyForURL(url, host) { if (host == 'localhost' || host == '127.0.0.1') { return 'DIRECT'; } else { return 'PROXY 127.0.0.1:6'; } }");
user_pref("network.proxy.type", 2);

BAD:

Changeset: 9ccc6a2267cbf69c621fec973bd28573c2a45a1f
Build ID: 20250709215737

GOOD:

Changeset: a5500d271fe3a1fefb4d81d96fc4abd00d9eade7
Build ID: 20250709093153

Could this be due to bug 1962026?

Flags: needinfo?(sphink)

Oh. Yes, almost certainly.

I only tested with the JS shell. I bet the browser is unhappy.

I knew it couldn't be that easy...

Flags: needinfo?(sphink)
Keywords: regression
Regressed by: 1962026

A Pernosco session is available here: https://pernos.co/debug/E-cdjR-cdAKv3efCV13xUQ/index.html

Keywords: pernosco
Blocks: sm-runtime
Severity: -- → S3
Priority: -- → P3

Hi Matthew can you please in crease the priority of this issue since it is a major issue for fuzzing. It is triggering start up crashes and spamming fuzzmanager with unbucketable (too many signatures to bucket) scary looking crashes.

Flags: needinfo?(mgaudet)

Oh I misunderstood: I thought it was only fuzzing that tested PAC, and I missed the [fuzzblocker] tag.

Severity: S3 → S2
Flags: needinfo?(mgaudet)

The regressing change is being backed out, so hopefully this will return to normal once that happens.

Marking as fixed now that bug 1962026 is backed out.

Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 142 Branch
QA Whiteboard: [qa-triage-done-c143/b142]
You need to log in before you can comment on or make changes to this bug.