New issue
Advanced search Search tips

Issue 854953 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Jul 30
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Chromium flashback when open setting page(chrome://settings)

Reported by wangqing...@loongson.cn, Jun 21 2018

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3189.0 Safari/537.36

Steps to reproduce the problem:
1. Open the chromium
2. Open setting page--chrome://settings

What is the expected behavior?
The settings page can be displayed normally

What went wrong?
chromium flashback and terminal displays the following information:
[32283:32294:0602/095802.901352:FATAL:template_expressions.cc(110)] Check failed: false. Unknown context %7BaboutObsoleteSystemURL%7D" target="_blank">
                    $i18n

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: lastest  Channel: n/a
OS Version: CentOS Linux release 7.4.1708
Flash Version:
 
Labels: Needs-Milestone
Cc: susan.boorgula@chromium.org
Labels: Needs-Feedback Triaged-ET
wangqing-hf@ Thanks for the issue.

Tested this issue on Ubuntu 17.10 and 14.04 on the latest Stable 67.0.3396.99 and Beta 68.0.3440.34 and unable to reproduce the issue.
By navigating to chrome://settings, can view the contents of the settings page without any issues.

Request you to retry the issue on a new profile without any flags/extensions and update the thread with the observations.

Also request you to confirm if this issue is observed only on CentOS Linux?

Thanks..
Yes
Currently only test on CentOS/Fedora Linux。
Can you test on CentOS Linux?
Project Member

Comment 4 by sheriffbot@chromium.org, Jun 27 2018

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: TE-NeedsTriageFromHYD
As per comment# 2, Unable to reproduce the issue on chrome reported version 67.0.3396.99 using Ubuntu 14.04 and 17.10 and as per comment# 3 from the reporter need to test this issue on Fedora Linux, hence routing this issue to Inhouse to test the issue on Fedora and adding TE-NeedsTriageFromHYD label.

Thanks!
comment# 2, what's your gn_configs when build chromium?
Cc: rbasuvula@chromium.org
Components: UI
Labels: -TE-NeedsTriageFromHYD Needs-Feedback
Thanks for the update! Tested in chrome # 67.0.3396.99 on Fedora 25 and not able to reproduce the issue.Please find the screen shots for your reference.

@ wangqing-hf: Could you please let me know if i have missed anything and if possible,Please Re-check once in latest chrome builds of chromium and let us know the observations of the issue which would help us to triage the issue further.

Thanks in Advance!
854953.png
92.4 KB View Download
build chromium #69.0.3481.0 and start chromium to open chrome://settings.
occur errors on terminal:
[18458:18471:0709/093722.990841:FATAL:template_expressions.cc(110)] Check failed: false. Unknown context %7BaboutObsoleteSystemURL%7D" target="_blank">
                    $i18n
#0 0x00ffed2d9898 base::debug::StackTrace::StackTrace()
#1 0x00ffed2219b4 base::debug::StackTrace::StackTrace()
#2 0x00ffed23ac5c logging::LogMessage::~LogMessage()
#3 0x00ffed382c00 ui::ReplaceTemplateExpressions()
#4 0x00ffed383c80 ui::I18nSourceStream::FilterData()
#5 0x00ffedbb67e0 net::FilterSourceStream::DoFilterData()
#6 0x00ffedbb699c net::FilterSourceStream::DoLoop()
#7 0x00ffedbb6a54 net::FilterSourceStream::Read()
#8 0x00ffedd1be78 net::URLRequestJob::Read()
#9 0x00ffedd12824 net::URLRequest::Read()
#10 0x00ffeb4764d4 content::ResourceLoader::ReadMore()
#11 0x00ffeb477320 content::ResourceLoader::PrepareToReadMore()
#12 0x00ffeb477f74 content::ResourceLoader::Resume()
#13 0x00ffeb47807c content::ResourceLoader::ScopedDeferral::~ScopedDeferral()
#14 0x00ffeb4783c8 content::ResourceLoader::CompleteRead()
#15 0x00ffeb4785c8 content::ResourceLoader::OnReadCompleted()
#16 0x00ffed2221e4 base::debug::TaskAnnotator::RunTask()
#17 0x00ffed2ffc48 base::internal::IncomingTaskQueue::RunTask()
#18 0x00ffed245da4 base::MessageLoop::RunTask()
#19 0x00ffed246978 base::MessageLoop::DeferOrRunPendingTask()
#20 0x00ffed246b4c base::MessageLoop::DoWork()
#21 0x00ffed2f4248 base::MessagePumpLibevent::Run()
#22 0x00ffed279810 base::RunLoop::Run()
#23 0x00ffed2a47f4 base::Thread::Run()
#24 0x00ffeb189ac0 content::BrowserProcessSubThread::IOThreadRun()
#25 0x00ffed2a4c78 base::Thread::ThreadMain()
#26 0x00ffed2ed858 base::(anonymous namespace)::ThreadFunc()
#27 0x00ffe7fa6b9c start_thread
#28 0x00ffe8261d7c __thread_start


build chromium gn_configs as follows:
GN_CONFIG = {
google_api_key = "AIzaSyDxKL42zsPjbke5O8_rPVpVrLrJ8aeE9rQ"
google_default_client_id =
    "595013732528-llk8trb03f0ldpqq6nprjp1s79596646.apps.googleusercontent.com"
google_default_client_secret = "5ntt6GbbkjnTVXx-MSxbmx5e"
clang_use_chrome_plugins = false
enable_hangout_services_extension = true
enable_nacl = false
enable_nacl_nonsfi = false
enable_swiftshader = false
enable_widevine = false
fatal_linker_warnings = false
ffmpeg_branding = "Chrome"
fieldtrial_testing_like_official_build = true
is_debug = false
is_clang = false
link_pulseaudio = true
linux_use_bundled_binutils = false
proprietary_codecs = true
remove_webcore_debug_symbols = true
symbol_level = 0
treat_warnings_as_errors = false
use_allocator = "tcmalloc"
use_cups = true
use_gnome_keyring = false
use_gold = false
use_gtk3 = true
use_kerberos = true
use_pulseaudio = true
use_sysroot = false
}
Project Member

Comment 9 by sheriffbot@chromium.org, Jul 9

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Cc: vamshi.kommuri@chromium.org
Components: Build
Labels: TE-NeedsTriageHelp
As per comment#8 the issue involves in building chromium, which is out of scope for us to do and proceed further. Hence adding appropriate component and requesting someone from from Devteam to have a look into this issue and help in further triaging it, adding label "TE-NeedsTriageHelp".

Thanks!
Hi, The problem has been found out.
Since node_modules cannot be obtained by gclient runhooks, I replaced it with npm install.
Status: WontFix (was: Unconfirmed)

Sign in to add a comment