Frequent crashes
Since a few day my FF crashes frequently. It seems to happen when I type in the adressbar or in when in google tying a search. It seems that this happens when a dropdownlist with suggestions is opened when I am typing. I use FF 47.0 32-bit on Win7-64
Currently it mkes using FF almost impossible to me.
Gekozen oplossing
It's been a few days since I reverted layers.offmainthreadcomposition.enabled to true. I have seen no more crashes, so this seems a goor workaround for this issue.
Dit antwoord in context lezen 👍 0Alle antwoorden (8)
Start Firefox in Safe Mode {web Link} by holding down the <Shift>
(Mac=Options) key, and then starting Firefox.
A small dialog should appear. Click Start In Safe Mode (not Refresh).
Is the problem still there?
While still in Safe Mode,
In the address bar, type about:crashes<enter>. Note: If any reports do not have BP in front of the numbers/letters, click it to submit them.
The crash report is several pages of data. We need the report numbers to see the whole report.
Using your mouse, mark the most resent 7 - 10 crash reports, and copy them. Now go to the reply box below and paste them in.
Security notice: Update all of your Adobe programs
FredMcD said
Start Firefox in Safe Mode {web Link} by holding down the <Shift>
(Mac=Options) key, and then starting Firefox. A small dialog should appear. Click Start In Safe Mode (not Refresh). Is the problem still there?
Yes, it makes no difference.
FredMcD said
While still in Safe Mode, In the address bar, type about:crashes<enter>. ... We need the report numbers to see the whole report.
bp-286e93cb-72d0-47b0-b2e2-9f9972160728 28-7-2016 20:03 bp-7ca1b100-166d-406c-91b0-5e4fd2160728 28-7-2016 20:00 bp-c4fe7701-e9db-42d2-a7e4-6ded12160728 28-7-2016 17:28 bp-5826b03f-7ce3-4ba0-a6c2-6efb02160728 28-7-2016 17:26 bp-4b84078d-bbdf-4494-844f-422082160728 28-7-2016 17:26 bp-ee99a0da-2a79-4764-8a0a-992a02160727 27-7-2016 20:03 bp-40a8d991-6042-45cb-8401-51f8f2160727 27-7-2016 20:02 bp-2aa72114-d7b2-447c-98f7-d54bc2160727 27-7-2016 20:02
FredMcD said
Security notice: Update all of your Adobe programs
Will do. Currently they are all set to "ask to activate".
Bart
bp-286e93cb-72d0-47b0-b2e2-9f9972160728 bp-7ca1b100-166d-406c-91b0-5e4fd2160728 bp-c4fe7701-e9db-42d2-a7e4-6ded12160728 bp-5826b03f-7ce3-4ba0-a6c2-6efb02160728
Signature: mozilla::layers::LayerTransactionParent::AllocPTextureParent
atidxx32.dll = Advanced Micro Devices = Check this link;
http://support.amd.com/en-us/download/desktop?os=Windows+7+-+64
This is for Sumo's Related Bugs 1279521 NEW --- Crash in mozilla::layers::LayerTransactionParent::AllocPTextureParent
FredMcD said
atidxx32.dll = Advanced Micro Devices = Check this link;
http://support.amd.com/en-us/download/desktop?os=Windows+7+-+64
Follwed the link and updated the drivers for my Radeon. Still crashes.
bp-aa2ef469-c849-4589-8716-2806c2160729 29-7-2016 20:09 I see there are now 3 "missing symbol" errors (again in atidxx32.dll (see the new version), but now also in atidxx32.dll and msmpeg2vdec.dll), where there was just 1 before. Not really an improvement I guess?
Unfortunately the new drivers also makes my computer very slow (startup time is now 5 minutes) and most applications including FF became sluggish.
Bart
Bewerkt door bartjunk64 op
I noticed that when I logged in as adifferent user FF did not crash. Then I remembered that about 1 year ago I had a problem with FF: https://support.mozilla.org/en-US/questions/1030862
I fixed that by setting layers.offmainthreadcomposition.enabled to false in about:config.
The FF profile of the other user did not have this modification.
I reverted layers.offmainthreadcomposition.enabled to true and in a short test I could not provoke the crash (did the same things as in the first post of this thread).
I will report after a few more day wether the crash really has gone.
Mind you: even if this does resolve my issue, IMO it still is a bug.
Bart
Good luck.
Gekozen oplossing
It's been a few days since I reverted layers.offmainthreadcomposition.enabled to true. I have seen no more crashes, so this seems a goor workaround for this issue.
Good to hear. Well done.