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

Issue 653406 link

Starred by 4 users

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Oct 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Latest chromium build doesn't startup and gives me an error on the command line

Reported by patently.paul@gmail.com, Oct 6 2016

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/52.0.2743.116 Chrome/52.0.2743.116 Safari/537.36

Steps to reproduce the problem:
1. run the latest chromium-binary from https://download-chromium.appspot.com/ (Build revision: 423444)

What is the expected behavior?
It starts up

What went wrong?
It doesn't and gives me this as output

patently@Kachel:~$ ~/somedir/chrome-linux/chrome --user-data-dir=/home/someuser/.config/chromium-canary
[1006/083405:ERROR:icu_util.cc(173)] Invalid file descriptor to ICU data received.
[1006/083405:FATAL:content_main_runner.cc(691)] Check failed: base::i18n::InitializeICU(). 
#0 0x55fae62638be base::debug::StackTrace::StackTrace()
#1 0x55fae62764ab logging::LogMessage::~LogMessage()
#2 0x55fae5f3e40c content::ContentMainRunnerImpl::Initialize()
#3 0x55fae5f3d30a content::ContentMain()
#4 0x55fae4da58ed ChromeMain
#5 0x7f704f886830 __libc_start_main
#6 0x55fae4da57bd <unknown>

Abgebrochen (Speicherabzug geschrieben)
patently@Kachel:~$

Did this work before? Yes Probably the chromium version fro yesterday

Chrome version:   Channel: canary
OS Version: Linux Kachel 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:42:33 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
Flash Version:
 
*from
Ive tried the latest chromium (revision:423476) and it still doesn't work

patently@Kachel:~$ sh chromium.sh
[1006/110815:ERROR:icu_util.cc(173)] Invalid file descriptor to ICU data received.
[1006/110815:FATAL:content_main_runner.cc(691)] Check failed: base::i18n::InitializeICU(). 
#0 0x55ac6e072ace base::debug::StackTrace::StackTrace()
#1 0x55ac6e0856bb logging::LogMessage::~LogMessage()
#2 0x55ac6dd4cf5c content::ContentMainRunnerImpl::Initialize()
#3 0x55ac6dd4be5a content::ContentMain()
#4 0x55ac6cbb3a6d ChromeMain
#5 0x7f72615ac830 __libc_start_main
#6 0x55ac6cbb393d <unknown>

Aborted (core dumped)
patently@Kachel:~$
Also affects windows.  Chromium builds NO LONGER RUN on Windows.

debug.log shows:

[1006/081342:ERROR:icu_util.cc(173)] Invalid file descriptor to ICU data received.
[1006/081342:FATAL:icu_util.cc(292)] Check failed: result. 
Backtrace:
	GetHandleVerifier [0x000007FEEBF25011+421201]
	RelaunchChromeBrowserWithNewCommandLineIfNeeded [0x000007FEEBEB393A+2263866]
	GetHandleVerifier [0x000007FEEC2BE692+4195282]
	ovly_debug_event [0x000007FEEBB85594+1912420]
	ovly_debug_event [0x000007FEEBB84E01+1910481]
	ChromeMain [0x000007FEEAD49C51+209]
	(No symbol) [0x000000013FC25678]
	(No symbol) [0x000000013FC22D08]
	IsSandboxedProcess [0x000000013FC7CD93+125371]
	BaseThreadInitThunk [0x00000000774D59CD+13]
	RtlUserThreadStart [0x000000007760A2E1+33]



debug.log
664 bytes View Download
scottmg points out that "icudtl.dat" next to the binary is missing
Cc: kerz@chromium.org
Labels: -Pri-2 Pri-1
Owner: chenwilliam@chromium.org
Status: Assigned (was: Unconfirmed)
I think https://chromium.googlesource.com/chromium/src/+/baf98fcec2132efbdf404f9dff40de42703b65bf probably broke this.

I don't know how that file works, but I'm guessing repeated entries aren't allowed, and the different archives should have instead been added to the existing entry for icudtl.dat.
Status: Started (was: Assigned)
Sorry about this - submitting a CL to fix this right away.

Comment 9 by 7cher...@gmail.com, Oct 6 2016

Same problem on windows 10 with 64 bits builds below
- 423420
- 423516
- 423530
- 423612
With an easy dichotomy process I detected that 
- last build OK is 423180
- first build KO is 423196

Downloads taken from http://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Win_x64/

I hope it will help fix the bug.

Thanks
Status: Fixed (was: Started)
I reverted my CL[1] and I checked that the latest Chromium Linux build is now working[2]. Please let me know if there's any issues with a build after commit position 423689. Thanks.

[1] https://codereview.chromium.org/2399173002/

[2] http://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Linux_x64/423689/
chenwilliam@, Thanks for the fix !

Chromedriver bots are back to green.
Thanks a lot ! Bug is fixed on windows too !

Sign in to add a comment