1368942 - container crash when browsing bbc website

Status: RESOLVED INCOMPLETE

(Core :: DOM: Security, defect, P1)

Description

[Bhasker C V]

Attachment: crash.txt

User Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:53.0) Gecko/20100101 Firefox/53.0
Build ID: 20170518070317

Steps to reproduce:

Browse websites under custom container name


Actual results:

1. All tabs opened with the custom container name closed. Other tabs are still present
2. After a few minutes of brwosing,  the custom container name is not available anymore under the new container '+' hover menu.


Expected results:

be able to browse without container crash.

Comment 1

[Kamil Jozwiak [:kjozwiak]]

Marking this as P1 as crashes are obviously never good. I'll investigate see if I can get some STR and a list of platforms that are currently affected.

Comment 2

[Christoph Kerschbaumer [:ckerschb]]

Kamil, since this is P1, can we find an assignee for this bug? Probably baku?

Comment 3

[Jonathan Kingston [:jkt] he/him]

Have you seen this Baku? I don't think I would be much help with this code at the moment as it's likely a non containerised DOM feature?

Comment 4

[Andrea Marchesini [:baku]]

It doesn't seem we _crash_ but that the container is not available from the '+' menu. Am I wrong?

If we crash, can you submit a crash report? Thanks!

Comment 5

[Bhasker C V]

Yes. I agree. The custom container name is no more available from the "+" menu. Almost all container tabs close and I get a blank page tab (non-container tab). Once this "incident"  happens, the custom container name is no more available.

Comment 6

[Bhasker C V]

I upadted the container plugin to 2.3.0 today and I see it is fairly stable. I will update this bug if I still find any issues. Until now ... things are fine.

Comment 7

[Christoph Kerschbaumer [:ckerschb]]

(In reply to Bhasker C V from comment #6)
> I upadted the container plugin to 2.3.0 today and I see it is fairly stable.
> I will update this bug if I still find any issues. Until now ... things are
> fine.

Bhasker, are you still encountering the problem? If not, I would like to close this bug.

Comment 8

[Bhasker C V]

Not anymore. Firefox is stable now. The container plugin was the culprit.