Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Avatar for Username

Search Support

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.

Learn More

This thread was archived. Please ask a new question if you need help.

Firefox crashes

  • 2 replies
  • 2 have this problem
  • 4 views
  • Last reply by guigs

lily101
lily101
more options

ID: bp-e3e3791a-e91c-4eb1-b2a5-c709a2140318 

Signature: proxy_Call

    Details
    Metadata
    Modules
    Raw Dump
    Extensions

Signature 	proxy_Call More Reports Search
UUID 	e3e3791a-e91c-4eb1-b2a5-c709a2140318
Date Processed	2014-03-18 17:21:05.838215
Uptime	504
Last Crash	844 seconds before submission
Install Age 	2692974 since version was first installed.
Install Time 	2014-02-15 13:18:04
Product 	Firefox
Version 	27.0.1
Build ID 	20140212131424
Release Channel 	release
OS 	Windows NT
OS Version 	5.1.2600 Service Pack 3
Build Architecture 	x86
Build Architecture Info 	GenuineIntel family 15 model 6 stepping 5 | 2
Crash Reason 	EXCEPTION_ACCESS_VIOLATION_READ
Crash Address 	0x8
User Comments 	
App Notes
ID: bp-e3e3791a-e91c-4eb1-b2a5-c709a2140318 <pre><nowiki>Signature: proxy_Call Details Metadata Modules Raw Dump Extensions Signature proxy_Call More Reports Search UUID e3e3791a-e91c-4eb1-b2a5-c709a2140318 Date Processed 2014-03-18 17:21:05.838215 Uptime 504 Last Crash 844 seconds before submission Install Age 2692974 since version was first installed. Install Time 2014-02-15 13:18:04 Product Firefox Version 27.0.1 Build ID 20140212131424 Release Channel release OS Windows NT OS Version 5.1.2600 Service Pack 3 Build Architecture x86 Build Architecture Info GenuineIntel family 15 model 6 stepping 5 | 2 Crash Reason EXCEPTION_ACCESS_VIOLATION_READ Crash Address 0x8 User Comments App Notes </nowiki></pre>

Modified by cor-el

All Replies (2)

Jithin Mathew
Jithin Mathew
more options

In order to be able to find the correct solution to your problem, we require some more non-personal information from you. Please do the following:

  • Click the Firefox button at the top left, then click the Help menu and select Troubleshooting Information from the submenu. If you don't have a Firefox button, click the Help menu at the top and select Troubleshooting Information from the menu.

Now, a new tab containing your troubleshooting information should open.

  • At the top of the page, you should see a button that says "Copy text to clipboard". Click it.
  • Now, go back to your forum post and click inside the reply box. Press Ctrl+V to paste all the information you copied into the forum post.

If you need further information about the Troubleshooting information page, please read the article Use the Troubleshooting Information page to help fix Firefox issues.

Thanks in advance for your help!

guigs
guigs
more options

Hey the troubleshooting information would help from the computer this crash came from though it has been added to the question.

Just looking at the crash report though most of the computers that are reporting this crash (there are only about 19 reported reports) they all are windows machines with a proxy error. And they all have this add on %7B972ce4c6-7e08-4474-a285-3208198ce6fd%7D:27.0.1 but I could not find this. The crash reports in Google that have this signature report that its a particular website they visit.

If you have a proxy on the network Server Not Found - Troubleshoot connection problems How to let Firefox use the internet on your Windows computer for the site that you can pinpoint consistently crashing for. Configure your network preferences in the Options > Advanced >Network tab and make sure this matches the computer's network configuration.

What were you doing before it crashed? was it a specific website? If this also continues in Safe Mode, you can rule out it being an add on interfering as well.

The crash address is the backspace character, but again I do not know how relevant this is.