Bug 41802 - Unexpected "failed to get 100ns ticks" in program output (mono-4.4.0.142,Windows)
Summary: Unexpected "failed to get 100ns ticks" in program output (mono-4.4.0.142,Wind...
Status: ASSIGNED
Alias: None
Product: Runtime
Classification: Mono
Component: General (show other bugs)
Version: 4.4.0 (C7)
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: johan.lorensson
URL:
Depends on:
Blocks:
 
Reported: 2016-06-14 15:04 UTC by Andrey Akinshin
Modified: 2016-09-07 18:35 UTC (History)
5 users (show)

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


Attachments

Description Andrey Akinshin 2016-06-14 15:04:45 UTC
*** Repro ***

using System;
using System.CodeDom.Compiler;
using Microsoft.CSharp;

namespace MyApplication
{
    class Program
    {
        static void Main()
        {
            var src = @"public class MyClass { public string Execute() { return ""Hooray!""; } }";
            var result = new CSharpCodeProvider()
                .CompileAssemblyFromSource(new CompilerParameters {GenerateInMemory = true}, src);
            var type = result.CompiledAssembly.GetType("MyClass");            
            var instance = Activator.CreateInstance(type);
            var method = type.GetMethod("Execute");
            var hooray = method.Invoke(instance, null);
            Console.WriteLine(hooray);
        }
    }
}

*** Expected Results ***
Hooray!

*** Actual Results ***
failed to get 100ns ticks
failed to get 100ns ticks
failed to get 100ns ticks
failed to get 100ns ticks
Hooray!

*** Environment ***
Windows 10 (Microsoft Windows [Version 10.0.10586])
mono-4.4.0.142 (downloaded from http://download.mono-project.com/archive/4.4.0/windows-installer/mono-4.4.0.142-gtksharp-2.12.38-win32-0.msi)
Comment 1 Nathan Phillip Brink (binki) 2016-08-03 19:01:44 UTC
Maybe it’s fixed in https://github.com/mono/mono/commit/cfc1228c9ba5c89188785332bf29af9183d34a43 which isn’t in mono-4.4.2.11 but is in mono-4.6.0.125.

I also see this message when running the bundled nuget in mono-4.4.1 amd64.
Comment 2 Jon Purdy 2016-09-07 18:35:47 UTC
Repro’d with 4.4 and confirmed fixed in 4.6. We should probably backport it; assigning Johan.

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