|
|
DescriptionReset Bluetooth EventHandler when it is invalid
When BluetoothChooser object is destroyed, its associated Bluetooth
EventHandler becomes invalid too and should not be used any more.
This CL resets the Bluetooth EventHandler when it becomes invalid
so that it can't be used any more.
BUG=629298
Committed: https://crrev.com/b583bbc88c44a1b90192110b071486cd953067e9
Cr-Commit-Position: refs/heads/master@{#410690}
Patch Set 1 : reset Bluetooth EventHandler when it is not valid #
Total comments: 4
Patch Set 2 : address comments #Patch Set 3 : fixed mac compile error #Patch Set 4 : tried fixing compile errors #
Total comments: 2
Patch Set 5 : added CONTENT_EXPORT #Patch Set 6 : added CONTENT_EXPORT #
Messages
Total messages: 45 (31 generated)
The CQ bit was checked by juncai@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Description was changed from ========== Reset Bluetooth EventHandler when it is not valid When BluetoothChooser object is destroyed, its associated Bluetooth EventHandler becomes invalid too and should not be used any more. This CL resets the Bluetooth EventHandler when it becomes invalid so that it can't be used any more. BUG=629298 ========== to ========== Reset Bluetooth EventHandler when it is invalid When BluetoothChooser object is destroyed, its associated Bluetooth EventHandler becomes invalid too and should not be used any more. This CL resets the Bluetooth EventHandler when it becomes invalid so that it can't be used any more. BUG=629298 ==========
juncai@chromium.org changed reviewers: + jyasskin@chromium.org
Please take a look.
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
https://codereview.chromium.org/2203103003/diff/1/chrome/browser/ui/bluetooth... File chrome/browser/ui/bluetooth/bluetooth_chooser_controller.cc (right): https://codereview.chromium.org/2203103003/diff/1/chrome/browser/ui/bluetooth... chrome/browser/ui/bluetooth/bluetooth_chooser_controller.cc:79: if (event_handler_.is_null()) Would it make sense to record how often this happens to UMA? Each time it does is probably a confusing user experience (since their selection didn't take effect), so we'd like to fix it, and when the numbers reach 0, we can turn this into a DCHECK. https://codereview.chromium.org/2203103003/diff/1/chrome/browser/ui/bluetooth... File chrome/browser/ui/bluetooth/bluetooth_chooser_desktop.cc (right): https://codereview.chromium.org/2203103003/diff/1/chrome/browser/ui/bluetooth... chrome/browser/ui/bluetooth/bluetooth_chooser_desktop.cc:17: bluetooth_chooser_controller_->ResetEventHandler(); Comment here that this satisfies the WebContentsDelegate:: RunBluetoothChooser() requirement that the EventHandler can be destroyed any time after the BluetoothChooser instance.
The CQ bit was checked by juncai@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
https://codereview.chromium.org/2203103003/diff/1/chrome/browser/ui/bluetooth... File chrome/browser/ui/bluetooth/bluetooth_chooser_controller.cc (right): https://codereview.chromium.org/2203103003/diff/1/chrome/browser/ui/bluetooth... chrome/browser/ui/bluetooth/bluetooth_chooser_controller.cc:79: if (event_handler_.is_null()) On 2016/08/05 20:37:51, Jeffrey Yasskin wrote: > Would it make sense to record how often this happens to UMA? Each time it does > is probably a confusing user experience (since their selection didn't take > effect), so we'd like to fix it, and when the numbers reach 0, we can turn this > into a DCHECK. Done. https://codereview.chromium.org/2203103003/diff/1/chrome/browser/ui/bluetooth... File chrome/browser/ui/bluetooth/bluetooth_chooser_desktop.cc (right): https://codereview.chromium.org/2203103003/diff/1/chrome/browser/ui/bluetooth... chrome/browser/ui/bluetooth/bluetooth_chooser_desktop.cc:17: bluetooth_chooser_controller_->ResetEventHandler(); On 2016/08/05 20:37:51, Jeffrey Yasskin wrote: > Comment here that this satisfies the WebContentsDelegate:: RunBluetoothChooser() > requirement that the EventHandler can be destroyed any time after the > BluetoothChooser instance. Done.
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: mac_chromium_compile_dbg_ng on master.tryserver.chromium.mac (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_comp...)
The CQ bit was checked by juncai@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: linux_chromium_compile_dbg_ng on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
The CQ bit was checked by juncai@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: linux_chromium_chromeos_ozone_rel_ng on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
lgtm https://codereview.chromium.org/2203103003/diff/60001/content/browser/bluetoo... File content/browser/bluetooth/bluetooth_metrics.h (right): https://codereview.chromium.org/2203103003/diff/60001/content/browser/bluetoo... content/browser/bluetooth/bluetooth_metrics.h:86: void RecordRequestDeviceOutcome(UMARequestDeviceOutcome outcome); You'll have to mark this with CONTENT_EXPORT.
The CQ bit was checked by juncai@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was checked by juncai@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: chromeos_daisy_chromium_compile_only_ng on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/chromeos_daisy_...)
The CQ bit was checked by juncai@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from jyasskin@chromium.org Link to the patchset: https://codereview.chromium.org/2203103003/#ps100001 (title: "added CONTENT_EXPORT")
https://codereview.chromium.org/2203103003/diff/60001/content/browser/bluetoo... File content/browser/bluetooth/bluetooth_metrics.h (right): https://codereview.chromium.org/2203103003/diff/60001/content/browser/bluetoo... content/browser/bluetooth/bluetooth_metrics.h:86: void RecordRequestDeviceOutcome(UMARequestDeviceOutcome outcome); On 2016/08/08 16:48:38, Jeffrey Yasskin wrote: > You'll have to mark this with CONTENT_EXPORT. Done.
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: chromium_presubmit on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)
juncai@chromium.org changed reviewers: + rkaplow@chromium.org
rkaplow@chromium.org: Please review changes at //tools/metrics/histograms/histograms.xml
lgtm
The CQ bit was checked by juncai@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Message was sent while issue was closed.
Description was changed from ========== Reset Bluetooth EventHandler when it is invalid When BluetoothChooser object is destroyed, its associated Bluetooth EventHandler becomes invalid too and should not be used any more. This CL resets the Bluetooth EventHandler when it becomes invalid so that it can't be used any more. BUG=629298 ========== to ========== Reset Bluetooth EventHandler when it is invalid When BluetoothChooser object is destroyed, its associated Bluetooth EventHandler becomes invalid too and should not be used any more. This CL resets the Bluetooth EventHandler when it becomes invalid so that it can't be used any more. BUG=629298 ==========
Message was sent while issue was closed.
Committed patchset #6 (id:100001)
Message was sent while issue was closed.
Description was changed from ========== Reset Bluetooth EventHandler when it is invalid When BluetoothChooser object is destroyed, its associated Bluetooth EventHandler becomes invalid too and should not be used any more. This CL resets the Bluetooth EventHandler when it becomes invalid so that it can't be used any more. BUG=629298 ========== to ========== Reset Bluetooth EventHandler when it is invalid When BluetoothChooser object is destroyed, its associated Bluetooth EventHandler becomes invalid too and should not be used any more. This CL resets the Bluetooth EventHandler when it becomes invalid so that it can't be used any more. BUG=629298 Committed: https://crrev.com/b583bbc88c44a1b90192110b071486cd953067e9 Cr-Commit-Position: refs/heads/master@{#410690} ==========
Message was sent while issue was closed.
Patchset 6 (id:??) landed as https://crrev.com/b583bbc88c44a1b90192110b071486cd953067e9 Cr-Commit-Position: refs/heads/master@{#410690}
Message was sent while issue was closed.
The include from chrome/browser/ui/bluetooth/bluetooth_chooser_controller.cc of content/browser/bluetooth/bluetooth_metrics.h (and the DEPS rule where you whitelisted this include) isn't correct because you're including private content headers from outside of content. Headers included from outside of content should be in content/public (then you wouldn't have had to add the DEPS file at all). Can you please fix this soon? This is the last thing that prevents "gn check: from running on //content/browser/ui/* (which would have also told you this was incorrect). Thanks!
Message was sent while issue was closed.
I filed https://bugs.chromium.org/p/chromium/issues/detail?id=641105 for this. |