Closed Bug 1169831 Opened 10 years ago Closed 4 years ago

crash in OOM | large | NS_ABORT_OOM(unsigned int) | nsAString_internal::SetCapacity(unsigned int) when taking screenshots in responsive UI mode

Categories

(DevTools :: Responsive Design Mode, defect, P2)

38 Branch
defect

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: xylamic, Unassigned)

References

()

Details

(Keywords: crash, csectype-oom, perf)

Crash Data

User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Firefox/38.0 Build ID: 20150513174244 Steps to reproduce: 1) Open responsive UI mode 2) Switch to a custom resolution (eg: 3296x2536) 3) Take screenshots (MUCH slower than it used to be last release) 4) Continue taking screenshots 5) Around the 10th screenshot, Firefox will crash. Actual results: Slow, then crash. Expected results: Would like the same speed as the previous release with no crashing.
Please post the information detailed in the following article. https://developer.mozilla.org/en-US/docs/How_to_get_a_stacktrace_for_a_bug_report
Component: Untriaged → Developer Tools: Responsive Mode
Flags: needinfo?(xylamic)
Keywords: crash, perf
Thank you for the update.
Severity: normal → critical
Crash Signature: [@ OOM | large | NS_ABORT_OOM(unsigned int) | nsAString_internal::SetCapacity(unsigned int) ]
Keywords: csectype-oom
Summary: Firefox slow and crashing when taking screenshots in responsive UI mode → crash in OOM | large | NS_ABORT_OOM(unsigned int) | nsAString_internal::SetCapacity(unsigned int) when taking screenshots in responsive UI mode
Crash Signature: [@ OOM | large | NS_ABORT_OOM(unsigned int) | nsAString_internal::SetCapacity(unsigned int) ] → [@ OOM | large | NS_ABORT_OOM(unsigned int) | nsAString_internal::SetCapacity(unsigned int) ] [@ OOM | large | NS_ABORT_OOM | nsAString_internal::SetCapacity ]
Product: Firefox → DevTools
Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: -- → P2

Closing because no crashes reported for 12 weeks.

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