Bug 52686 - crash webserver
Summary: crash webserver
Status: NEW
Alias: None
Product: Runtime
Classification: Mono
Component: Debugger ()
Version: 4.6.0 (C8)
Hardware: PC Linux
: --- normal
Target Milestone: ---
Assignee: Zoltan Varga
Depends on:
Reported: 2017-02-22 20:32 UTC by Roman
Modified: 2017-02-22 20:32 UTC (History)
2 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report for Bug 52686 on GitHub or Developer Community if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: GitHub Markdown or Developer Community HTML
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:

Description Roman 2017-02-22 20:32:14 UTC
STATE CUE CARD: (? means a positive number, usually 1 or 2, * means any number)
	0x0	- starting (GOOD, unless the thread is running managed code)
	0x1	- running (BAD, unless it's the gc thread)
	0x2	- detached (GOOD, unless the thread is running managed code)
	0x?03	- async suspended (GOOD)
	0x?04	- self suspended (GOOD)
	0x?05	- async suspend requested (BAD)
	0x?06	- self suspend requested (BAD)
	0x*07	- blocking (GOOD)
	0x?08	- blocking with pending suspend (GOOD)
--thread 0x7f35340008e0 id 0x7f35620ba700 [(nil)] state 1  
--thread 0x7f35400008e0 id 0x7f35622bb700 [(nil)] state 1  
--thread 0x7f353c0008e0 id 0x7f35624bc700 [(nil)] state 1  GC INITIATOR
--thread 0x7f35480008e0 id 0x7f35626bd700 [(nil)] state 105  
--thread 0x7f35440008e0 id 0x7f35628be700 [(nil)] state 1  
--thread 0x7f35500008e0 id 0x7f35628ff700 [(nil)] state 1  
--thread 0x7f354c0008e0 id 0x7f3562940700 [(nil)] state 1  
--thread 0x7f35580008e0 id 0x7f3562b41700 [(nil)] state 1  
--thread 0x7f35540008e0 id 0x7f3563e5f700 [(nil)] state 1  
--thread 0x7f355c0008e0 id 0x7f3564060700 [(nil)] state 1  
--thread 0x1586290 id 0x7f3567639740 [(nil)] state 1  
WAITING for 1 threads, got 0 suspended
suspend_thread suspend took 200 ms, which is more than the allowed 200 ms

  at <unknown> <0xffffffff>
  at Mono.WebServer.InitialWorkerRequest.ReadRequestLine () <IL 0x00025, 0x00197>
  at Mono.WebServer.InitialWorkerRequest.GetRequestLine () <IL 0x00005, 0x000f3>
  at Mono.WebServer.InitialWorkerRequest.ReadRequestData () <IL 0x00002, 0x00077>
  at Mono.WebServer.XSP.XSPWorker.ReadCB (System.IAsyncResult) <IL 0x0002e, 0x001cf>
  at System.Net.Sockets.SocketAsyncResult/<Complete>c__AnonStorey0.<>m__0 (object) [0x00000] in /tmp/buildd/mono-
  at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem () [0x00019] in /tmp/buildd/mono-
  at System.Threading.ThreadPoolWorkQueue.Dispatch () [0x00096] in /tmp/buildd/mono-
  at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback () [0x00000] in /tmp/buildd/mono-
  at (wrapper runtime-invoke) <Module>.runtime_invoke_bool (object,intptr,intptr,intptr) <IL 0x0001f, 0x00141>

Native stacktrace:

	/usr/bin/mono() [0x4accca]
	/lib/x86_64-linux-gnu/libpthread.so.0(+0x11390) [0x7f3566b26390]
	/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x38) [0x7f356656b428]
	/lib/x86_64-linux-gnu/libc.so.6(abort+0x16a) [0x7f356656d02a]
	/usr/bin/mono() [0x65a909]
	/usr/bin/mono() [0x65ab17]
	/usr/bin/mono() [0x65abc2]
	/usr/bin/mono() [0x6510ec]
	/usr/bin/mono() [0x65217a]
	/usr/bin/mono() [0x4c86ce]
	/usr/bin/mono(mono_g_hash_table_foreach+0x5c) [0x5bef4c]
	/usr/bin/mono() [0x4cbab8]
	/usr/bin/mono() [0x4d7e34]
	/usr/bin/mono() [0x4d8236]
	/usr/bin/mono() [0x4d88b4]
	/usr/bin/mono() [0x58ff67]
	/usr/bin/mono() [0x5105fe]
	/usr/bin/mono() [0x425efc]
	/usr/bin/mono() [0x4af809]
	/usr/bin/mono() [0x4b0230]

Debug info from gdb:

Could not attach to process.  If your uid matches the uid of the target
process, check the setting of /proc/sys/kernel/yama/ptrace_scope, or try
again as the root user.  For more details, see /etc/sysctl.d/10-ptrace.conf
ptrace: Дію заборонено.
No threads.

Got a SIGABRT while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries 
used by your application.