X
Tap here to go to the mobile version of the site.

منتدى الدعم

Firefox 25.0.1 & Windows Server 2003 Entreprise SP2 compatible ?

Posted

At exit Firefox crash with a memory error that can't be read by an instruction

At exit Firefox crash with a memory error that can't be read by an instruction

Additional System Details

Installed Plug-ins

  • Citrix offline plug-in Mozilla Plug-in (Win32)
  • Adobe PDF Plug-In For Firefox and Netscape
  • Windows Presentation Foundation (WPF) plug-in for Mozilla browsers

Application

  • Firefox 25.0.1
  • User Agent: Mozilla/5.0 (Windows NT 5.2; rv:25.0) Gecko/20100101 Firefox/25.0
  • Support URL: https://support.mozilla.org/1/firefox/25.0.1/WINNT/fr/

Extensions

  • IE Tab + 2.04.20110724 (coralietab@mozdev.org)
  • Troubleshooter 1.1a (troubleshooter@mozilla.org)
  • Java Quick Starter 1.0 (jqs@sun.com) (Inactive)
  • Microsoft .NET Framework Assistant 0.0.0 ({20a82645-c095-46ed-80e3-08825760534b}) (Inactive)

Javascript

  • incrementalGCEnabled: True

Graphics

  • adapterDescription:
  • adapterDescription2:
  • adapterDeviceID: 0x0000
  • adapterDeviceID2:
  • adapterDrivers: RDPDD
  • adapterDrivers2:
  • adapterRAM: Unknown
  • adapterRAM2:
  • adapterVendorID: 0x0000
  • adapterVendorID2:
  • direct2DEnabled: False
  • direct2DEnabledMessage: [u'blockedGfxCard']
  • directWriteEnabled: False
  • directWriteVersion: 0.0.0.0
  • driverDate:
  • driverDate2:
  • driverVersion:
  • driverVersion2:
  • info: {u'AzureCanvasBackend': u'skia', u'AzureFallbackCanvasBackend': u'cairo', u'AzureContentBackend': u'none', u'AzureSkiaAccelerated': 0}
  • isGPU2Active: False
  • numAcceleratedWindows: 0
  • numAcceleratedWindowsMessage: [u'blockedGfxCard']
  • numTotalWindows: 1
  • webglRendererMessage: [u'blockedGfxCard']
  • windowLayerManagerRemote: False
  • windowLayerManagerType: Basic

Modified Preferences

  • browser.cache.disk.capacity: 358400
  • browser.cache.disk.smart_size.first_run: False
  • browser.cache.disk.smart_size.use_old_max: False
  • browser.cache.disk.smart_size_cached_value: 358400
  • browser.link.open_newwindow: 2
  • browser.places.smartBookmarksVersion: 4
  • browser.search.update: False
  • browser.sessionstore.upgradeBackup.latestBuildID: 20131112160018
  • browser.startup.homepage_override.buildID: 20131112160018
  • browser.startup.homepage_override.mstone: 25.0.1
  • dom.ipc.plugins.enabled.npietab2.dll: True
  • dom.mozApps.used: True
  • extensions.lastAppVersion: 25.0.1
  • network.cookie.prefsMigrated: True
  • places.history.expiration.transient_current_max_pages: 104858
  • plugin.disable_full_page_plugin_for_types: application/pdf
  • plugin.importedState: True
  • privacy.sanitize.migrateFx3Prefs: True

Misc

  • User JS: No
  • Accessibility: No
John99 971 solutions 13138 answers

Hi dvigneron,
Sorry it is crashing. AFAIK it should be supported and not crashing.

I haven't specifically checked but would anticipate Win Server2003 to be Tier 1 Firefox supported, but we need crash report IDs anyhow IF this is a Firefox Crash you are reporting.
(You appear to be running 32bit Firefox on a 32 bit machine)

  • Or is this a BSOD System Crash ?
  • Why are you running the unsupported Firefox 25 ?
  • The current release is Fx26 and about to update to Fx27
  • Corporate users may be on ESR and using Fx24.2 esr

Navigate to about:crashes and provide a couple of the Crash ID strings please, they commence with bp-
see Firefox crashes - Troubleshoot, prevent and get help fixing crashes

