Bug 39905 - Assertion at mono-threads.c:326, condition `result' not met
Summary: Assertion at mono-threads.c:326, condition `result' not met
Status: NEW
Alias: None
Product: Runtime
Classification: Mono
Component: Debugger (show other bugs)
Version: 4.2.0 (C6)
Hardware: PC Linux
: --- normal
Target Milestone: ---
Assignee: Zoltan Varga
URL:
Depends on:
Blocks:
 
Reported: 2016-03-25 01:23 UTC by Kratzer Kevin
Modified: 2016-03-25 01:23 UTC (History)
2 users (show)

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


Attachments

Description Kratzer Kevin 2016-03-25 01:23:46 UTC
I'm experiencing an issue when creating threads in a mono subprocess integrating CEF ( https://bitbucket.org/chromiumembedded/cef/ ) on Xubuntu 15.10, mono 4.2.3.4.
Simple statments like

* new System.Threading.Thread (() => {}).Start ();
* Task.Run (() => {});

Result in the error "* Assertion at mono-threads.c:326, condition `result' not met"
I don't think I can provide a test case for this multi process behaviour.
Maybe you can provide me with some hint on what might cause this error.

> mono --version
Mono JIT compiler version 4.2.3 (Stable 4.2.3.4/832de4b Wed Mar 16 13:19:08 UTC 2016)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
	TLS:           __thread
	SIGSEGV:       altstack
	Notifications: epoll
	Architecture:  amd64
	Disabled:      none
	Misc:          softdebug 
	LLVM:          supported, not enabled.
	GC:            sgen

> apt-cache policy mono-complete 
mono-complete:
  Installed: 4.2.3.4-0xamarin2
  Candidate: 4.2.3.4-0xamarin2
  Version table:
 *** 4.2.3.4-0xamarin2 0
        500 http://download.mono-project.com/repo/debian/ wheezy/main amd64 Packages
        100 /var/lib/dpkg/status
     3.2.8+dfsg-4ubuntu4 0
        500 http://jp.archive.ubuntu.com/ubuntu/ wily/universe amd64 Packages

> cat /proc/version
Linux version 4.2.0-34-generic (buildd@lgw01-54) (gcc version 5.2.1 20151010 (Ubuntu 5.2.1-22ubuntu2) ) #39-Ubuntu SMP Thu Mar 10 22:13:01 UTC 2016

Note You need to log in before you can comment on or make changes to this bug.