Bug 60977 - ves_icall_System_Diagnostics_Process_ShellExecuteEx_internal
Summary: ves_icall_System_Diagnostics_Process_ShellExecuteEx_internal
Status: RESOLVED ANSWERED
Alias: None
Product: Runtime
Classification: Mono
Component: General ()
Version: master
Hardware: PC Linux
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2017-12-04 20:20 UTC by pr0vieh
Modified: 2018-01-05 01:13 UTC (History)
4 users (show)

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


Attachments
completeStackTrace (62.89 KB, text/plain)
2017-12-04 20:20 UTC, pr0vieh
Details


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 on GitHub or Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED ANSWERED

Description pr0vieh 2017-12-04 20:20:20 UTC
Created attachment 25904 [details]
completeStackTrace

Hi,

my tool is craching after startup with this Stack: @Master since about 28.11.

can someone look at this?

Stacktrace:

  at <unknown> <0xffffffff>
  at (wrapper managed-to-native) System.Diagnostics.Process.ShellExecuteEx_internal (System.Diagnostics.ProcessStartInfo,System.Diagnostics.Process/ProcInfo&) [0x00000] in <b7eb18babc0245f8843dc6ea18fa4175#ED67B79F-9F22-CA4B-3B48-E620F81CBADF>:0
  at System.Diagnostics.Process.StartWithShellExecuteEx (System.Diagnostics.ProcessStartInfo) [0x000be] in <b7eb18babc0245f8843dc6ea18fa4175#ED67B79F-9F22-CA4B-3B48-E620F81CBADF>:0
  at System.Diagnostics.Process.Start () [0x00032] in <b7eb18babc0245f8843dc6ea18fa4175#ED67B79F-9F22-CA4B-3B48-E620F81CBADF>:0
  at (wrapper remoting-invoke-with-check) System.Diagnostics.Process.Start () [0x00031] in <b7eb18babc0245f8843dc6ea18fa4175#ED67B79F-9F22-CA4B-3B48-E620F81CBADF>:0
  at System.Diagnostics.Process.Start (System.Diagnostics.ProcessStartInfo) [0x0001b] in <b7eb18babc0245f8843dc6ea18fa4175#ED67B79F-9F22-CA4B-3B48-E620F81CBADF>:0
  at System.Diagnostics.Process.Start (string,string) [0x00007] in <b7eb18babc0245f8843dc6ea18fa4175#ED67B79F-9F22-CA4B-3B48-E620F81CBADF>:0
  at Majestic12.WebCrawler.Exec (string,string) [0x00000] in <4434327b29a24afc93fd6e0bd078f310#ED67B79F-9F22-CA4B-3B48-E620F81CBADF>:0
  at Majestic12.WebCrawler.GetMonoData (string,string) [0x0002b] in <4434327b29a24afc93fd6e0bd078f310#ED67B79F-9F22-CA4B-3B48-E620F81CBADF>:0
  at Majestic12.WebCrawler.FinaliseDataBucket (Majestic12.URLbucket) [0x0058d] in <4434327b29a24afc93fd6e0bd078f310#ED67B79F-9F22-CA4B-3B48-E620F81CBADF>:0
  at Majestic12.WebCrawler.ArchiveManager () [0x0045a] in <4434327b29a24afc93fd6e0bd078f310#ED67B79F-9F22-CA4B-3B48-E620F81CBADF>:0
  at System.Threading.ThreadHelper.ThreadStart_Context (object) [0x00014] in <42737e5728fe4ea0a6c30c67432e6f45#ED67B79F-9F22-CA4B-3B48-E620F81CBADF>:0
  at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext,System.Threading.ContextCallback,object,bool) [0x00071] in <42737e5728fe4ea0a6c30c67432e6f45#ED67B79F-9F22-CA4B-3B48-E620F81CBADF>:0
  at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext,System.Threading.ContextCallback,object,bool) [0x00000] in <42737e5728fe4ea0a6c30c67432e6f45#ED67B79F-9F22-CA4B-3B48-E620F81CBADF>:0
  at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext,System.Threading.ContextCallback,object) [0x0002b] in <42737e5728fe4ea0a6c30c67432e6f45#ED67B79F-9F22-CA4B-3B48-E620F81CBADF>:0
  at System.Threading.ThreadHelper.ThreadStart () [0x00008] in <42737e5728fe4ea0a6c30c67432e6f45#ED67B79F-9F22-CA4B-3B48-E620F81CBADF>:0
  at (wrapper runtime-invoke) object.runtime_invoke_void__this__ (object,intptr,intptr,intptr) [0x0004d] in <42737e5728fe4ea0a6c30c67432e6f45#ED67B79F-9F22-CA4B-3B48-E620F81CBADF>:0
Comment 1 pr0vieh 2017-12-06 20:52:21 UTC
i figured out this is happens when mono start an external process

i think this has something todo with this marge:
https://github.com/mono/mono/pull/5570
Comment 2 Alexander Köplinger [MSFT] 2018-01-05 01:13:55 UTC
Let's track this with https://github.com/mono/mono/issues/6383 which has more details. Thanks!