Hi dvigneron, <br />Sorry it is crashing. AFAIK it should be supported and not crashing. I haven't specifically checked but would anticipate Win Server2003 to be Tier 1 Firefox supported, but we need crash report IDs anyhow IF this is a Firefox Crash you are reporting. <br />(You appear to be running 32bit Firefox on a 32 bit machine) *Or is this a BSOD System Crash ? *Why are you running the unsupported Firefox 25 ? *The current release is Fx26 and about to update to Fx27 * Corporate users may be on ESR and using Fx24.2 esr Navigate to about:crashes and provide a couple of the Crash ID strings please, they commence with '''bp-''' <br /> see [[Firefox crashes - Troubleshoot, prevent and get help fixing crashes]]

Helpful Reply

Hi John, Thank for you help.

I tried FF 26 and I still have a memory error at exit. But when I launch again FF and try about:crashes there is no crash recorded.

It's not a BSOD. In the Event viewer I have again : Application popup : nsAppShell:EventWindow: Firefox.exe - Erreur d'application : L'instruction à "0x61201669" emploie l'adresse mémoire "0x00000050". La mémoire ne peut pas être "read".

PS: Ps for my bad english, I'm on the over side of atlantique and it's not my native language :-) .

Hi John, Thank for you help. I tried FF 26 and I still have a memory error at exit. But when I launch again FF and try about:crashes there is no crash recorded. It's not a BSOD. In the Event viewer I have again : Application popup : nsAppShell:EventWindow: Firefox.exe - Erreur d'application : L'instruction à "0x61201669" emploie l'adresse mémoire "0x00000050". La mémoire ne peut pas être "read". PS: Ps for my bad english, I'm on the over side of atlantique and it's not my native language :-) .
John99 971 solutions 13138 answers

Sorry for not getting back to you earlier.

Working in the dark if we have no Crash ID

Windows Server 2003 needs a minimum of SP1 for Firefox compatibility so with SP2 you should be fully compatible. (Using 32 bit Firefox).

You may need to use Firefox 25 for some odd reason but if you could do a custom install of Firefox 26 that is the supported Release. It is easy to use a second version of Firefox as long as it has its own profile.

When doing this also create a new clean test profile and try to run the problem Firefox 25 install with that profile. It may work as such crashes may be related to profile problems.

Additionally

  • Windows Safe Mode
    Try Using Windows Safe Mode with networking. Does that help and either to prevent Crashes or give a Crash that has a submitted crash report.
  • Check Your RAM
    Use memtest or similar to run an overnight test on the RAM. Faulty RAM may be a cause of the problem, and a reason for the lack of Crash Reports.
    Memory issues may affect Firefox's ability to deal with submission of Crashes.
  • If not fixed we do need Crash Reports. Or failing that someone could probably work from a Windbg stack trace.


The error message in English would I expect be

Title: "nsAppShell:EventWindow: firefox.exe - Application Error" 
Message: "The instruction at "0x61201669" referenced memory at "0x00000050". The memory could not be "read".
PS: Ps for my bad english, I'm on the over side of atlantique and it's not my native language :-) . 

I am on the same side of the pond as you ;-)

Sorry for not getting back to you earlier. Working in the dark if we have no Crash ID Windows Server 2003 needs a minimum of SP1 for Firefox compatibility so with SP2 you should be fully compatible. (Using 32 bit Firefox). You may need to use Firefox 25 for some odd reason but if you could do a custom install of Firefox 26 that is the supported Release. It is easy to use a second version of Firefox as long as it has its own profile. * http://kb.mozillazine.org/Testing_pre-release_versions#Installing_multiple_versions When doing this also create a new clean test profile and try to run the problem Firefox 25 install with that profile. It may work as such crashes may be related to profile problems. * [[Use the Profile Manager to create and remove Firefox profiles#w_creating-a-profile]]'''_creating-a-profile''' Additionally *Windows Safe Mode <br />Try Using Windows Safe Mode with networking. Does that help and either to prevent Crashes or give a Crash that has a submitted crash report. * Check Your RAM <br /> Use [http://en.wikipedia.org/wiki/Memtest86 memtest] or similar to run an overnight test on the RAM. Faulty RAM may be a cause of the problem, and a reason for the lack of Crash Reports. <br />Memory issues may affect Firefox's ability to deal with submission of Crashes. * If not fixed we do need Crash Reports. Or failing that someone could probably work from a Windbg stack trace. ** see https://developer.mozilla.org/en-US/docs/How_to_get_a_stacktrace_with_WinDbg The error message in English would I expect be ''Title: "nsAppShell:EventWindow: firefox.exe - Application Error" <br /> Message: "The instruction at "0x61201669" referenced memory at "0x00000050". The memory could not be "read".'' ''PS: Ps for my bad english, I'm on the over side of atlantique and it's not my native language :-) . '' I am on the same side of the pond as you ;-)