This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

সহায়তা খুঁজুন

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

আরও জানুন

Firefox v48 crashes on XPSP3

  • 3 উত্তরসমূহ
  • 1 এই সমস্যাটি আছে
  • 6 দেখুন
  • শেষ জবাব দ্বারা philipp

more options

Installed Firefox v48 on XPSP3. When I goto https://csc.redbrickhealth.com/ and login, Firefox crashes. On occasion if I start in Safe-Mode and login to that site it may stay up; most of the time it crashes too. I've had to back out to v45.

bp-d100c54a-321e-45d2-a3f6-212ee2160824 Mozilla Crash Reports Search

   Product: 

Select Version: Report:

Super Search Firefox 49.0b5 Crash Report [@ mozilla::Maybe<T>::emplace<T> ] Search Mozilla Support for Help ID: d100c54a-321e-45d2-a3f6-212ee2160824 Signature: mozilla::Maybe<T>::emplace<T>

   Details
   Metadata
   Modules
   Raw Dump
   Extensions

Signature mozilla::Maybe<T>::emplace<T> More Reports Search UUID d100c54a-321e-45d2-a3f6-212ee2160824 Date Processed 2016-08-24 01:37:35 Uptime 9 seconds Last Crash 78 seconds before submission (1 minute and 18 seconds) Install Age 444 seconds since version was first installed (7 minutes and 24 seconds) Install Time 2016-08-24 01:30:03 Product Firefox Release Channel beta Version 49.0b5 Build ID 20160818050015 OS Windows XP OS Version 5.1.2600 Service Pack 3 Build Architecture x86 Build Architecture Info GenuineIntel family 15 model 2 stepping 9 | 2 Adapter Vendor ID

0x10de

Adapter Device ID

0x0221

Crash Reason EXCEPTION_BREAKPOINT Crash Address 0x10817e49 User Comments Total Virtual Memory 2,147,352,576 bytes (2 GB) Available Virtual Memory 1,829,703,680 bytes (1.7 GB) Available Page File 1,853,403,136 bytes (1.73 GB) Available Physical Memory 522,981,376 bytes (498.75 MB) System Memory Use Percentage 67 EMCheckCompatibility

True

App Notes

AdapterVendorID: 0x10de, AdapterDeviceID: 0x0221, AdapterSubsysID: 213f1682, AdapterDriverVersion: 6.14.11.6218 FP(D000-L10010-W00000000-T0000) D2D1.1? D2D1.1-

Processor Notes processor_ip-172-31-37-133_1293; MozillaProcessorAlgorithm2015; skunk_classifier: reject - not a plugin hang

Bugzilla - Report this bug in Firefox Core External Software Affecting Firefox Toolkit Related Bugs

   1272963RESOLVED INCOMPLETE Crash in mozilla::Maybe<T>::emplace<T>
   1224595NEW --- crash in mozilla::Maybe<T>::emplace<T>

Crashing Thread (0) Frame Module Signature Source 0 xul.dll mozilla::Maybe<js::jit::AutoWritableJitCode>::emplace<unsigned char*&, unsigned int&>(unsigned char*&, unsigned int&) obj-firefox/dist/include/mozilla/Maybe.h:386 1 @0x3e9c156

S

Installed Firefox v48 on XPSP3. When I goto https://csc.redbrickhealth.com/ and login, Firefox crashes. On occasion if I start in Safe-Mode and login to that site it may stay up; most of the time it crashes too. I've had to back out to v45. bp-d100c54a-321e-45d2-a3f6-212ee2160824 Mozilla Crash Reports Search Product: Select Version: Report: Super Search Firefox 49.0b5 Crash Report [@ mozilla::Maybe<T>::emplace<T> ] Search Mozilla Support for Help ID: d100c54a-321e-45d2-a3f6-212ee2160824 Signature: mozilla::Maybe<T>::emplace<T> Details Metadata Modules Raw Dump Extensions Signature mozilla::Maybe<T>::emplace<T> More Reports Search UUID d100c54a-321e-45d2-a3f6-212ee2160824 Date Processed 2016-08-24 01:37:35 Uptime 9 seconds Last Crash 78 seconds before submission (1 minute and 18 seconds) Install Age 444 seconds since version was first installed (7 minutes and 24 seconds) Install Time 2016-08-24 01:30:03 Product Firefox Release Channel beta Version 49.0b5 Build ID 20160818050015 OS Windows XP OS Version 5.1.2600 Service Pack 3 Build Architecture x86 Build Architecture Info GenuineIntel family 15 model 2 stepping 9 | 2 Adapter Vendor ID 0x10de Adapter Device ID 0x0221 Crash Reason EXCEPTION_BREAKPOINT Crash Address 0x10817e49 User Comments Total Virtual Memory 2,147,352,576 bytes (2 GB) Available Virtual Memory 1,829,703,680 bytes (1.7 GB) Available Page File 1,853,403,136 bytes (1.73 GB) Available Physical Memory 522,981,376 bytes (498.75 MB) System Memory Use Percentage 67 EMCheckCompatibility True App Notes AdapterVendorID: 0x10de, AdapterDeviceID: 0x0221, AdapterSubsysID: 213f1682, AdapterDriverVersion: 6.14.11.6218 FP(D000-L10010-W00000000-T0000) D2D1.1? D2D1.1- Processor Notes processor_ip-172-31-37-133_1293; MozillaProcessorAlgorithm2015; skunk_classifier: reject - not a plugin hang Bugzilla - Report this bug in Firefox Core External Software Affecting Firefox Toolkit Related Bugs 1272963RESOLVED INCOMPLETE Crash in mozilla::Maybe<T>::emplace<T> 1224595NEW --- crash in mozilla::Maybe<T>::emplace<T> Crashing Thread (0) Frame Module Signature Source 0 xul.dll mozilla::Maybe<js::jit::AutoWritableJitCode>::emplace<unsigned char*&, unsigned int&>(unsigned char*&, unsigned int&) obj-firefox/dist/include/mozilla/Maybe.h:386 1 @0x3e9c156 S

spetragl দ্বারা পরিমিত

All Replies (3)

more options

thank you, if you can easily and reproducibly get firefox to crash on that page, it would be quite helpful if you could use the "mozregression" tool in order to test various firefox versions in order to find out when exactly the error got introduced into the browser: https://mozilla.github.io/mozregression/

it will download a series of builds asking you if they exhibit the problem each time (good/bad) and at the end it would generate a "pushlog" which is the bit that could lead us to identifying the change in the firefox code that causes this crash...

more options

Philipp,

I think I finally got it to build all the way down.

pushlog_url: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=06ab805e14b5e6d8a8a99c7846c8fde163a9e5d7&tochange=3f41d7d0f544ebd98273e39bd945c28878a47427 repo_name: mozilla-central

Does this help?

more options

hi, thanks but this range is more than a month (2015-12-15 till 2016-01-25) which is too much to get a useful result out of it. we should try to get it down to a single day...