1175677 - [e10s] 3-way WaitForMessage hang clicking on the test plugin

Status: RESOLVED WORKSFORME

(Core Graveyard :: Plug-ins, defect)

Description

[Jim Mathies [:jimm]]

Attachment: test case

Pretty sure this is a regression since I've been working with these test cases regularly for months now and this is the first I've seen of this.

STR:

1) open the test case and let the green test plugin load
2) click on the green plugin window

result: deadlock

Here's the weird thing: the content process is caught up in WaitForMessage as well which should not happen since that thread should not have an event queue that's bound to the other processes.

Comment 1

[Jim Mathies [:jimm]]

Tracy, can you reproduce this?

Comment 2

[Tracy Walker [:tracy]]

With the testcase, I get a grey plugin window with the lego piece "A plugin is needed to display this content."  Clicking on it does nothing.

Comment 3

[Jim Mathies [:jimm]]

(In reply to [:tracy] Tracy Walker - QA Mentor from comment #2)
> With the testcase, I get a grey plugin window with the lego piece "A plugin
> is needed to display this content."  Clicking on it does nothing.

You need the to get the test plugin installed. The test plugin is available in local windows builds and in our test package zips the test slaves use.

Comment 4

[Jim Mathies [:jimm]]

I did spot checks back to 01-01 and was able to reproduce so I guess this has been around for a while.

Comment 5

[Jim Mathies [:jimm]]

Note to self, if you ever copy a debug build of the test plugin over to your profile directory, remember to remove it after you're through testing.

I had a copy of the test plugin with a 45 second hang on left click installed. :)