New issue
Advanced search Search tips

Issue 914343 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

memory.leak_detection/https://www.livejournal.com/ failing on chromium.linux/Leak Detection Linux

Project Member Reported by sheriff-...@appspot.gserviceaccount.com, Dec 12

Issue description

Filed by sheriff-o-matic@appspot.gserviceaccount.com on behalf of fhorschig@google.com

memory.leak_detection/https://www.livejournal.com/ in memory.leak_detection failing on chromium.linux/Leak Detection Linux: 
 https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Leak%20Detection%20Linux

Log snippet:
[ RUN      ] memory.leak_detection/https://www.livejournal.com/
(WARNING) 2018-12-12 05:25:26,325 inspector_log._OnMessage:26  DevTools console [network]: Failed to load resource: the server responded with a status of 404 (Not Found) https://st.top100.ru/top100/top100.js
(WARNING) 2018-12-12 05:25:26,325 inspector_log._OnMessage:26  DevTools console [network]: Failed to load resource: the server responded with a status of 404 (Not Found) https://www.tns-counter.ru/V13a***R%3E*sup_ru/ru/UTF-8/tmsec=lj_noncyr/562000000
(WARNING) 2018-12-12 05:25:27,221 inspector_log._OnMessage:26  DevTools console [network]: Failed to load resource: the server responded with a status of 404 () https://securepubads.g.doubleclick.net/gpt/pubads_impl_240.js
(WARNING) 2018-12-12 05:25:27,222 inspector_log._OnMessage:26  DevTools console [network]: Failed to load resource: the server responded with a status of 404 () https://pagead2.googlesyndication.com/pagead/js/r20180813/r20180604/show_ads_impl_le.js
(WARNING) 2018-12-12 05:25:59,480 inspector_log._OnMessage:26  DevTools console [network]: Failed to load resource: the server responded with a status of 404 () https://pagead2.googlesyndication.com/pagead/js/r20180813/r20180604/show_ads_impl_le.js
(ERROR) 2018-12-12 05:26:02,770 story_runner.ProcessError:119  Handleable error
Traceback (most recent call last):
  File "/b/s/w/ir/third_party/catapult/telemetry/telemetry/internal/story_runner.py", line 145, in _RunStoryAndProcessErrorIfNeeded
    state.RunStory(results)
  File "/b/s/w/ir/third_party/catapult/common/py_trace_event/py_trace_event/trace_event_impl/decorators.py", line 75, in traced_function
    return func(*args, **kwargs)
  File "/b/s/w/ir/third_party/catapult/telemetry/telemetry/page/shared_page_state.py", line 304, in RunStory
    self._current_page.Run(self)
  File "/b/s/w/ir/third_party/catapult/telemetry/telemetry/page/__init__.py", line 95, in Run
    shared_state.page_test.RunNavigateSteps(self, current_tab)
  File "/b/s/w/ir/third_party/catapult/common/py_trace_event/py_trace_event/trace_event_impl/decorators.py", line 75, in traced_function
    return func(*args, **kwargs)
  File "/b/s/w/ir/third_party/catapult/telemetry/telemetry/page/legacy_page_test.py", line 152, in RunNavigateSteps
    page.RunNavigateSteps(action_runner)
  File "/b/s/w/ir/tools/perf/contrib/leak_detection/page_sets.py", line 29, in RunNavigateSteps
    self._WaitForPageLoadToComplete(new_tab.action_runner)
  File "/b/s/w/ir/tools/perf/contrib/leak_detection/page_sets.py", line 36, in _WaitForPageLoadToComplete
    py_utils.WaitFor(action_runner.tab.HasReachedQuiescence, timeout=30)
  File "/b/s/w/ir/third_party/catapult/common/py_utils/py_utils/__init__.py", line 150, in WaitFor
    (timeout, GetConditionString()))
TimeoutException: Timed out while waiting 30s for HasReachedQuiescence.
(WARNING) 2018-12-12 05:26:02,771 desktop_browser_backend._GetAllCrashpadMinidumps:322  No path to crashpad_database_util found
(WARNING) 2018-12-12 05:26:02,772 shared_page_state.DumpStateUponFailure:130  Taking screenshots upon failures disabled.
(ERROR) 2018-12-12 05:26:02,772 page_test_results.Fail:587  Failure recorded: Exception raised running https://www.livejournal.com/
[  FAILED  ] memory.leak_detection/https://www.livejournal.com/ (44115 ms)

There are quite some recent failures but for various reasons:

memory.leak_detection/https://www.homedepot.com/ (StoryActionError('Unable to obtain memory dump'))
https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Leak%20Detection%20Linux/27523

memory.leak_detection/https://www.yahoo.com (Memory leak is found.)
https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Leak%20Detection%20Linux/27508

memory.leak_detection/https://www.hotels.com/ (Timeout)
https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Leak%20Detection%20Linux/27496

memory.leak_detection/http://www.hockeybuzz.com (Memory leak is found.)
https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Leak%20Detection%20Linux/27472
 
Owner: erikc...@chromium.org
Status: Assigned (was: Available)
I took a look at all the failure for the last 24 hours and it seems random. This needs to be investigated, but not sure who the owner is.

erikchen@ Can you take a look?
Owner: yuzus@chromium.org
This code looks like it was added by yuzus@.
Labels: -Pri-2 -Sheriff-Chromium Pri-1
Removing from sheriff queue, because the test has been flaky for a while.
Bumping priority, please consider disabling the test if you're not working on it.
Components: Blink
Labels: OS-Linux Type-Bug
Here are a couple more failures:

https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Leak%20Detection%20Linux/27978
https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Leak%20Detection%20Linux/27993

Should these be separated out into individual bugs? Are there instructions for how to deal with failures from this bot?
Sorry it took me a while to respond. I added the leak detector bot.

I will disable the flaky timeout tests and look into the leak bugs to see if they are real leaks. 
Also I could write up a brief instruction on how to deal with failures from the bot. Do you know where I should put the instruction?
Project Member

Comment 6 by bugdroid1@chromium.org, Dec 18

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/06bcceab73bc64236f661652d781cbfbadfb70d4

commit 06bcceab73bc64236f661652d781cbfbadfb70d4
Author: Yuzu Saijo <yuzus@chromium.org>
Date: Tue Dec 18 08:36:19 2018

Fix timeout tests in leak detector

Some tests in leak detector are failing flakily for timeout. This CL
changes the timing of navigation for those websites so that they would
not wait until the whole page load to be completed but until document
state is ready.

Change-Id: Ia64fb72d6831c4931faecab957c8ef789b2b92f8
Bug: 914343
Reviewed-on: https://chromium-review.googlesource.com/c/1381298
Reviewed-by: Keishi Hattori <keishi@chromium.org>
Commit-Queue: Yuzu Saijo <yuzus@chromium.org>
Cr-Commit-Position: refs/heads/master@{#617415}
[modify] https://crrev.com/06bcceab73bc64236f661652d781cbfbadfb70d4/tools/perf/contrib/leak_detection/page_sets.py

Components: -Blink Blink>Internals

Sign in to add a comment