printing: Sandboxed processes must ask the browser to allocate shared memory.

printing: Sandboxed processes must ask the browser to allocate shared memory.

SharedMemory is being changed on Windows so that the underlying File Mapping
Object is always named. This means that sandboxed processes must request the
object from the browser process, just like on POSIX.

BUG=493414
Committed: https://crrev.com/72780b29dcf5642ad50df5c3421e6e2e625c704e
Cr-Commit-Position: refs/heads/master@{#376335}

[erikchen, 2016-02-18 21:56:37]

The CQ bit was checked by erikchen@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-02-18 21:57:17]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1714643002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1714643002/1

[erikchen, 2016-02-18 21:58:20]

erikchen@chromium.org changed reviewers:
+ thestig@chromium.org

[erikchen, 2016-02-18 21:58:20]

thestig: Please review.

Note that this CL is doing the same thing as
https://codereview.chromium.org/1705863003/, just for a different process.

[Lei Zhang, 2016-02-18 22:04:52]

lgtm, horray for consistency.

[commit-bot: I haz the power, 2016-02-18 22:19:46]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-02-18 22:19:47]

Dry run: Try jobs failed on following builders:
  android_arm64_dbg_recipe on tryserver.chromium.android (JOB_FAILED,
https://build.chromium.org/p/tryserver.chromium.android/builders/android_arm6...)
  android_compile_dbg on tryserver.chromium.android (JOB_FAILED,
https://build.chromium.org/p/tryserver.chromium.android/builders/android_comp...)
  linux_android_rel_ng on tryserver.chromium.android (JOB_FAILED,
https://build.chromium.org/p/tryserver.chromium.android/builders/linux_androi...)
  chromeos_daisy_chromium_compile_only_ng on tryserver.chromium.linux
(JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/chromeos_daisy_...)
  linux_chromium_compile_dbg_ng on tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
  mac_chromium_compile_dbg_ng on tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_comp...)

[erikchen, 2016-02-18 22:23:11]

The CQ bit was checked by erikchen@chromium.org

[erikchen, 2016-02-18 22:23:11]

The patchset sent to the CQ was uploaded after l-g-t-m from thestig@chromium.org
Link to the patchset: https://codereview.chromium.org/1714643002/#ps20001
(title: "Fix compile error.")

[commit-bot: I haz the power, 2016-02-18 22:24:22]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1714643002/20001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1714643002/20001

[commit-bot: I haz the power, 2016-02-18 22:50:39]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-02-18 22:50:40]

Try jobs failed on following builders:
  linux_chromium_gn_chromeos_rel on tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[erikchen, 2016-02-19 00:23:59]

The CQ bit was checked by erikchen@chromium.org

[commit-bot: I haz the power, 2016-02-19 00:27:07]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1714643002/20001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1714643002/20001

[commit-bot: I haz the power, 2016-02-19 01:30:24]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2016-02-19 01:31:25]

Description was changed from

==========
printing: Sandboxed processes must ask the browser to allocate shared memory.

SharedMemory is being changed on Windows so that the underlying File Mapping
Object is always named. This means that sandboxed processes must request the
object from the browser process, just like on POSIX.

BUG=493414
==========

to

==========
printing: Sandboxed processes must ask the browser to allocate shared memory.

SharedMemory is being changed on Windows so that the underlying File Mapping
Object is always named. This means that sandboxed processes must request the
object from the browser process, just like on POSIX.

BUG=493414

Committed: https://crrev.com/72780b29dcf5642ad50df5c3421e6e2e625c704e
Cr-Commit-Position: refs/heads/master@{#376335}
==========

[commit-bot: I haz the power, 2016-02-19 01:31:26]

Patchset 2 (id:??) landed as
https://crrev.com/72780b29dcf5642ad50df5c3421e6e2e625c704e
Cr-Commit-Position: refs/heads/master@{#376335}