Revert of Skeleton of the overall design for the database for Pver4

Revert of Skeleton of the overall design for the database for Pver4 (patchset #5 id:80001 of https://codereview.chromium.org/1952843003/ )

Reason for revert:
Speculative; lots of browser tests started failing with leak reports, and all stacks contain "safe browsing". See https://build.chromium.org/p/chromium.linux/builders/Linux%20Tests%20%28dbg%29%281%29/builds/54004, e.g.

[444:555:0506/185642:ERROR:leak_tracker.h(100)] #0 0x7fd9c5c00d0e base::debug::StackTrace::StackTrace()
#1 0x00000186cf6f base::debug::LeakTracker<>::LeakTracker()
#2 0x0000018635bb SystemURLRequestContextGetter::SystemURLRequestContextGetter()
#3 0x000001865c21 IOThread::InitSystemRequestContext()
#4 0x000001865af5 IOThread::system_url_request_context_getter()
#5 0x000001a08b90 BrowserProcessImpl::system_request_context()
#6 0x000001ef00c4 safe_browsing::SafeBrowsingService::Initialize()
#7 0x000001a0c1b0 BrowserProcessImpl::CreateSafeBrowsingService()
#8 0x000001a0c022 BrowserProcessImpl::safe_browsing_service()

Original issue's description:
> Skeleton of the overall design for the database for Pver4
> Design doc: https://goto.google.com/chromium-pver4-design-doc
>
> BUG==543161
>
> Committed: https://crrev.com/8354386e0eb264960f0ccdaa9e3e003ad72f0bcd
> Cr-Commit-Position: refs/heads/master@{#392211}

TBR=nparker@chromium.org,vakh@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG==543161

Committed: https://crrev.com/11fe25ad8c2112312c4f0cad5bec97047eb0befe
Cr-Commit-Position: refs/heads/master@{#392262}

[Nico, 2016-05-07 14:31:00]

Created Revert of Skeleton of the overall design for the database for Pver4

[commit-bot: I haz the power, 2016-05-07 14:31:09]

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

[commit-bot: I haz the power, 2016-05-07 14:32:37]

Description was changed from

==========
Revert of Skeleton of the overall design for the database for Pver4 (patchset #5
id:80001 of https://codereview.chromium.org/1952843003/ )

Reason for revert:
Speculative; lots of browser tests started failing with leak reports, and all
stacks contain "safe browsing". See
https://build.chromium.org/p/chromium.linux/builders/Linux%20Tests%20%28dbg%2...,
e.g.

[444:555:0506/185642:ERROR:leak_tracker.h(100)] #0 0x7fd9c5c00d0e
base::debug::StackTrace::StackTrace()
#1 0x00000186cf6f base::debug::LeakTracker<>::LeakTracker()
#2 0x0000018635bb SystemURLRequestContextGetter::SystemURLRequestContextGetter()
#3 0x000001865c21 IOThread::InitSystemRequestContext()
#4 0x000001865af5 IOThread::system_url_request_context_getter()
#5 0x000001a08b90 BrowserProcessImpl::system_request_context()
#6 0x000001ef00c4 safe_browsing::SafeBrowsingService::Initialize()
#7 0x000001a0c1b0 BrowserProcessImpl::CreateSafeBrowsingService()
#8 0x000001a0c022 BrowserProcessImpl::safe_browsing_service()


Original issue's description:
> Skeleton of the overall design for the database for Pver4
> Design doc: https://goto.google.com/chromium-pver4-design-doc
> 
> BUG==543161
> 
> Committed: https://crrev.com/8354386e0eb264960f0ccdaa9e3e003ad72f0bcd
> Cr-Commit-Position: refs/heads/master@{#392211}

TBR=nparker@chromium.org,vakh@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG==543161
==========

to

==========
Revert of Skeleton of the overall design for the database for Pver4 (patchset #5
id:80001 of https://codereview.chromium.org/1952843003/ )

Reason for revert:
Speculative; lots of browser tests started failing with leak reports, and all
stacks contain "safe browsing". See
https://build.chromium.org/p/chromium.linux/builders/Linux%20Tests%20%28dbg%2...,
e.g.

[444:555:0506/185642:ERROR:leak_tracker.h(100)] #0 0x7fd9c5c00d0e
base::debug::StackTrace::StackTrace()
#1 0x00000186cf6f base::debug::LeakTracker<>::LeakTracker()
#2 0x0000018635bb SystemURLRequestContextGetter::SystemURLRequestContextGetter()
#3 0x000001865c21 IOThread::InitSystemRequestContext()
#4 0x000001865af5 IOThread::system_url_request_context_getter()
#5 0x000001a08b90 BrowserProcessImpl::system_request_context()
#6 0x000001ef00c4 safe_browsing::SafeBrowsingService::Initialize()
#7 0x000001a0c1b0 BrowserProcessImpl::CreateSafeBrowsingService()
#8 0x000001a0c022 BrowserProcessImpl::safe_browsing_service()


Original issue's description:
> Skeleton of the overall design for the database for Pver4
> Design doc: https://goto.google.com/chromium-pver4-design-doc
> 
> BUG==543161
> 
> Committed: https://crrev.com/8354386e0eb264960f0ccdaa9e3e003ad72f0bcd
> Cr-Commit-Position: refs/heads/master@{#392211}

TBR=nparker@chromium.org,vakh@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG==543161
==========

[commit-bot: I haz the power, 2016-05-07 14:32:38]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-05-07 14:34:16]

Description was changed from

==========
Revert of Skeleton of the overall design for the database for Pver4 (patchset #5
id:80001 of https://codereview.chromium.org/1952843003/ )

Reason for revert:
Speculative; lots of browser tests started failing with leak reports, and all
stacks contain "safe browsing". See
https://build.chromium.org/p/chromium.linux/builders/Linux%20Tests%20%28dbg%2...,
e.g.

[444:555:0506/185642:ERROR:leak_tracker.h(100)] #0 0x7fd9c5c00d0e
base::debug::StackTrace::StackTrace()
#1 0x00000186cf6f base::debug::LeakTracker<>::LeakTracker()
#2 0x0000018635bb SystemURLRequestContextGetter::SystemURLRequestContextGetter()
#3 0x000001865c21 IOThread::InitSystemRequestContext()
#4 0x000001865af5 IOThread::system_url_request_context_getter()
#5 0x000001a08b90 BrowserProcessImpl::system_request_context()
#6 0x000001ef00c4 safe_browsing::SafeBrowsingService::Initialize()
#7 0x000001a0c1b0 BrowserProcessImpl::CreateSafeBrowsingService()
#8 0x000001a0c022 BrowserProcessImpl::safe_browsing_service()


Original issue's description:
> Skeleton of the overall design for the database for Pver4
> Design doc: https://goto.google.com/chromium-pver4-design-doc
> 
> BUG==543161
> 
> Committed: https://crrev.com/8354386e0eb264960f0ccdaa9e3e003ad72f0bcd
> Cr-Commit-Position: refs/heads/master@{#392211}

TBR=nparker@chromium.org,vakh@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG==543161
==========

to

==========
Revert of Skeleton of the overall design for the database for Pver4 (patchset #5
id:80001 of https://codereview.chromium.org/1952843003/ )

Reason for revert:
Speculative; lots of browser tests started failing with leak reports, and all
stacks contain "safe browsing". See
https://build.chromium.org/p/chromium.linux/builders/Linux%20Tests%20%28dbg%2...,
e.g.

[444:555:0506/185642:ERROR:leak_tracker.h(100)] #0 0x7fd9c5c00d0e
base::debug::StackTrace::StackTrace()
#1 0x00000186cf6f base::debug::LeakTracker<>::LeakTracker()
#2 0x0000018635bb SystemURLRequestContextGetter::SystemURLRequestContextGetter()
#3 0x000001865c21 IOThread::InitSystemRequestContext()
#4 0x000001865af5 IOThread::system_url_request_context_getter()
#5 0x000001a08b90 BrowserProcessImpl::system_request_context()
#6 0x000001ef00c4 safe_browsing::SafeBrowsingService::Initialize()
#7 0x000001a0c1b0 BrowserProcessImpl::CreateSafeBrowsingService()
#8 0x000001a0c022 BrowserProcessImpl::safe_browsing_service()

Original issue's description:
> Skeleton of the overall design for the database for Pver4
> Design doc: https://goto.google.com/chromium-pver4-design-doc
>
> BUG==543161
>
> Committed: https://crrev.com/8354386e0eb264960f0ccdaa9e3e003ad72f0bcd
> Cr-Commit-Position: refs/heads/master@{#392211}

TBR=nparker@chromium.org,vakh@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG==543161

Committed: https://crrev.com/11fe25ad8c2112312c4f0cad5bec97047eb0befe
Cr-Commit-Position: refs/heads/master@{#392262}
==========

[commit-bot: I haz the power, 2016-05-07 14:34:17]

Patchset 1 (id:??) landed as
https://crrev.com/11fe25ad8c2112312c4f0cad5bec97047eb0befe
Cr-Commit-Position: refs/heads/master@{#392262}

[Nico, 2016-05-07 16:08:41]

This revert did _not_ help. I'll reland this CL once I found the real
culprit.
On May 7, 2016 10:34 AM, "commit-bot@chromium.org via
codereview.chromium.org" <reply@chromiumcodereview-hr.appspotmail.com>
wrote:

> Patchset 1 (id:??) landed as
> https://crrev.com/11fe25ad8c2112312c4f0cad5bec97047eb0befe
> Cr-Commit-Position: refs/heads/master@{#392262}
>
> https://codereview.chromium.org/1960893002/
>

-- 
You received this message because you are subscribed to the Google Groups
"Chromium-reviews" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to chromium-reviews+unsubscribe@chromium.org.

[Nico, 2016-05-07 19:30:25]

A revert of this CL (patchset #1 id:1) has been created in
https://codereview.chromium.org/1963463002/ by thakis@chromium.org.

The reason for reverting is: This revert didn't help, the real culprit was
https://codereview.chromium.org/1835823002/.