Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

AddOtlpExporter seems to be causing a crash?

See original GitHub issue

Bug Report

        <PackageReference Include="OpenTelemetry.Extensions.Hosting" Version="1.0.0-rc1.1" />
        <PackageReference Include="OpenTelemetry.Instrumentation.AspNetCore" Version="1.0.0-rc1.1" />
        <PackageReference Include="OpenTelemetry" Version="1.0.0-rc1.1" />
        <PackageReference Include="OpenTelemetry.Exporter.OpenTelemetryProtocol" Version="1.0.0-rc1.1" />

Running on net5.0

Symptom

It seems like when I use the following in my ASP.net Core project:

            services.AddOpenTelemetryTracing((builder) =>
            {
                builder
                    .AddSource(projectName)
                    .SetSampler(new AlwaysOnSampler())
                    .AddAspNetCoreInstrumentation()
                    .AddOtlpExporter();
            });

I get a segfault with the message: Process finished with exit code 139.

Note: If I remove AddOtlpExporter() everything boots fine.

What is the expected behavior? Normal application bootup.

What is the actual behavior? The segfault.

Issue Analytics

State:
Created 3 years ago
Reactions:1
Comments:16 (10 by maintainers)

Top GitHub Comments

1reaction

alanwestcommented, Dec 9, 2020

Ah, yes, sorry I had missed your previous statement regarding Ubuntu. I’m able to reproduce what you’re seeing. Still not yet sure why, but I can confirm that #1634 does not resolve this issue.

1reaction

edubsicommented, Nov 25, 2020

Sadly we just ran into the same problem. Added unhandled Task & App Exception Handling to maybe catch & log the exceptions which did not help. For us it looks like the crash happens when the first trace/log/metric is exported.