[dep, 13Jan2003]

  The browser side of the java plugin will call plugin_error, which in
  turn calls exit(2), for all manner of problems. While sometimes it
  is in response to situations which could only be caused by a sick
  browser or plugin (in which case we should really be dumping core),
  and some reflect a legitimate fatal error, many seem to be just a
  half-hearted response to something which should cause just the plugin
  to fail but not the entire browser.
  
  For example, many people have been encountering bugs recently which
  involve the jvm process crashing. Unfortunately, the plugin's
  reaction apparently is to call plugin_error, resulting in this
  message:
  
  > INTERNAL ERROR on Browser End: Pipe closed during read? State may be corrupt
  > System error?:: Resource temporarily unavailable

  and a dead mozilla, as well.
  
  Curiously, in several places we attempt to clean up after a call to
  plugin_error, despite its fatal nature.