Adding proper component for someone from the respective team to take a look into this.

I can't seem to reproduce this. Are you running headless in a special environment (e.g., AWS lambda)?

Could you also try with an official Chrome package instead of headless shell?

No it's just ubuntu server and lastest headless_shell (built from git today)
crashed (it takes some time to reproduce) with a lot of [1028/190339.197904:WARNING:ipc_message_attachment_set.cc(49)] MessageAttachmentSet destroyed with unconsumed attachments: 0/1

Have tried with chromium-browser:
chromium-browser --version
Chromium 62.0.3202.62 Built on Ubuntu , running on Ubuntu 17.04

with --headless param - the same warnings but now crashes so far...

Thank you for providing more feedback. Adding requester "skyostil@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Also, I can only reproduce the bug with the "is_debug=false" flag (sometimes chrome doesnt crash, just stops responding to devtools commands)

Still not fixed even with one "thread" on lastest build:
https://www.googleapis.com/download/storage/v1/b/chromium-browser-snapshots/o/Linux_x64%2F526094%2Fchrome-linux.zip?alt=media

./chrome --headless --remote-debugging-port=1234 --remote-debugging-address=0.0.0.0

DevTools listening on ws://0.0.0.0:1234/devtools/browser/d383dddc-5654-4382-8412-460d5a241d01
[1223/022435.024820:ERROR:gpu_process_transport_factory.cc(1043)] Lost UI shared context.
[1223/022435.076612:ERROR:command_buffer_proxy_impl.cc(114)] ContextResult::kFatalFailure: Shared memory handle is not valid
[1223/022441.989185:WARNING:spdy_session.cc(2899)] Received HEADERS for invalid stream 13
[1223/022442.012966:WARNING:spdy_session.cc(2899)] Received HEADERS for invalid stream 15
[1223/022443.980493:WARNING:spdy_session.cc(2899)] Received HEADERS for invalid stream 13
[1223/022443.998603:WARNING:spdy_session.cc(2899)] Received HEADERS for invalid stream 15
[1223/022446.045759:WARNING:spdy_session.cc(2899)] Received HEADERS for invalid stream 13
[1223/022448.009861:WARNING:spdy_session.cc(2899)] Received HEADERS for invalid stream 13
[1223/022448.034498:WARNING:spdy_session.cc(2899)] Received HEADERS for invalid stream 15
Received signal 11 SEGV_MAPERR 000000000000
#0 0x5560fea8166c base::debug::StackTrace::StackTrace()
#1 0x5560fea811d1 base::debug::(anonymous namespace)::StackDumpSignalHandler()
#2 0x7f1886fcb670 <unknown>
#3 0x5560fda16607 content::RenderProcessHostImpl::Cleanup()
#4 0x5560fd88c634 content::KeepAliveHandleFactory::Context::~Context()
#5 0x5560fd88c73b content::KeepAliveHandleFactory::KeepAliveHandleImpl::~KeepAliveHandleImpl()
#6 0x5560fd88c4b7 [1223/022454.892576:WARNING:spdy_session.cc(2899)] Received HEADERS for invalid stream 13
mojo::BindingSetBase<>::OnConnectionError()
#7 0x5560ff1ada72 mojo::InterfaceEndpointClient::NotifyError()
#8 0x5560ff1b4c42 mojo::internal::MultiplexRouter::ProcessNotifyErrorTask()
#9 0x5560ff1b312f mojo::internal::MultiplexRouter::ProcessTasks()
#10 0x5560ff1b1f52 mojo::internal::MultiplexRouter::OnPipeConnectionError()
#11 0x5560ff1abfa4 mojo::Connector::HandleError()
#12 0x5560ff1bdd4a mojo::SimpleWatcher::OnHandleReady()
#13 0x5560fea829df base::debug::TaskAnnotator::RunTask()
#14 0x5560fea9bed7 base::MessageLoop::RunTask()
#15 0x5560fea9c3d8 base::MessageLoop::DoWork()
#16 0x5560fea9e9bf base::(anonymous namespace)::WorkSourceDispatch()
#17 0x7f1884eec377 g_main_context_dispatch
#18 0x7f1884eec5e0 <unknown>
#19 0x7f1884eec68c g_main_context_iteration
#20 0x5560fea9e882 base::MessagePumpGlib::Run()
#21 0x5560feabe235 base::RunLoop::Run()
#22 0x5560fd799271 content::BrowserMainLoop::MainMessageLoopRun()
#23 0x5560fd799073 content::BrowserMainLoop::RunMainMessageLoopParts()
#24 0x5560fd79bf02 content::BrowserMainRunnerImpl::Run()
#25 0x5561029762bf headless::HeadlessContentMainDelegate::RunProcess()
#26 0x5560fe7be3d0 content::RunNamedProcessTypeMain()
#27 0x5560fe7bede5 content::ContentMainRunnerImpl::Run()
#28 0x5560fe7c809f service_manager::Main()
#29 0x5560fe7bd8f1 content::ContentMain()
#30 0x55610297544a headless::(anonymous namespace)::RunContentMain()
#31 0x5561029754be headless::HeadlessBrowserMain()
#32 0x5560fe7c4eda headless::HeadlessShellMain()
#33 0x5560fd03b1c5 ChromeMain
#34 0x7f188104a3f1 __libc_start_main
#35 0x5560fd03b02a _start
  r8: 0000000000000000  r9: 00001aae23bdc810 r10: 00001aae23afeb60 r11: 0000000000000246
 r12: 00007fff1edf02c8 r13: 00001aae24e3b388 r14: 00001aae24706d80 r15: 0000000000000000
  di: 00001aae24e3b388  si: 0000000000000000  bp: 00007fff1edf0310  bx: 0000000000000000
  dx: 00001aae24e3b388  ax: 0000000000000000  cx: 0000000000000000  sp: 00007fff1edf0290
  ip: 00005560fda16607 efl: 0000000000010246 cgf: 002b000000000033 erf: 0000000000000004
 trp: 000000000000000e msk: 0000000000000000 cr2: 0000000000000000
[end of stack trace]
Calling _exit(1). Core file will not be generated.

Deleted: test.js 1.5 KB

test.js 1.5 KB View Download

As per comment#6 this is reproducible only with the "is_debug=false" flag.This might be related to debug build.

@skyostil: Could you please help in debugging this further.

Thanks!

Sorry, still unable to reproduce with Chrome 68.0.3438.3. Please make sure you're using the official Debian packages instead of builds taken off the build server since those may not have passed QA.