Pomoc pśepytaś

Glědajśo se wobšudy pomocy. Njenapominajomy was nigda, telefonowy numer zawołaś, SMS pósłaś abo wósobinske informacije pśeraźiś. Pšosym dajśo suspektnu aktiwitu z pomocu nastajenja „Znjewužywanje k wěsći daś“ k wěsći.

Dalšne informacije

Firefox crash several times a day EXCEPTION_ACCESS_VIOLATION_READ

  • 17 wótegrona
  • 4 maju toś ten problem
  • 7 naglědow
  • Slědne wótegrono wót truelies

more options

The error is EXCEPTION_ACCESS_VIOLATION_READ or EXCEPTION_ACCESS_VIOLATION_WRITE The report is here: https://crash-stats.mozilla.com/report/index/e0f334a0-f1bf-416d-bf8e-aa3d82150717 https://crash-stats.mozilla.com/report/index/d2dffe83-8f7d-4f89-be40-062752150714

Wondering what cause those firefox crash?

The error is EXCEPTION_ACCESS_VIOLATION_READ or EXCEPTION_ACCESS_VIOLATION_WRITE The report is here: https://crash-stats.mozilla.com/report/index/e0f334a0-f1bf-416d-bf8e-aa3d82150717 https://crash-stats.mozilla.com/report/index/d2dffe83-8f7d-4f89-be40-062752150714 Wondering what cause those firefox crash?

Wšykne wótegrona (17)

more options

Sorry to hear about the crashes and thank you for the two reports.

The latest report has a "signature" of atidxx32.dll@0x341514 which refers to the ATI/AMD graphics adapter driver software. You might want to check for updates to that software, in case there is an incompatibility with the version you have now. This article suggests safe sites to check for that: Upgrade your graphics drivers to use hardware acceleration and WebGL.

The older report has a "signature" of RtlpWaitOnCriticalSection | RtlEncodePointer | PR_Lock | sftk_FindAttribute. It seems to arise from checking the validity of an SSL certificate. I don't know why that would cause a problem, perhaps there was something very unusual about the particular certificate?

Do you have other reports on file that might help provide more information?


Meanwhile, I noticed you have a tremendous number of plugins. To remove complications, you could consider disabling all the ones you do not think you will need for the next 24-48 hours. You can do that on the Add-ons page. Either:

  • Ctrl+Shift+a
  • "3-bar" menu button (or Tools menu) > Add-ons

In the left column, click Plugins. On the right side, set the plugins you don't plan to use during that time to "Never Activate".

more options

You can also do a malware check with several malware scanning programs on the Windows computer. Please scan with all programs because each program detects different malware. All these programs have free versions.

Make sure that you update each program to get the latest version of their databases before doing a scan.

You can also do a check for a rootkit infection with TDSSKiller.

See also:

more options

jscher2000 said

Sorry to hear about the crashes and thank you for the two reports. The latest report has a "signature" of atidxx32.dll@0x341514 which refers to the ATI/AMD graphics adapter driver software. You might want to check for updates to that software, in case there is an incompatibility with the version you have now. This article suggests safe sites to check for that: Upgrade your graphics drivers to use hardware acceleration and WebGL. Here has other reports https://crash-stats.mozilla.com/report/index/89a41f14-1419-43eb-a874-19c872150711 https://crash-stats.mozilla.com/report/index/151a7c69-39a3-498c-a944-bd8552150711 https://crash-stats.mozilla.com/report/index/0768c0ca-5128-442b-a1c8-bc4dd2150708 The older report has a "signature" of RtlpWaitOnCriticalSection | RtlEncodePointer | PR_Lock | sftk_FindAttribute. It seems to arise from checking the validity of an SSL certificate. I don't know why that would cause a problem, perhaps there was something very unusual about the particular certificate? Do you have other reports on file that might help provide more information?

Meanwhile, I noticed you have a tremendous number of plugins. To remove complications, you could consider disabling all the ones you do not think you will need for the next 24-48 hours. You can do that on the Add-ons page. Either:

  • Ctrl+Shift+a
  • "3-bar" menu button (or Tools menu) > Add-ons

In the left column, click Plugins. On the right side, set the plugins you don't plan to use during that time to "Never Activate".

more options

Here is the new report just happened. I already checked the video driver, it's current. Disabled the "hardware accelerate" and The WebGL

https://crash-stats.mozilla.com/report/index/d765ebdd-2046-43f0-b8e2-485c42150717


This time it's EXCEPTION_ACCESS_VIOLATION_EXEC

Wót truelies změnjony

more options

The most recent reports seem to be problems with garbage collection, a process of cleaning up memory after various operations, and the JavaScript compiler. I'm not sure what causes these kinds of crashes.

Could you test in Firefox's Safe Mode? That's a standard diagnostic tool to deactivate extensions, the JavaScript compilers, and some other advanced features of Firefox. More info: Diagnose Firefox issues using Troubleshoot Mode.

If Firefox is not running: Hold down the Shift key when starting Firefox.

If Firefox is running: You can restart Firefox in Safe Mode using either:

  • "3-bar" menu button > "?" button > Restart with Add-ons Disabled
  • Help menu > Restart with Add-ons Disabled

and OK the restart.

Both scenarios: A small dialog should appear. Click "Start in Safe Mode" (not Refresh).

Any difference?

more options

You can check for recently installed suspicious or unknown extensions.


