Status Update
Comments
gu...@gmail.com <gu...@gmail.com> #2
[Empty comment from Monorail migration]
[Monorail components: -Platform>DevTools Blink>CSS]
[Monorail components: -Platform>DevTools Blink>CSS]
ka...@google.com <ka...@google.com> #3
Tested the issue on reported chrome version #87.0.4280.00 using Mac 10.13.6 as per the steps in https://crbug.com/chromium/1159587#c0
Steps:
---------
1. Launched chrome and opened devtools
2. Observed that able to add position and top rules.
Attached screen-cast for reference.
@Reporter: Could you please review the attached screen-cast and let us know if we missed anything from our end.
Requesting you to provide a sample URL/file that reproduce the issue, so that it would be really helpful in triaging the issue.
Thanks
Steps:
---------
1. Launched chrome and opened devtools
2. Observed that able to add position and top rules.
Attached screen-cast for reference.
@Reporter: Could you please review the attached screen-cast and let us know if we missed anything from our end.
Requesting you to provide a sample URL/file that reproduce the issue, so that it would be really helpful in triaging the issue.
Thanks
ka...@google.com <ka...@google.com> #4
Hi, no disrespect, but please forward this to developer who knows CSS and HTML. I have explained the issue perfectly.
rw...@scottlogic.com <rw...@scottlogic.com> #5
Thank you for providing more feedback. Adding the requester to the cc list.
For more details visithttps://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
For more details visit
rw...@scottlogic.com <rw...@scottlogic.com> #6
[Empty comment from Monorail migration]
[Monorail components: -Blink>CSS Platform>DevTools>Authoring]
[Monorail components: -Blink>CSS Platform>DevTools>Authoring]
pe...@google.com <pe...@google.com> #7
As per https://crbug.com/chromium/1159587#c0 , it seems to be a feature request hence marking it 'Untriaged' and requesting someone from Dev to look into it.
Thanks.!
Thanks.!
ka...@google.com <ka...@google.com> #8
This is something we’ve been thinking about. We do want to make DevTools more helpful w.r.t. “inactive” styles, i.e. declarations that are covered but still don’t have any effect due to other declarations or rules — like `left: 42px` on a statically positioned element.
rw...@scottlogic.com <rw...@scottlogic.com> #9
Making this issue about the originally reported behavior, and filing https://bugs.chromium.org/p/chromium/issues/detail?id=1178508 to track further improvements to “inactive” styles.
pe...@google.com <pe...@google.com> #10
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.
Sorry for the inconvenience if the bug really should have been left as Available.
For more details visithttps://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Sorry for the inconvenience if the bug really should have been left as Available.
For more details visit
ka...@google.com <ka...@google.com> #11
[Empty comment from Monorail migration]
rw...@scottlogic.com <rw...@scottlogic.com> #12
[Empty comment from Monorail migration]
pe...@google.com <pe...@google.com> #13
This issue was migrated from crbug.com/chromium/1159587?no_tracker_redirect=1
[Monorail components added to Component Tags custom field.]
[Monorail components added to Component Tags custom field.]
Description
Steps to reproduce the problem
Problem Description
I'm unzipping a zip file containing a large number of small files, into a directory structure on the user-visible filesystem (not the Origin private file system, as the user needs these files). I'm aware that such writes first go to a .crswap temporary file, which are scanned for safety before being copied to the destination file.
It appears that Chrome creates a process for each file created, with no limit. In my scenario, the >1000 of processes effectively bring my machine to a halt for several minutes.
I suggest that there should at least be some limit on how many of these processes can be running at once.
Further, I'm not sure how efficient the process-per-file approach is for scenarios involving a large number of files. Some further efficiency improvements may be necessary to enable use cases such as mine.
Additional Comments
I am aware of https://issues.chromium.org/issues/40743502 on which there is discussion about whether there should be a temp file at all.
Also reproduced in Chrome 126 Beta.
Summary
Unbounded creation of file quarantine.mojom.quarantine utility processes via File System Access API
Custom Questions
Which component does this fall under?
Blink>Storage
Does this work in other browsers?
Not sure - I don't know
Additional Data
Category: API
Chrome Channel: Stable
Regression: N/A