Firefox crashes
Firefox had been working perfectly, but this morning when I opened it I received the "Firefox had a problem and crashed" message. I was able to open it in safe mode, but that meant my add-ons were disabled. I make extensive use Alpheios, an "extension for reading and learning languages" (alpheios.net is their home page.) I refreshed Firefox and reinstalled The Alpheios add-ons (Basic Library, Greek tools. Latin Tools) from the Firefox add-on site. The problem reoccurred. I then uninstalled and reinstalled Firefox, refreshed it, and reinstalled the Alpheios ad-ons from the Firefox add-on site. The problem reoccurred. The refresh removed all my other add-ons and so the problem must be specific to Firefox and Alpheios. What must I do to get Firefox to let me continue using Alpheios as usual?
Chosen solution
Looks like Bug 1255888 involves a security exploit and will be inaccessible until it is fixed by Mozilla. If you had filed that Bug yourself, you may have gotten an email from Bugzilla when it is fixed; but now about all you can do is to 'watch' that Bug report to see when it becomes accessible to the public. You can't even access that Bug to vote for it and ask to "add me to CC list" to get an email notification.
My advice it to contact Alpheios via support@alpheios.net , and file a Bug report with them, giving them the Bugzilla bug number 1255888 .
Read this answer in context 👍 1All Replies (13)
Could you type about:crashes in the location bar and paste some crash links (bp-...).
Is this what you need? Report ID Date Submitted bp-b29ca27e-8256-463f-8a1f-6ca922160311 3/11/2016 12:39 PM bp-524de024-e99a-4240-8e3a-15a7a2160311 3/11/2016 12:35 PM bp-3dc34165-d8a0-45a3-bbeb-c581a2160311 3/11/2016 12:32 PM bp-13422a49-5fcd-4954-b31e-209ad2160311 3/11/2016 12:32 PM bp-54dadd44-632b-4b1e-bf1b-068252160311 3/11/2016 12:32 PM bp-fbf70fac-f9fe-4176-88e0-0f2842160311 3/11/2016 12:32 PM bp-40afe718-b671-4132-9dc3-029ed2160311 3/11/2016 12:10 PM bp-a2c29106-264a-4876-875a-f52842160311 3/11/2016 11:36 AM bp-f1c1988e-16ab-46da-9ad7-0578c2160311 3/11/2016 11:35 AM bp-2e3fc041-f8ba-4d53-8acc-a8b9f2160311 3/11/2016 11:35 AM bp-338fa4b9-0115-4ff3-8ec4-d44122160311 3/11/2016 11:35 AM bp-2a6f0fad-14ee-4d2e-b79b-86f402160311 3/11/2016 11:29 AM bp-43577e92-671f-4b2e-8ec6-2d6b12160311 3/11/2016 11:27 AM bp-ebc195fb-1503-490e-865d-ab18b2160311 3/11/2016 11:26 AM bp-4d457f75-5a3f-4a1d-b93a-fd4312160311 3/11/2016 11:25 AM bp-704746e7-86ef-49ee-aeaa-23bb12160311 3/11/2016 11:25 AM bp-43ba9e2e-a8b9-4386-9201-4d34f2160311 3/11/2016 10:51 AM bp-ba56ab57-7b1c-4f1b-bdea-3f8852160311 3/11/2016 10:50 AM bp-c3e6de51-f415-4b00-85a3-e97662160311 3/11/2016 10:50 AM bp-7132ce00-d755-4d79-96f9-af3f12160311 3/11/2016 10:50 AM bp-3ef7031c-2ed5-4266-aa75-b64fb2160311 3/11/2016 10:47 AM bp-51b9726d-aec4-4b31-8521-eb78a2160311 3/11/2016 10:44 AM bp-2ddbf76d-9584-406f-b561-384ad2160311 3/11/2016 10:29 AM bp-376dae0e-0469-492e-add3-94bf92160311
Modified by cor-el
Thanks. Does it crash only with the add-on of Alpheios?
Ok, I'm able to reproduce the crash, I'll file a bug on Bugzilla for that.
It seems so. I just refreshed Firefox, removing Alpheios, and Firefox started uneventfully.
What happens next?
RichardBeck said
What happens next?
See https://bugzilla.mozilla.org/show_bug.cgi?id=1255888 as follow-up to the issue.
I no longer have access to bug 1255888, despite having created a Bugzilla account. Will I hear from someone when the problem is solved? Thanks.
Chosen Solution
Looks like Bug 1255888 involves a security exploit and will be inaccessible until it is fixed by Mozilla. If you had filed that Bug yourself, you may have gotten an email from Bugzilla when it is fixed; but now about all you can do is to 'watch' that Bug report to see when it becomes accessible to the public. You can't even access that Bug to vote for it and ask to "add me to CC list" to get an email notification.
My advice it to contact Alpheios via support@alpheios.net , and file a Bug report with them, giving them the Bugzilla bug number 1255888 .
Access to bug 1255888 has been restricted because of security sensitive. And it's probably a dupe of bug 1222624 which is going to be fixed.
I would like to thank Oxylatium and the-edmeister for their assistance. I contacted Alpheios, who contacted me back directly and referred me to this letter, which might be of interest: http://alpheios.net/content/letter-alpheios-users. I may have to wait a while to get Alpheios back. But as the two of you were so pleasant to work with, I wanted to take a moment to thank you.
RichardBeck said
I would like to thank Oxylatium and the-edmeister for their assistance. I contacted Alpheios, who contacted me back directly and referred me to this letter, which might be of interest: http://alpheios.net/content/letter-alpheios-users. I may have to wait a while to get Alpheios back. But as the two of you were so pleasant to work with, I wanted to take a moment to thank you.
The bug is in Firefox, after Mozilla fixed it (I hope for v46), it should be OK to use these extensions.
CORRECTION: the offending bug has been backout and the fix should be in the next release 45.0.1 under the note "XSLTProcessor.importStylesheet was failing when <import> was used (1249572)"