Do a malware check with several malware scanning programs on the Windows computer. Please scan with all programs because each program detects different malware. All these programs have free versions.

Make sure that you update each program to get the latest version of their databases before doing a scan.

You can also do a check for a rootkit infection with TDSSKiller.

See also:

more options

jscher2000 said

The most recent reports seem to be problems with garbage collection, a process of cleaning up memory after various operations, and the JavaScript compiler. I'm not sure what causes these kinds of crashes. Could you test in Firefox's Safe Mode? That's a standard diagnostic tool to deactivate extensions, the JavaScript compilers, and some other advanced features of Firefox. More info: Diagnose Firefox issues using Troubleshoot Mode. If Firefox is not running: Hold down the Shift key when starting Firefox. If Firefox is running: You can restart Firefox in Safe Mode using either:
  • "3-bar" menu button > "?" button > Restart with Add-ons Disabled
  • Help menu > Restart with Add-ons Disabled
and OK the restart. Both scenarios: A small dialog should appear. Click "Start in Safe Mode" (not Refresh). Any difference?

I only have two add-on are "always active". All others "Ask to active". Does "Ask to active" mean when not pop out window to ask active, then always inactive?

more options

truelies said

I only have two add-on are "always active". All others "Ask to active". Does "Ask to active" mean when not pop out window to ask active, then always inactive?

"Always Activate" means that any time a site invokes the plugin, let the site use it.

"Ask to Activate" means when a site invokes a plugin, display a notification (icon in address bar, and usually an additional form such as infobar or video placeholder) so you can decide whether the site can use the plugin.

"Never Activate" means completely turn off the plugin and hide it from sites.

The problem with "Ask to Activate" is that some plugins intended to function globally, such as password managers or security filters, do not work correctly in that mode: no user interface is generated for them and they might only half work, sometimes breaking the interface.

So for this test, I suggest disabling all the ones you don't use by setting them to "Never Activate".

more options

Here is the newest crash. I deactivated all add-ons and extensions exception the shockwave flash 18

https://crash-stats.mozilla.com/report/index/e98d24e8-e3a6-4ec8-8187-8807f2150722

It shows "Related Bugs". Does that means it's a bug of Firefox?

more options

The related bugs are selected based on having a similar crash signature. The problem is, it seems many different things can lead to a crash with this signature. I did not read the bug reports.

Did you try Firefox's Safe Mode?

more options

jscher2000 said

The related bugs are selected based on having a similar crash signature. The problem is, it seems many different things can lead to a crash with this signature. I did not read the bug reports. Did you try Firefox's Safe Mode?

This one just crashed under safe mode

https://crash-stats.mozilla.com/report/index/e3a64e59-5ad4-4675-aca4-b71b72150723

more options

Hi truelies, your latest report doesn't ring any bells for me. In the past 28 days, it has been reported mostly on Android builds and only a few times on Windows. That's unusual and puzzling. But it seems that in Safe Mode, you are not getting the "garbage collection" crashes you were getting in normal mode.

Were you able to perform the malware scans to check for possible issues there?

more options

https://crash-stats.mozilla.com/report/index/74b059ac-70e5-4572-b58e-e9e5a2150728

This crash happens each time I tried to use ctrl+v to paste in firefox.

more options

Hi truelies, were you pasting into a form on a web page, or into something like the address bar or search bar?

Where had you copied from?

Oddly, the crash stats server doesn't show any similar clipboard-related crashes. Another rare problem.

The code where Firefox crashes seem routine, just accessing the Windows clipboard. Do you use any security software that might shield the clipboard from access by Firefox? Or any spyware that is watching what applications move on and off the clipboard?

more options

Here is the newest one today: https://crash-stats.mozilla.com/report/index/29b300e2-d76a-4f02-858f-f2b2b2150729

I suspect Firefox has a lot of bugs and it also allow other code insert thread into firefox.exe. A lot of crashes may be due to this.

more options

truelies said

I suspect Firefox has a lot of bugs and it also allow other code insert thread into firefox.exe. A lot of crashes may be due to this.

If other code tries to inject itself into Firefox, Windows will kill Firefox. That really isn't something that Firefox manages on its own, other than Add-ons of course.

I don't have any new suggestions based on today's crash.

What plugins do you currently have activate (either Always Activate or Ask to Activate)? You can pull a list using this page:

https://jeffersonscher.com/res/plugins.html

more options

jscher2000 said

truelies said
I suspect Firefox has a lot of bugs and it also allow other code insert thread into firefox.exe. A lot of crashes may be due to this.

If other code tries to inject itself into Firefox, Windows will kill Firefox. That really isn't something that Firefox manages on its own, other than Add-ons of course.

I don't have any new suggestions based on today's crash.

What plugins do you currently have activate (either Always Activate or Ask to Activate)? You can pull a list using this page:

https://jeffersonscher.com/res/plugins.html

  • Name (Version): Adobe Acrobat (11.0.0.379)
    Description: Adobe PDF Plug-In For Firefox and Netscape 11.0.0
    File name: nppdf32.dll
  • Name (Version): BaiduYunGuanjia Application (5.3.1.3)
    Description: YunWebDetect
    File name: npyunwebdetect.dll
  • Name (Version): Shockwave Flash (18.0.0.209)
    Description: Shockwave Flash 18.0 r0
    File name: NPSWF32_18_0_0_209.dll