X
Thinta lapha ukuze uye kuveshini yamakhalekhukhwini kusayithi.

Isithangami Sabeseki

Lolu chungechunge lwabekwa kunqolobane. Uyacelwa ubuze umbuzo omusha uma udinga usizo.

Often crash in plugin-container.exe; FF ver. 42.0

Kuphostiwe

Extremely often crash on INT3 in plugin-container.exe at offset 0x00B8ED50: 00B8ED41 push eax 00B8ED42 push 0B9705Ch 00B8ED47 call dword ptr ds:[0B961C0h] 00B8ED4D add esp,10h 00B8ED50 int 3 ; <== it's a crash point. After this crash LoadLibrary() and LoadLibraryEx() APIs (all variants - Unicode/MBCS and single char) stop normal operation until reboot, xul.dll remains locked by unknown process. As the result, Crash reporter can neither send the crash report with data collected nor add user's comment to it. Further transmission of crash report is available only via about:crashes page after system reboot because a lot of other applications (including FF) can't be started. Graphical attributes of other opened windows belong to other applications and texts in windows' headers look spoiled. Contents of all other CHtmlView-derived windows belong to other applications (even started before this crash) becomes empty. After reboot and until next FF crash all normally works. This crash happens in -safe-mode too, FF clearance doesn't helpful. Step-by-step backout of FF ver. from 42.0 to 33.1.1 has reduced fault frequency but not removed it at all. Fault may occure on attempt of open some Web page and may not occure on the same page next time after reboot, so, it looks like cumulative and/or garbage-in-constructor problem...

Extremely often crash on INT3 in plugin-container.exe at offset 0x00B8ED50: 00B8ED41 push eax 00B8ED42 push 0B9705Ch 00B8ED47 call dword ptr ds:[0B961C0h] 00B8ED4D add esp,10h 00B8ED50 int 3 ; <== it's a crash point. After this crash LoadLibrary() and LoadLibraryEx() APIs (all variants - Unicode/MBCS and single char) stop normal operation until reboot, xul.dll remains locked by unknown process. As the result, Crash reporter can neither send the crash report with data collected nor add user's comment to it. Further transmission of crash report is available only via about:crashes page after system reboot because a lot of other applications (including FF) can't be started. Graphical attributes of other opened windows belong to other applications and texts in windows' headers look spoiled. Contents of all other CHtmlView-derived windows belong to other applications (even started before this crash) becomes empty. After reboot and until next FF crash all normally works. This crash happens in -safe-mode too, FF clearance doesn't helpful. Step-by-step backout of FF ver. from 42.0 to 33.1.1 has reduced fault frequency but not removed it at all. Fault may occure on attempt of open some Web page and may not occure on the same page next time after reboot, so, it looks like cumulative and/or garbage-in-constructor problem...

Eminye Imininingwane Yohlelo

Fakela amapulagi

  • Adobe PDF Plug-In For Firefox and Netscape 11.0.8
  • Google Update
  • AlterGeo browser helper object
  • Next Generation Java Plug-in 11.65.2 for Mozilla browsers
  • DRM Netscape Network Object
  • DRM Store Netscape Plugin
  • Picasa plugin
  • Shockwave Flash 19.0 r0
  • Npdsplay dll
  • Windows Presentation Foundation (WPF) plug-in for Mozilla browsers

Isisebenziso

  • I-ejenti Engumsebenzisi: Mozilla/5.0 (Windows NT 5.1; rv:42.0) Gecko/20100101 Firefox/42.0

Eminye Imininingwane

FredMcD
  • Top 10 Contributor
4259 izisombululo 59628 izimpendulo
Kuphostiwe

Start your Computer in safe mode with networking. Then start Firefox. Try Safe web sites. Is the problem still there?

Starting The Computer In Safe Mode;
Free Online Encyclopedia

Start your '''Computer''' in safe mode with networking. Then start Firefox. Try '''Safe''' web sites. Is the problem still there? '''[http://encyclopedia2.thefreedictionary.com/Linux+Safe+Mode Starting The Computer In Safe Mode;<br>Free Online Encyclopedia]'''