Closed Bug 1373918 Opened 7 years ago Closed 7 years ago

Nightly is crashing at close

Categories

(Core :: Graphics: Layers, defect, P3)

56 Branch
defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: perfectswing, Unassigned, NeedInfo)

References

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:56.0) Gecko/20100101 Firefox/56.0 Build ID: 20170616030207 Steps to reproduce: Closed the Nightly Browser Actual results: Windows popup says nightly has stopped working and to close program. firefox was still running in my task manager even after I chose to close to program from the popup. I had simillar issue recently after appempting a restart update it wouldnt update. if i attempt to relaunch firefox without stoopping the process in the task manager it will not load the nightly program Expected results: should have just closed
Summary: https://www876.playercdn.net/86/0/TVQ_z_NtiISpChkdzIjIxQ/1497776067/170616/728FGNICW7QEO8O31XJYF.mp4 → FireFox Nightly is crashing at close
Is it reproducible every time you close Nightly? If yes, could you test with a fresh profile: https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles
Flags: needinfo?(perfectswing)
Summary: FireFox Nightly is crashing at close → Nightly is crashing at close
Yes it happens at each close. Now after yesterdays update of nightly it continues to have the close program issue but will now reload after the physical close but shows multiply firefox.exe in taskmanager (5 at this moment) I will try to see with new profile if continues and report back also this is what the windows popup tells me Problem signature: Problem Event Name: APPCRASH Application Name: firefox.exe Application Version: 56.0.0.6376 Application Timestamp: 5943bd07 Fault Module Name: StackHash_3c7f Fault Module Version: 0.0.0.0 Fault Module Timestamp: 00000000 Exception Code: c0000005 Exception Offset: 000000000008075c OS Version: 6.1.7601.2.1.0.256.1 Locale ID: 1033 Additional Information 1: 3c7f Additional Information 2: 3c7f0d9d51012597583a807f5364f2c6 Additional Information 3: baee Additional Information 4: baeeab1f5c256281132fb605315855f6
Flags: needinfo?(perfectswing)
I opened a fresh new profile and it happened with that profile aswell.
(In reply to Loic from comment #1) > Is it reproducible every time you close Nightly? > If yes, could you test with a fresh profile: > https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove- > firefox-profiles Yes it happens at each close. Now after yesterdays update of nightly it continues to have the close program issue but will now reload after the physical close but shows multiply firefox.exe in taskmanager (5 at this moment) I will try to see with new profile if continues and report back also this is what the windows popup tells me Problem signature: Problem Event Name: APPCRASH Application Name: firefox.exe Application Version: 56.0.0.6376 Application Timestamp: 5943bd07 Fault Module Name: StackHash_3c7f Fault Module Version: 0.0.0.0 Fault Module Timestamp: 00000000 Exception Code: c0000005 Exception Offset: 000000000008075c OS Version: 6.1.7601.2.1.0.256.1 Locale ID: 1033 Additional Information 1: 3c7f Additional Information 2: 3c7f0d9d51012597583a807f5364f2c6 Additional Information 3: baee Additional Information 4: baeeab1f5c256281132fb605315855f6 Update: I opened a fresh new profile and it happened with that profile aswell. Update: Now bug will not allow updae to happen and will not relaunch without being stopped in tskmanager
Update: Im new to nightly so sorry if i'm not following predures properly, i notice from the Firefox health page that i've had 2 crashes since refresh and 3 in total since install, not sure if this info helps but hope so, like nightly for its speed so hope we can fi this ... or perhaps i should do a total re-install of nightly and see if it rehappens ??? Firefox 56.0a1 Crash Report [@ IPCError-browser | ShutDownKill ] 1 day ago https://crash-stats.mozilla.com/report/index/9e9477df-c40f-4b4f-9f2e-60b000170616 Firefox 56.0a1 Crash Report [@ IPCError-browser | ShutDownKill ] 4 hours ago https://crash-stats.mozilla.com/report/index/109caa36-3ae9-41b5-be1f-7e5060170617 Firefox 56.0a1 Crash Report [@ mozilla::layers::CompositorBridgeParent::InitSameProcess ] 4 hours ago https://crash-stats.mozilla.com/report/index/2535c570-dd39-474f-88d3-3c7d70170617
Component: Untriaged → Graphics: Layers
Product: Firefox → Core
Your issue could be a duplicateof bug 1373540 according to the 3rd crash report you provided.
Andrew, could you confirm if it's a duplicate of your issue and resolve accordingly?
Flags: needinfo?(aosmond)
I think this bug might be a duplicate of bug 1374043. The date it started (2017-06-16), Nightly 64 bit on Windows, the 'Windows crash' information in Comment # 2 and the symptoms in Comment # 4. DJ-Leith
Depends on: 1375242
I have tried to reproduce this bug on an affected Nightly build using Windows 10 x64 and Windows 7 x86 but with no success. I followed the STR from comment 0, and in my case Firefox has stopped running in task manager after I choose to close the program. (using the pop up menu or ALT + F4). ... > I had simillar issue recently after appempting a restart > update it wouldnt update. if i attempt to relaunch firefox without stoopping > the process in the task manager it will not load the nightly program Unfortunately I was not able to reproduce this neither, the Nightly updates worked as expected on my machines. Given the fact that I was not able to reproduce any of the symptoms mentioned in comment 0, perfectswing@hotmail.com could you please help us verifying this bug on latest Nightly 56.0a1 so we can close this issue? Thanks!
Flags: needinfo?(perfectswing)
The crashes with the signature [@ mozilla::layers::CompositorBridgeParent::InitSameProcess ] are certainly fixed (in the end) by bug 1377869 and bug 1382644. Can't comment on the others.
Flags: needinfo?(aosmond)
Let's reopen if there are still crashes with the latest nightlies. Perhaps it's related to bug 1389021.
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Priority: -- → P3
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.