Schlagwort-Archive: crash

Quick Fix for Firefox Bug #456705: Crash on SSL Connect

[Get only posts in English]

After updating to, Firefox crashes if the FoxyProxy extension is installed. This renders the browser virtually useless. You won’t even be able to install the update that fixes this issue once there is one, since Firefox‘ automatic update function does, of course, use SSL. Some of the links in this post also point to HTTPS URLs, so if you are reading this post using Firefox because you have this problem, read to the end but don’t click anywhere.

To fix this issue and get Firefox to work again, you’ll have to uninstall the FoxyProxy extension before accessing any HTTPS URL. If Firefox is configured to start with a blank or non-SSL page and you do not want to restore a session containing HTTPS pages, you can probably do so from within Firefox. Go to Tools -> Add-ons, select FoxyProxy in the list that opens, and uninstall. Or is disabling FoxyProxy sufficient? Please leave a comment if you tried; I didn’t.

If Firefox for some reason tries to load an HTTPS page automatically when it starts, you will have to edit your Firefox profile. On Windows, profile data are usually found under C:\Documents and Settings\<your username>\Application Data\Mozilla\Firefox\Profiles\<random name>\. Note that Documents and Settings and Application Data may be named differently in localised versions of Windows. Under MacOS X the profile is stored under /Users/<your username>/Library/Application Support/Firefox/Profiles/<random name>, and on a Unix-style system such as Linux or *BSD you will probably find the path to you profile somewhere under your home directory. If you see a recently edited file named bookmarks.html, and the file contains your bookmarks, you found the right place.

Inside the profile directory you should see a subdirectory extensions and inside, one or more subdirectory. Find the one containing FoxyProxy, it will probably be named foxyproxy@eric.h.jung. Delete this subdirectory, or better move it elswhere just in case you made a mistake.

Now start Firefox again.

See also: Ubuntu Bug #274065; FoxyProxy crashes Firefox on shutdown; Firefox Support Forum: Firefox crashes with foxyProxy 2.8.5, Bug #456705.

Update 2008-09-29: New versions of FoxyProxy are available. Installing version 2.8.6 or newer should fix the issue. The latest version is 2.8.8 now. If you haven’t updated your browser yet, it would be wise to update the extension first.

Interim Report on BA038 Accident

[Get only posts in English]

The U.K. Air Accidents Investigation Branch (AAIB) has published an Interim Report on the Accident to Boeing 777-236ER, G-YMMM at London Heathrow Airport on 17 January 2008, better known as the BA038 crash. As I mentioned before, aviation accident investigations are time-consuming. 8 months after the crash they are not finished yet, but they have an idea what the cause might have been. Their summary:

»The investigation has shown that the fuel flow to both engines was restricted; most probably due to ice within the fuel feed system. The ice is likely to have formed from water that occurred naturally in the fuel whilst the aircraft operated for a long period, with low fuel flows, in an unusually cold environment; although, G-YMMM was operated within the certified operational envelope at all times. (…)«

The report goes on discussing the issue and warns that other types of aircraft may be affected as well.

Attitude Adjustment Needed?

[Notice for our international readers]

I have no idea what went wrong today when a British Airways jet crashed short of the runway in London Heathrow. Nobody does at this point, we’ll have to wait for the results of a thorough investigation as will undoubtedly be carried out for this crash like for any other. This is the way the aviation community learns from mistakes all around the world.

So there would be not much to say about this accident, hadn’t I tripped over a statement that BBC News quotes prominently in their online coverage of the events, attributed to David Learmount, Air transport expert:

»BA pilots don’t make error of judgements of that type, especially not at the home base, let alone anywhere else«

This is not the appropriate attitude towards safety and the causes of accidents. In reality, pilot or flight crew error is the primary cause of accidents in aviation. At this point, let me repeat myself, we don’t have the slightest idea what caused this crash, but we know for sure that even BA pilots make errors of judgement, perhaps even of this particular type.

To be fair, according to my experience with the media, this sentence is one short snippet selected by a journalist out of a longer conversation. It may not entirely represent what had been said and our air transport expert may be innocent. However, in the particular way in which it appears on the BBC page, emphasized through page layout and ripped out of its possible context, it is just plain wrong.


  • The Man in a Shed points out: »It is worth speculating as to why all BA 777’s and other airline 777s haven’t been grounded given the reported total electrical failure of the aircraft. Perhaps something is known about the cause after all.« I’m afraid he might have wrong expectations about aircraft being grounded. This is not the common reaction to any incident or accident unless it is obvious that there would be a high, immediate danger in not doing so.
  • Kevin Anderson criticizes the Times‘ coverage of the events.
  • Holly of PlaneBuzz discusses the many ways in which this accident is perplexing. This is exactly why it needs to be investigated.
  • Juan Antonio Giner of Innovations in Newspapers noticed a BA ad in the middle of a news report on the accident, and has further comments on the reporting.
  • Jon, too, complains about the style of reporting and recommends that we wait for the results of the investigation.