Have you tried running in Firefox's Safe Mode? In addition to deactivating extensions (which sounds as though it is not necessary) it also turns off hardware acceleration of graphics and the JavaScript just-in-time compilers. More info: Diagnose Firefox issues using Troubleshoot Mode.

You can restart Firefox in Safe Mode using

Help > Restart with Add-ons Disabled (Flash and other plugins still run)

In the dialog, click "Start in Safe Mode" (not Reset)

Any difference? (Not sure how soon you will know...)

Is your Firefox connected with the Sync service (either old Sync or new Sync, I haven't read up much on the changes)?

You can also check for corrupted and duplicate fonts and other font issues:

• http://www.thexlab.com/faqs/multipleappsquit.html - Font Book 2.0 Help: Checking for damaged fonts
• http://www.creativetechs.com/iq/garbled_fonts_troubleshooting_guide.html

Thanks for the responses.

Have you tried running in Firefox's Safe Mode?

Just to be sure, I've been running in safe mode for about 30-40 min, and just experienced the same crash unfortunately. Here is the crash report of this crash while running in safe mode: bp-08d629fd-bf32-4f93-946d-14da62140317

I am not using the Sync service at all.

You can also check for corrupted and duplicate fonts and other font issues

Thanks for those 2 resources. All fonts appear to be in working order. I'm fairly certain that no additional fonts have ever been installed onto this computer.

Still having major problems with this... I'm lucky to have firefox stay alive for more than 10 minutes.. I have 13 crash reports from today (and I'm pretty sure that i did not submit a report every time it crashed).

As mentioned earlier, this is a guest VM of OSX 10.9.2 running on ESXI 5.5.0. I have tried safe mode, fully re-installing firefox, and also installing a fresh OS to a new VM. I've tried configuring various VM cpu, ram, etc settings to no improvement.

I'm fairly certain that the root of this problem is related to being a VM, but unsure of where to go from here. As far as I can tell, there is no consistent indicator thoughout my crash reports.. but perhaps someone who understands them better than I can see something going on?

Any help would be appreciated.

Crash reports:

bp-29b93a18-4866-4ad1-8600-3052a2140325 bp-e96be715-92ac-4140-858f-7421a2140324 bp-1b4a6d29-aafd-431c-83aa-e39142140324 bp-a8d00624-8f72-4f8d-bfdd-acb432140324 bp-4d5cfc80-5854-4004-8905-097b92140324 bp-1903fc92-bb4e-4578-a395-63bac2140324 bp-235e1e86-ca7c-484c-8c6d-0809e2140324 bp-faa9e6e5-97d0-461b-bf4a-91d6d2140324 bp-1db0c5ca-1035-4f03-bfcb-8aa5c2140324 bp-96c99d8b-0431-4b96-bdc3-c00242140324 bp-79f0a522-8807-4db0-9965-1f3102140324 bp-e29cd13f-15f3-474c-8cf2-758c42140324 bp-88138700-95cd-4272-b983-5a9532140324 bp-994157d5-2489-4255-93db-550742140321 bp-489819f7-bf0c-46e6-a18b-395442140320 bp-e4604e5f-d00f-46f2-a377-d52332140320 bp-384b47f9-f4a6-4d79-a221-7c1832140320 bp-7731b587-3a5c-4d10-865a-d5c732140319 bp-e7788814-b776-495b-86f2-dc4c82140319 bp-ba54a932-2c67-4c1b-97bb-d0dda2140319 bp-c97f4c9f-8239-4039-929f-8b3492140319 bp-e58ff90f-482c-4922-aefc-570cc2140319 bp-3dfeead1-5f4d-4373-88f5-ae4b22140319 bp-a4966ca9-15b9-4844-96de-a622b2140319 bp-a5c09006-9872-437f-b472-9715f2140319

Some of our users are experiencing similiar if not the same problems. The difference is that we are using Win 7 64bit on ESxi 5.2 and the latest esr 24.5.0.

The crashes most frequently occure when the user searches a location on maps.google.com or openstreetmap.org. Shortly after the search when the map zooms in to show the result Firefox crashes and the user is send to the login window but no session on VMware is lost.

The latest crash report after a crash using maps.google.com is 17f2ed80-5265-4d34-a3e1-31bac2140625

Other users reported that they only need to search pictures with google and FF crashes.

I tried to reproduce the crash on two other virtual machines but so far haven't had any luck. Generally it seems that the error appears and disappears randomly.

Hi mav_hhu, are there crash reports that have information about the crashing thread? the ones that say EMPTY generally don't have enough information to perform any kind of diagnosis.

I could take a look at previous crash reports if any of them isn't empty. The problem would be to identify if the old crash reports are related to the described problem or caused by something else.