Closed Bug 1171151 Opened 9 years ago Closed 9 years ago

Nightly crashes almost immediate after startup since Jun 2, 2015 update

Categories

(Firefox :: Untriaged, defect)

Product:
Firefox
Component:
Untriaged
Version:
41 Branch
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: kylegggut, Assigned: alessarik)

References

Details

(Keywords: crash)

Crash Data

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Firefox/38.0 Build ID: 20150525141253 Steps to reproduce: After startup almost any action will cause a crash. Opening a new tab, accessing Options, Addon, etc. Actual results: Firefox crashes and the reporting too is displayed. Expected results: Firefox shouldn't crash.
Type about:crashes in the location bar and paste some crash reports (bp-...).
Severity: normal → critical
Flags: needinfo?(kylegggut)
Keywords: crash
Does it crash if you disable e10s? When starting with a new profile? https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles
Crash Signature: [@ nsRefPtr<nsIThread>::assign_assuming_AddRef(nsIThread*) | InkCollector::Shutdown() ]
I had disabled e10s prior to this because it conflicted with too many of the plugins i used.
Does it crash when testing with a fresh profile?
This crash is happening with significant frequency on Nightly (started in builds of 2015-06-02) and is in code only added a few weeks ago in bug 1016232. Maksim, any idea what's going on here?
Flags: needinfo?(alessarik)
Does the reporter use a pen digitizer with Nightly?
Flags: needinfo?(kylegggut)
(In reply to Robert Kaiser (:kairo@mozilla.com) from comment #6) > Maksim, any idea what's going on here? Bug 1166347 enabled code in bug 1016232. I would like to get more info about repro-steps, OS, Firefox build, which was used (desktop, w64, ...)
Flags: needinfo?(alessarik)
OS = Windows 7 SP1 x64. There was a question about me using a pen digitizer. I do have a Wacom Graphire3 attached to his laptop. Not sure if that's what you mean by pen digitizer. As of today's update (41.0a1 (2015-06-04)) the problem seems to have been corrected. At least Nightly is no longer crashing soon after it starts.
Flags: needinfo?(kylegggut)
Could You please download build and test it for correct work with your environment? https://treeherder.mozilla.org/#/jobs?repo=try&revision=e4d0fcd0cafb Before testing you should enable [dom.w3c_pointer_events.enabled] at [about:config].
Blocks: 1122211, 1166347
Flags: needinfo?(kylegggut)
I enabled [dom.w3c_pointer_events.enabled] and installed the update for June 11 2015. As of this update I am again almost immediately crashing again. The following are the crash reports: bp-a69ed396-ef98-4f04-9646-4a7882150611 6/11/2015 12:47 PM bp-9a9f92b0-56bd-4a42-9c25-a6d442150611 6/11/2015 12:47 PM bp-e6715b89-0797-4525-a247-c380f2150611 6/11/2015 12:46 PM bp-948886d4-2812-406d-a7a6-90f432150611 6/11/2015 12:45 PM bp-89096af4-2e60-417e-8dde-a8bcd2150611 6/11/2015 12:42 PM Thanks.
Flags: needinfo?(kylegggut)
Crash Signature: [@ nsRefPtr<nsIThread>::assign_assuming_AddRef(nsIThread*) | InkCollector::Shutdown() ] → [@ nsRefPtr<nsIThread>::assign_assuming_AddRef(nsIThread*) | InkCollector::Shutdown() ] [@ nsRefPtr<T>::assign_assuming_AddRef(nsIThread*) | InkCollector::Shutdown() ]
Crash Signature: [@ nsRefPtr<nsIThread>::assign_assuming_AddRef(nsIThread*) | InkCollector::Shutdown() ] [@ nsRefPtr<T>::assign_assuming_AddRef(nsIThread*) | InkCollector::Shutdown() ] → [@ nsRefPtr<nsIThread>::assign_assuming_AddRef(nsIThread*) | InkCollector::Shutdown() ] [@ nsRefPtr<T>::assign_assuming_AddRef(nsIThread*) | InkCollector::Shutdown() ] [@ nsRefPtr<T>::assign_assuming_AddRef | InkCollector::Shutdown ]
(In reply to Kyle Green from comment #11) > ... and installed the update for June 11 2015... I am not interested of any updates, they will crashes until we push the solution. But we cannot push patch with solution until we check and test it. So I ask you about specific build prepared with patch. It can be downloaded from special try-server. Please, see comment 10.
Flags: needinfo?(kylegggut)
Sorry I misunderstood you. Unfortunately I do not have the experience need to downland and build this update. Do you have another suggestion? I'm happy to test it if I could somehow get the update in a different way. I'm running Windows 7 SP1 x64. Please let me know. Thanks
Flags: needinfo?(kylegggut)
(In reply to Kyle Green from comment #13) > Sorry I misunderstood you. Unfortunately I do not have the experience need > to downland and build this update. Do you have another suggestion? I'm happy > to test it if I could somehow get the update in a different way. I'm running > Windows 7 SP1 x64. Please let me know. Thanks It's very easy. You should find string "Windows XP opt" and click "B". Then you should find string "Build: x86 windowsxp win" - it is link for target folder. After it You can download "firefox-41.0a1.en-US.win32.zip" and unzip it to any folder. And that is all. So I wait results from your checking and testing.
Flags: needinfo?(kylegggut)
Following your instructions, I have been running the provided update all day without crashing. I have run the test mostly with e10s disabled because of interference with some of the add-ons I relay on. I have however run the update with e10s enabled as well. Regardless of this the update DOES NOT crash. I have NOT encountered any problems or issues. Do you know when this update will be made available via the normal nightly update process? Thanks for the great work all of you do with Firefox. It's by far the best browser out there! Keep up the GREAT work!
Flags: needinfo?(kylegggut)
(In reply to Kyle Green from comment #15) > Regardless of this the update DOES NOT crash. I have NOT encountered any problems or issues. Just for confirmation: Pointer events were enabled? Did You check it? > Do you know when this update will be made available via the normal nightly update process? I hope in nearest days. > Thanks for the great work all of you do with Firefox. It's by far the best browser out there! > Keep up the GREAT work! Thank You very much. We like Firefox. We like that Firefox is liked by people.
Flags: needinfo?(kylegggut)
Yes, absolutely Pointer events is set to true. I just went back and checked again to make sure. I look forward to getting this update for Nightly.
Flags: needinfo?(kylegggut)
(In reply to Kyle Green from comment #17) > I look forward to getting this update for Nightly. Bug 1171712 were fixed and that needed changes were pushed into m-c. So I expect that they will be available at Nightly update at nearest days. But I would like to notify that Pointer events have already prepared to turn on at Nightly again (Bug 1166347). So more testing will be better for our needs and our Firefox. Lets make the world better :-)
Assignee: nobody → alessarik
Depends on: 1171712
So Pointer Events have been enabled again at Bug 1166347. If crashes have been stoped we can close current bug.
I haven't experienced anymore crashes, even using the currently Nightly, the system has been as stable as it normally is. Thanks for addressing this issues as quickly as you did. GO FIREFOX!
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.