New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 714144 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 454513
Owner:
Closed: Dec 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug

Blocking:
issue 722827



Sign in to add a comment

DCHECK hit in extension_pref_value_map.cc:73: Extension nlkncpkkdoccmpiclbokaimcnedabhhm is not registered but accesses pref settings.accessibility

Project Member Reported by emaxx@chromium.org, Apr 21 2017

Issue description

Chrome Version: ToT
OS: Chrome OS

What steps will reproduce the problem?
(1) Build a dcheck_always_on=true build for link and deploy it to a link Chromebook.
(2) Log in, double-click on a PNG file in Files.

What happens instead?
[FATAL:extension_pref_value_map.cc(73)] Check failed: false. Extension nlkncpkkdoccmpiclbokaimcnedabhhm is not registered but accesses pref settings.accessibility (incognito: 0).  http://crbug.com/454513 
#0 0x7f78dcd8f827 base::debug::StackTrace::StackTrace()
#1 0x7f78dcda936d logging::LogMessage::~LogMessage()
#2 0x7f78db70f0cb ExtensionPrefValueMap::CanExtensionControlPref()
#3 0x7f78dea35705 extensions::PreferenceAPIBase::CanExtensionControlPref()
#4 0x7f78dea38877 extensions::preference_helpers::GetLevelOfControl()
#5 0x7f78dea3692b extensions::GetPreferenceFunction::Run()
#6 0x7f78db701cf5 ExtensionFunction::RunWithValidation()
#7 0x7f78db704844 extensions::ExtensionFunctionDispatcher::DispatchWithCallbackInternal()
#8 0x7f78db7042e1 extensions::ExtensionFunctionDispatcher::Dispatch()
#9 0x7f78db7274ef _ZN3IPC8MessageTI29ExtensionHostMsg_Request_MetaSt5tupleIJ31ExtensionHostMsg_Request_ParamsEEvE8DispatchIN10e
xtensions28ExtensionWebContentsObserverES8_N7content15RenderFrameHostEMS8_FvPSA_RKS3_EEEbPKNS_7MessageEPT_PT0_PT1_T2_
#10 0x7f78db7273de extensions::ExtensionWebContentsObserver::OnMessageReceived()
#11 0x7f78de956b40 extensions::ChromeExtensionWebContentsObserver::OnMessageReceived()
#12 0x7f78db5c98ce content::WebContentsImpl::OnMessageReceived()
#13 0x7f78db2db9c3 content::RenderFrameHostImpl::OnMessageReceived()
#14 0x7f78db4b738a content::RenderProcessHostImpl::OnMessageReceived()
#15 0x7f78dd38cec5 IPC::ChannelProxy::Context::OnDispatchMessage()
#16 0x7f78db0df01a _ZN4base8internal7InvokerINS0_9BindStateINS0_18IgnoreResultHelperIMN7content20BrowserMessageFilter8InternalE
FbRKN3IPC7MessageEEEEJ13scoped_refptrIS6_ES8_EEEFvvEE3RunEPNS0_13BindStateBaseE
#17 0x7f78daba0611 _ZNO4base8CallbackIFvvELNS_8internal8CopyModeE1ELNS2_10RepeatModeE1EE3RunEv
#18 0x7f78dce4524d base::debug::TaskAnnotator::RunTask()
#19 0x7f78dcdb1661 base::MessageLoop::RunTask()
#20 0x7f78dcdb19d8 base::MessageLoop::DeferOrRunPendingTask()
#21 0x7f78dcdb1e96 base::MessageLoop::DoWork()
#22 0x7f78dcdb4699 base::MessagePumpLibevent::Run()
#23 0x7f78dcdb12c9 base::MessageLoop::RunHandler()
#24 0x7f78dcddac24 base::RunLoop::Run()
#25 0x7f78dc95f655 ChromeBrowserMainParts::MainMessageLoopRun()
#26 0x7f78db1bedb1 content::BrowserMainLoop::RunMainMessageLoopParts()
#27 0x7f78db1c1acf content::BrowserMainRunnerImpl::Run()
#28 0x7f78db1ba176 content::BrowserMain()
#29 0x7f78dc910f87 content::RunNamedProcessTypeMain()
#30 0x7f78dc911caa content::ContentMainRunnerImpl::Run()
#31 0x7f78de14ca65 service_manager::Main()
#32 0x7f78dc9107c2 content::ContentMain()
#33 0x7f78dab98d4d ChromeMain
#34 0x7f78d860b816 __libc_start_main
#35 0x7f78dab98b19 _start


mtomasz@: Assigning to you for triaging, as the referenced extension is the Gallery extension, and I believe you're one of the OWNERS for it.
 
Cc: yamaguchi@chromium.org weifangsun@chromium.org oka@chromium.org
Components: Platform>Apps>FileManager
Owner: ----
Status: Available (was: Assigned)
Owner: yamaguchi@chromium.org
Assigning to @yamaguchi for triage, as I don't actively work on the code anymore.

Comment 4 by gab@chromium.org, May 25 2017

Blocking: 722827
Labels: -Pri-1 Pri-3
I think this can be Pri 3 because 722827 is also Pri 3.

Comment 6 by emaxx@chromium.org, May 30 2017

Re comment 5: If this bug won't be investigated anytime soon, then I guess we'll have to disable the DCHECK?
This report is unrelated to  issue 722827 . I'm personally often using the Debug builds when working on my features, so these unexpected DCHECKs lead to crashes and require manually commenting them in the code, rebuilding and redeploying Chrome to the test device.
Labels: -Pri-3 Pri-1
No, this isn't P3, this should be at least P1. We should not have DCHECKs in the build that routinely fire, any more than we should allow routine regular crashes.

Also,  bug 722827  is about changing what the build should do by default, it is not a statement about the relative priority of dchecks one way or another.
Owner: fukino@chromium.org
Status: Assigned (was: Available)
It still reproduces.
We're sorry for leaving this. Let me look into it.
Labels: M-65
Mergedinto: 454513
Status: Duplicate (was: Assigned)
I assume this should be fixed for all component extensions.
I reopened  issue 454513  and updated a comment about it.
https://bugs.chromium.org/p/chromium/issues/detail?id=454513#c57

Sign in to add a comment