| Index: chrome/browser/android/provider/blocking_ui_thread_async_request.cc
|
| diff --git a/chrome/browser/android/provider/blocking_ui_thread_async_request.cc b/chrome/browser/android/provider/blocking_ui_thread_async_request.cc
|
| index 7267e583ef55d4d8ae29219d8fcf466f6ab83ec3..4eb9811ed63aa68e8a87b5f1d713d36fe82df0d9 100644
|
| --- a/chrome/browser/android/provider/blocking_ui_thread_async_request.cc
|
| +++ b/chrome/browser/android/provider/blocking_ui_thread_async_request.cc
|
| @@ -12,6 +12,6 @@ void BlockingUIThreadAsyncRequest::RequestCompleted() {
|
| // Currently all our use cases receive their request response in the UI
|
| // thread (the same thread that made the request). However this is not
|
| // a design constraint and can be changed if ever needed.
|
| - DCHECK(content::BrowserThread::CurrentlyOn(content::BrowserThread::UI));
|
| + DCHECK_CURRENTLY_ON(content::BrowserThread::UI);
|
| request_completed_.Signal();
|
| }
|
|
|