Firefox 17 crashes when automation testing is run. But works properly in Firefox 10. It opens many tabs while running and it crosses 50.
Hi,
When we run automation testing of our product, it works well in firefox old versions and IE. But when we run it in firefox 17 it crashes. We noticed that in firefox 10, each task in automation was opened in new windows and ran smoothly. But in firefox 17, each task opens in new tab and the number of tabs opened crosses 50 and finally crashes. We tried with various troubleshooting methods discussed in your blog. But no help.
What is the change in firefox 17 that it makes each task opened in new tabs? Or what is the setting we need to set so that each task opens in new window?
We have hundreds of test cases. This bug is a blocker for certification of firefox 17 for our product.
Thanks
Modified by vino5
All Replies (17)
Could you try with the latest version of Firefox 22.
Hi, Let me try with the new version and let you know.
BTW, there is a mistake in my question. Each task opens in new tab and not new window. Hence the no.of tabs running crosses 50.
Hello,
Try disabling graphics hardware acceleration. Since this feature was added to Firefox, it has gradually improved, but there still are a few glitches.
You might need to restart Firefox in order for this to take effect, so save all work first (e.g., mail you are composing, online documents you're editing, etc.).
Then perform these steps:
- Click the orange Firefox button at the top left, then select the "Options" button, or, if there is no Firefox button at the top, go to Tools > Options.
- In the Firefox options window click the Advanced tab, then select "General".
- In the settings list, you should find the Use hardware acceleration when available checkbox. Uncheck this checkbox.
- Now, restart Firefox and see if the problems persist.
Additionally, please check for updates for your graphics driver by following the steps mentioned in the following Knowledge base articles:
Did this fix your problems? Please report back to us!
Thank you.
Hi we have already tried this but no help :(
In order to assist you better, please follow the steps below to provide us crash ID's to help us learn more about your crash.
- Enter about:crashes in the address bar (that's where you enter your website URL) and press Enter. You should now see a list of submitted crash reports.
- Copy the 5 most recent crash ID's that you see in the crash report window and paste them into your response here.
Thank you for your help!
More information and further troubleshooting steps can be found in the Troubleshoot Firefox crashes (closing or quitting unexpectedly) article.
Okay, I will send the crash ids once the crash occurs.
bp-e94a2d2b-1b68-4c86-964b-05f612130530
This is the crash id. This was generated a month ago. Though our firefox crashes, we dint submit the crash reports. So this was the last generated crash id.
It seems as if v21.0b5 fixes this crash (v21 and above)
Removing the topcrash keyword because: 1. it no longer happens in 21.0b5 and above 2. bug 772330 comment 19
refer to: https://bugzilla.mozilla.org/show_bug.cgi?id=865701#c27
and do not comment etc. in bugzilla areas
Modified by kobe
Okay. I will ask my team to try with firefox 22. Thanks for your quick response :)
Hi,
I tried the same automation with firefox 22. Still the firefox crashed. We changed the settings and made it open in new window for every new task. But no luck. And also crash reporter dint pop up and hence couldnt submit the crash report. Also while running in firefox 10, each new window opened for task got closed and hence the crash dint occur. But here in firefox 22, the new window dint get closed and firefox hung. The crash report for firefox 17 was submitted in the previous post.
Regards, Vinoth
Can you try out Firefox 23 coming sometime (if not already) today?
Do you have the graphics display card mentioned in the bug report: AMD Radeon 6310/6320 ?
If not then the bug may not apply to your case.
Are there any extensions installed on the test machine?
Do the crashes still happen if Windows is booted in safe mode with network support?
Note that issues also be caused by gathering data for the Firefox Health Report.
Hi, We dint make any hardware changes. Also we tried automatiom in two different machine.
We removed the extensions before running.
We dint try this in windows safe mode. I will ask my team to try that.
I feel this looks like an issue from firefox side. Because we had the same automation running in firefox 10. It worked fine. Since firefox 17, the automation gets interrupted in between due to crash. My understanding is any new feature or settings added in firefox 17 might cause this issue. And this issue is a certification blocker. So the temperature is high.
Anyway I will try with windows safe mode and let you know.
Modified by vino5
The automation fails on firefox versions 17,22 and 23.
The crash reporter dint pop up sometimes. Below are the name of the files stored in firefox crash folder after crashing.
InstallTime20121106195758 - firefox17
InstallTime20130618035212 - firefox22
InstallTime20130730113002 - firefox23
Modified by vino5
HI, Any update?
What are those files whose name starting with 'InstallTime'? Why crash report was not generated by firefox 17+?
Thanks in advance
InstallTime files are not crash reports, but files that log the installation of a Firefox update.
You appear to have jumped from Firefox 17 (2012-11-06) to Firefox 22 (2013-06-18) and have missed the updates from 18 till 21.
No, we uninstalled firefox 17 completely and then installed firefox 22.