Open Bug 1148757 Opened 10 years ago Updated 2 years ago

Segfault around nsAppShell::ProcessNextNativeEvent

Categories

(Core :: Widget: Gtk, defect, P3)

Product:
Core
Component:
Widget: Gtk
Version:
31 Branch
Platform:
x86
Linux
Type:
defect

Tracking

()

Tracking Flags:
Tracking Status
firefox49 --- affected
firefox-esr45 --- affected
firefox50 --- affected

People

(Reporter: paulepanter, Unassigned)

References

Details

(Keywords: crash, Whiteboard: tpi:+)

Crash Data

Attachments

(1 file)

20150327--iceweasel-sigsegv--backtrace--taabtf.txt
122.07 KB, text/plain
Details
User Agent: Mozilla/5.0 (X11; Linux i686) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.76 Safari/537.36 Steps to reproduce: See thread 1. Entering some values into a text field. Actual results: The program terminated with a segmentation fault. Expected results: It should not have crashed and told the user, if something was up.
Can you reproduce it with a Firefox build from Mozilla, of a recent version or Beta/Aurora/Nightly?
Severity: normal → critical
Component: Untriaged → Widget: Gtk
Flags: needinfo?(paulepanter)
Keywords: crash
Product: Firefox → Core
(In reply to [:Aleksej] from comment #1) > Can you reproduce it with a Firefox build from Mozilla, of a recent version > or Beta/Aurora/Nightly? Sorry, I do not know as I do not know how to reproduce this. It just happened once and, as the core dump files are saved on my system, I reported the issue. Unfortunately, it looks like the backtrace is all there is.
Paul, have you seen the crash since April?
Whiteboard: [closeme 2015-10-20]
Wayne, no I have not seen the crash since then. I am unable to reproduce it with Iceweasel 38.1.0esr-3. Unfortunately, I am unable to tell when or how it was fixed, as I used Google Chromium since April. I am not setting the status to *Resolved* as there is no reason *fixed in a later version* or so.
(stacktrace indicates iceweasel 31) Thanks for testing the newer version. I agree we can't declare this fixed or worksforme. But without steps to reproduce or a history of repetition it also doesn't seem worth keeping open. Can we call it incomplete for now?
Crash Signature: [@ nsAppShell::ProcessNextNativeEvent]
Whiteboard: [closeme 2015-10-20]
Version: 35 Branch → 31 Branch
Sure, please do that. Unfortunately I don’t have *incomplete* as an option in the selection box for *resolved*.
Flags: needinfo?(paulepanter)
This is very low volume, but still present on release. Interestingly, it has never appeared on dev channels.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: -- → P3
Whiteboard: tpi:+
Crash volume for signature 'nsAppShell::ProcessNextNativeEvent': - nightly (version 52): 0 crashes from 2016-09-19. - aurora (version 51): 0 crashes from 2016-09-19. - beta (version 50): 5 crashes from 2016-09-20. - release (version 49): 85 crashes from 2016-09-05. - esr (version 45): 216 crashes from 2016-06-01. Crash volume on the last weeks (Week N is from 10-03 to 10-09): W. N-1 W. N-2 - nightly 0 0 - aurora 0 0 - beta 5 0 - release 56 29 - esr 0 0 Affected platform: Windows Crash rank on the last 7 days: Browser Content Plugin - nightly - aurora - beta #2387 - release #755 - esr
status-firefox49: --- → affected
status-firefox50: --- → affected
status-firefox-esr45: --- → affected
QA Whiteboard: qa-not-actionable
See Also: → 1719741

Since the crash volume is low (less than 5 per week), the severity is downgraded to S3. Feel free to change it back if you think the bug is still critical.

For more information, please visit auto_nag documentation.

Severity: critical → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: