Obsolete
Status Update
No update yet.
Comments
db...@chromium.org
we communicate with flash to clear LSOs IIRC
dd...@chromium.org
Also reproduced on Mac 25.0.1364.99 (Official Build 183764). This likely affects all OSes that have Flapper.
Does Flash require the broker to access LSOs?
It seems like a really bad idea to launch any Flash process before asked to read/write the settings. This also bypasses the Broker infobar. I guess we trust the Browser process and/or chrome:// URLs, but I don't really want Flash running unsandboxed on my system just because I checked Chrome's settings.
Does Flash require the broker to access LSOs?
It seems like a really bad idea to launch any Flash process before asked to read/write the settings. This also bypasses the Broker infobar. I guess we trust the Browser process and/or chrome:// URLs, but I don't really want Flash running unsandboxed on my system just because I checked Chrome's settings.
db...@chromium.org
I don't know what the broker is, just that this is a reason we need to communicate with Flash on the settings page.
dd...@chromium.org
I should have explained: The Broker is an unsandboxed process running the Flash binary. It has a different entrypoint, but it is still Flash code. Its main uses are for Flash Access (DRM), installing Adobe Air apps, etc. Most Flash use cases do not require it and most users will never launch it (except for this bug).
db...@chromium.org
ddorwin@: also Content settings > Unsandboxed plugin access is likely related.
ro...@chromium.org
[Empty comment from Monorail migration]
js...@chromium.org
There's some weird thing wired up here for handling LSOs, but I don't remember what it is. Brett or Trung should be able to explain it.
js...@chromium.org
[Empty comment from Monorail migration]
bu...@chromium.org
[Empty comment from Monorail migration]
js...@chromium.org
I have no idea why I would be assigned owner of this.
js...@chromium.org
This is working as intended. I confirmed that the Flash broker is launched as an interface to the Flash specific settings, because the code for manipulating that lives in Flash, not Chrome. (In retrospect, I guess I ended up being owner.)
bu...@chromium.org
[Empty comment from Monorail migration]
bu...@chromium.org
[Empty comment from Monorail migration]
bu...@chromium.org
[Empty comment from Monorail migration]
bu...@chromium.org
[Empty comment from Monorail migration]
js...@chromium.org
Bulk release of old security bug reports.
js...@chromium.org
Bulk release of old security bug reports.
is...@google.com
This issue was migrated from crbug.com/chromium/181324?no_tracker_redirect=1
[Auto-CCs applied]
[Multiple monorail components: Blink, Internals, Internals>Plugins, Internals>Plugins>Flash, Internals>Plugins>Pepper, Security, UI>Settings]
[Monorail components added to Component Tags custom field.]
[Auto-CCs applied]
[Multiple monorail components: Blink, Internals, Internals>Plugins, Internals>Plugins>Flash, Internals>Plugins>Pepper, Security, UI>Settings]
[Monorail components added to Component Tags custom field.]
Description
Version: 27.0.1434.0 (Developer Build 187052), 26.0.1410.27 (Official Build 186066) beta
OS: Linux x64
What steps will reproduce the problem?
(Explanation for the second tab: I thought that one time this did not reproduce when going to chrome://settings from the only open tab. However, I cannot reproduce that now.)
What is the expected output? What do you see instead?
Only the Browser process and two Renderer processes are running.
Instead, after the settings page loads, a "Plug-in Broker: Shockwave Flash" process is running.
Please use labels and text to provide additional information.
There is no reason for the broker to be running. Even worse, there isn't a matching Flash plugin process.
Using the PID from Task Manager (11592):
ps aux | grep 11592
11592 0.4 0.0 1014296 49616 pts/3 Sl+ 16:27 0:00 /src/chrome/src/out/Debug/chrome --type=ppapi-broker --channel=11348.13.2055978969 --lang=en-US --enable-crash-reporter=09BDC74E9804ED131ECB8038B2ED7E34,Ubuntu 12.04.1 LTS
Then looking for the process that created the channel (11348):
ps aux | grep 11348
11348 9.5 0.2 1381328 159984 pts/3 Sl+ 16:27 0:22 /src/chrome/src/out/Debug/chrome --user-data-dir=/tmp/newprofile
11592 0.0 0.0 1014296 49616 pts/3 Sl+ 16:27 0:00 /src/chrome/src/out/Debug/chrome --type=ppapi-broker --channel=11348.13.2055978969 --lang=en-US --enable-crash-reporter=09BDC74E9804ED131ECB8038B2ED7E34,Ubuntu 12.04.1 LTS
11903 0.0 0.0 20184 928 pts/7 S+ 16:30 0:00 grep --color=auto 11348