Closed Bug 736204 Opened 13 years ago Closed 1 year ago

Unbounded title size setting causes browser to stop responding

Categories

(Core :: General, defect)

Product:
Core
Component:
General
Type:
defect

Tracking

()

Status:
RESOLVED WONTFIX

People

(Reporter: martijn.martijn, Unassigned)

References

(
URL
)

Details

(Keywords: crash, testcase, Whiteboard: [native-crash])

See https://bugzilla.mozilla.org/attachment.cgi?id=591441 , which is the testcase from bug 721006. It's making an exponentially big title. The crash in bug 721006 seems fixed, but Fennec still closes by itself, when visiting that page, letting it stay there for a while, then trying to reload. The crash reporter doesn't come up. Tested on the HTC Desire HD, Android 2.3.5 and Samsung Galaxy Nexus, Android 4.0.2 using Fennec build from 2012-03-15.
This testcase is fairly edge casey. not a blocker, but it does cause the browser to crash.
This also causes issues with desktop firefox.
Whiteboard: [native-crash]
Desktop affected, moving to core. feel free to assign the right component.
Assignee: nobody → general
Component: General → JavaScript Engine
Product: Fennec Native → Core
QA Contact: general → general
Assignee: general → nobody
Severity: critical → S2

Doesn't appear to be a crash on desktop; going to re-assign this out of the JS engine, because this just seems to be a 'what happens when parent process has gigabytes of strings' bug.

This probably should get re-triaged into a component responsible for title, and avoiding setting enormous titles repeatedly.

No longer blocks: sm-defects-crashes
Severity: S2 → --
Component: JavaScript Engine → General
OS: Android → All
Hardware: ARM → All
Summary: Testcase from bug 721006 and reloading causes Fennec to die → Unbounded title size setting causes browser to stop responding

I think it is fine to close this. If this becomes an issue, we can file a new bug. I've seen similar ish issues before anyways.

Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.