Increasing DOM Nodes after adding and removing an embed element for PPAPI
Reported by
scheuerm...@barco.com,
Sep 20
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:61.0) Gecko/20100101 Firefox/61.0 Steps to reproduce the problem: 1. Take the graphics_2d example from pepper_49 2. Exchange the common.js file with the uploaded file 3. Run the example 4. Open the development tools 5. Open More tools -> Performance monitor 6. Press 'Hide' button in the web page 7. Run 'Collect garbage' 8. write down the number of DOM Nodes 9. Press 'Show' button 10. Press 'Hide' button What is the expected behavior? The nomber of DOM Nodes should be the same as before showing and removing the PPAPI plugin. What went wrong? For each show/hide cycle 3 more DOM Nodes are used. Did this work before? N/A Does this work in other browsers? N/A Chrome version: 69.0.3497.100 Channel: stable OS Version: Debian 8 Flash Version:
,
Oct 26
Tried testing the issue on reported chrome version #69.0.3497.100 using Ubuntu 17.10(as there is no Debian OS available at TE end) by following below steps. Steps: ===== 1.Launched chrome. 2.Downloaded and extracted the "graphics_2d.tar.gz " file. 3.Opened "index.html" and navigated to devtools->performance->performance monitor. 4.Clicked on the hide button and ran Collect garbage. 5.Observed the DOM nodes by clicking show and hide buttons. 6.Observed that for each cycle the DOM nodes are increasing and decreasing(the difference between them is greater than 3). Attached screencast for reference. @reporter: Could you please review attached screencast and let us know if that is the issue you are pointing to. Requesting you to confirm if the issue is specific to Debian OS. Thanks.!
,
Nov 9
Yes, I can confirm that this is the issue I'm pointing to. This issue is not specific to Debian OS. I can reproduce it also on Windows.
,
Nov 9
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 13
Able to reproduce the issue on reported chrome version #69.0.3497.100 , latest stable #70.0.3538.102 and latest chrome #72.0.3608.0 using Mac OS 10.13.6 , Ubuntu 17.10 and Windows 10 by following steps as per comment#0. The behavior is seen from M-64(from where the performance monitor has been introduced). This is non regression issue hence marking it as untraiged and requesting someone from dev team to look into the issue. Thanks.,!
,
Nov 13
Not a DevTools issue, DevTools is merely pointing at a leak. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by susan.boorgula@chromium.org
, Sep 20