This is being posted from a Chromebook running v64, so the UserAgent information in this report is not for the version that has the problem, as I had to restore the chromebook back to an earlier version due to this issue. This bug report is what is happening for v67 as listed in the report.

Can you provide a crash id from chrome://crashes ?

May be a dupe of this restricted issue: 824630

Issue also spotted on a Toshiba Chromebook 2 2015 (i3).

Crash ID:59a019d8c8f1d3bf
OS Version:67.0.3396.87

Stack Quality100%Show frame trust levels
0x000055a35fbca373	(chrome -ordinal.h:304 )	app_list::(anonymous namespace)::UpdateSyncItemFromAppItem(ChromeAppListItem const*, app_list::AppListSyncableService::SyncItem*)
0x000055a35fbcad5c	(chrome -app_list_syncable_service.cc:633 )	app_list::AppListSyncableService::UpdateSyncItem(ChromeAppListItem const*)
0x000055a35fbcf520	(chrome -app_list_syncable_service.cc:287 )	app_list::AppListSyncableService::ModelUpdaterDelegate::OnAppListItemUpdated(ChromeAppListItem*)
0x000055a35fbd4867	(chrome -chrome_app_list_model_updater.cc:522 )	ChromeAppListModelUpdater::OnItemUpdated(mojo::StructPtr<ash::mojom::AppListItemMetadata>)
0x000055a35fbc6120	(chrome -app_list_client_impl.cc:120 )	<name omitted>
0x000055a35bdfd29e	(chrome -app_list.mojom.cc:4280 )	ash::mojom::AppListClientStubDispatch::Accept(ash::mojom::AppListClient*, mojo::Message*)
0x000055a35d1c358c	(chrome -interface_endpoint_client.cc:419 )	mojo::InterfaceEndpointClient::HandleValidatedMessage(mojo::Message*)
0x000055a35a82f8d3	(chrome -interface_endpoint_client.cc:306 )	mojo::internal::MultiplexRouter::ProcessIncomingMessage(mojo::internal::MultiplexRouter::MessageWrapper*, mojo::internal::MultiplexRouter::ClientCallBehavior, base::SequencedTaskRunner*)
0x000055a35a82f3f9	(chrome -multiplex_router.cc:589 )	mojo::internal::MultiplexRouter::Accept(mojo::Message*)
0x000055a35a82ec62	(chrome -connector.cc:443 )	mojo::Connector::ReadAllAvailableMessages()
0x000055a35d1d62d5	(chrome -callback.h:124 )	mojo::SimpleWatcher::OnHandleReady(int, unsigned int, mojo::HandleSignalsState const&)
0x000055a35a8175b8	(chrome -callback.h:95 )	base::MessageLoop::RunTask(base::PendingTask*)
0x000055a35a819a21	(chrome -message_loop.cc:364 )	base::MessagePumpLibevent::Run(base::MessagePump::Delegate*)
0x000055a35cd2a36f	(chrome -run_loop.cc:130 )	ChromeBrowserMainParts::MainMessageLoopRun(int*)
0x000055a35b452970	(chrome -browser_main_loop.cc:989 )	content::BrowserMainLoop::RunMainMessageLoopParts()
0x000055a35b455861	(chrome -browser_main_runner.cc:161 )	content::BrowserMainRunnerImpl::Run()
0x000055a35b44ab5d	(chrome -browser_main.cc:46 )	content::BrowserMain(content::MainFunctionParams const&)
0x000055a35cd0ddb3	(chrome -content_main_runner.cc:633 )	content::ContentMainRunnerImpl::Run()
0x000055a35cd1a4cf	(chrome -main.cc:452 )	service_manager::Main(service_manager::MainParams const&)
0x000055a35a9603d8	(chrome -content_main.cc:19 )	ChromeMain
0x000077cf9aa74735	(libc-2.23.so -libc-start.c:289 )	__libc_start_main
0x000055a35a954438	(chrome + 0x011cd438 )	_start
0x00007ffccf963dd7		

Issue 858886 has been merged into this issue.

User Feedback reports from latest M67 Stable (with logs):
https://listnr.corp.google.com/report/85525327732
https://listnr.corp.google.com/report/85523790516
https://listnr.corp.google.com/report/85523932627
https://listnr.corp.google.com/report/85514528369

https://crash.corp.google.com/browse?q=EXISTS+%28SELECT+1+FROM+UNNEST%28CrashedStackTrace.StackFrame%29+WHERE+FunctionName%3D%27app_list%3A%3A%28anonymous+namespace%29%3A%3AUpdateSyncItemFromAppItem%28ChromeAppListItem+const*%2C+app_list%3A%3AAppListSyncableService%3A%3ASyncItem*%29%27%29#samplereports

Starting ~ Jun 17.
Regression in M67

Issue 863779 has been merged into this issue.

This bug is marked as a 68 stable release blocker, and we are coming up on stable in a couple weeks, so we need to get it fixed or reclassify it.

I'm still seeing user feedback reports about this issue on M67 Stable, but am not seeing any such reports about "launcher" or "search button" on M68 Dev/Beta.

If this was in 67 or earlier, we cannot block the 68 stable on it.

We can still take a merge if we can find a fix though, whom would be a good owner for this?

There is no crashes in M68 (only few in 68.0.3397.0 long time ago Apr 20). I assume we fixed this in one of many CLs for app list stabilization.

After the play store got re-enable and I was able to install my apps, this started happening on 68 (stable) on an Acer R11