New issue
Advanced search Search tips

Issue 919792 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug



Sign in to add a comment

Changing constructor property on Array instance doubles execution time of decryption

Reported by kl...@live.de, Jan 8

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36

Steps to reproduce the problem:
1. Go to https://plnkr.co/edit/5JT0X0whMJ6G7wXZfZNM?p=preview and run the script/test
2. Go to https://plnkr.co/edit/x8skIAMV0P7cpimL4YCS?p=preview and run the script/test
3. Compare the "time needed" that is shown on the right between (1) and (2).

What is the expected behavior?
I expect that the needed time is about the same for both test cases (1) and (2).

What went wrong?
The time needed in testcase (2) is about doubled the time needed in (1). On my computer these are about 100ms in case (1) and 200ms in case (2).

The only difference between the two scripts are the lines:
var object = [1,2,3];
object.constructor = function() {};

Where the second line is not present in testcase (1). So it seems that setting the constructor property of an instance of an array object dramatically slows down the decryption that is done in the rest of the script. I have no clue why this could be and I also think this should not be the case.

Did this work before? N/A 

Chrome version: 71.0.3578.98  Channel: stable
OS Version: 10.0
Flash Version: 

I've tried the same on a Windows 7 Virtual Machine, same error.

In current Firefox and Edge this problem does not occur.
 
Additional interesting behaviour: just removing the line
object.constructor = function() {};
and re-run the test does not solve the problem, it only helps after restarting Chrome.
Labels: Needs-Triage-M71
Cc: santhoshkumar@chromium.org
Labels: Triaged-ET Target-73 M-73 FoundIn-71 FoundIn-73 FoundIn-72 OS-Linux OS-Mac
Status: Untriaged (was: Unconfirmed)
"Able to reproduce the issue on reported chrome version # 71.0.3578.98 and latest chrome #73.0.3665.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-60. This is non regression issue hence marking it as untraiged and requesting some one from dev team to look into the issue.
Thanks"
Components: -Blink Blink>JavaScript

Comment 5 by hablich@chromium.org, Today (21 hours ago)

Components: -Blink>JavaScript Blink>JavaScript>Runtime
Owner: verwa...@chromium.org
Status: Assigned (was: Untriaged)
verwaest@, any insight?

Sign in to add a comment