Google.Apis.Bigquery.v2 hard crash on dotnet core and linux docker

I am not quite sure why yet, but it seems that we get a hard crash when executing this piece of code within a linux docker container :

			BigqueryService bqservice = Connect(context);

			if (bqservice == null)
				return null;

			var query = new QueryRequest()
			{
				Query = sql,
				DefaultDataset = new DatasetReference()
				{
					DatasetId = context.DatasetId,
					ProjectId = context.ProjectId
				},
				TimeoutMs = 600000,
				MaxResults = 100000,
				UseQueryCache = true
			};

			JobsResource.QueryRequest job = bqservice.Jobs.Query(query, context.ProjectId);

			try
			{

				QueryResponse result = job.Execute();//hard crash, no stack trace, the main process of the container dies, and it kills the container

We are building our solution off of microsoft/aspnetcore-build:2.0 and deploying using microsoft/aspnetcore:2.0 images.

The SQL is valid SQL and can be executed within the BigQuery query editor, and we are certain that the DatasetId and ProjectId are valid.

We are using Version=“1.29.1.967”. We’ll try updating to see if that fixes anything. I’m tempted to simply use google cloud api, see if it fixes anything, but I’m worried that I will just be delaying/hidding the potential problem and not actually fix it.

[AlexandreOuellet]

(Agreed that it’s much easier to use, but did not exist at the time this code was written)

And we’ve found the bug : Turns out it’s a weird interaction/conflict with LibSSL and LibCrypto. We have an in-house dll that is using different versions (not statically linked) as the one used in google api, and when we load it first, it somehow interfere with the one for bigquery (likely just the authentication part), and just shuts down.

As for how we came to this conclusion : pure wild guess. Tested removing this lib, and it seems to work. It could also explain our others random crashes that we were getting (this one was the only one that we could reproduce with certainty).

[jskeet]

Aha - yes, I’ve seen that problem in a completely different scenario. Note that this isn’t part of the .NET library; it would be part of one of the base docker images.

I’ll close this issue now as I don’t think it’s related to code in this repo, but let me know if you think I should reopen it.

Thanks so much for reporting the result, and well done for finding it!