616088 - A crashtest with a Flash plugin which can't be loaded due to DNS resolution issues makes the crashtest suite not exit cleanly

Status: RESOLVED INCOMPLETE

(Core Graveyard :: Plug-ins, defect)

Description

[(no longer active)]

Today, our crashtest suite on OS X 10.5 started failing for no good reason.

After hours of bisecting the crashtest suite, it turned out that the problem was bug 616085, namely, this network access: <http://mxr.mozilla.org/mozilla-central/source/layout/generic/crashtests/508908-1.html?force=1#23>.

The test machines could not resolve the host, and it caused Firefox not to exit cleanly at the end of the crashtest run.

While I've disabled the test for now, the underlying bug remains to be investigated and fixed.  Depending on what's going on, this may need to block 2.0, I think.

Read more about the background of the issue here: <http://groups.google.com/group/mozilla.dev.tree-management/browse_thread/thread/f11512cae9b5875d>

I should also mention that the browser was responsive, it just wouldn't quit.

Comment 1

[(no longer active)]

The effect of this over the timeout in bug 615858 should also be interesting to investigate.

Comment 2

[Johnny Stenback (:jst)]

I don't think this blocks.

Comment 3

[(no longer active)]

(In reply to comment #2)
> I don't think this blocks.

Do we have enough information yet to make that call?  We don't yet know why this happens, and whether it can happen in real browser sessions, but if it can, it means that Firefox will hang when asked to quit...

Comment 4

[Benjamin Smedberg]

Resolving old bugs which are likely not relevant any more, since NPAPI plugins are deprecated.