How to resolve error “Insufficient memory to continue the execution of the program.” when debugging Azure Functions locally?

This post was most recently updated on February 5th, 2021.

This article describes a solution to an error “Insufficient memory to continue the execution of the program.” I was debugging an Azure Function locally and ran into it – it stopped my Azure Function from starting at all.

So, this is what I got:

Insufficient memory to continue the execution of the program.

Ohh… kay..? My development machines have plenty of RAM, surely enough to run an Azure Function!

Hell, I’m sure I have enough memory to have Google Chrome running while debugging a pesky Azure Function. So what gives?

How to resolve the error?

Okay, okay. So it’s actually super simple and the error is just misleading.

Not the first time that’s the case, right? :)

Anyway, chances are that you have empty values in your local.settings.json file. Something like shown below:

This’ll throw Azure Functions runtime off. Weirdly, this seems to have been fixed in 2019 and merged in DEV branch of Azure Functions runtime in February 2020 – but it seems to still occur with current version.

Just make sure you only have entries with at least the key set up!

And hey – if you have an application setting with an empty key (but the value set), you’ll get an error like this:

Just for the record, here’s the error once more:

String cannot be of zero length. (Parameter 'variable')

Just fill the key for your application setting entries!

With that, you should be good! :)

References

• https://github.com/Azure/azure-functions-core-tools/issues/1732
• https://github.com/Azure/azure-functions-core-tools/pull/1735

• Author
• Recent Posts

Antti K. Koskela

Developer / Speaker / Consultant at Koskila / Etteplan Oyj / Norppandalotti Software Co / Alter - Experience Ideas Ltd.

Antti Koskela is a proud digital native nomadic millennial full stack developer (is that enough funny buzzwords? That's definitely enough funny buzzwords!), who works as a Cloud Solutions Architect for Etteplan Oyj, an engineering company that employs something like 700 devs building and fixing anything even half-digital.

He's been a developer from 2004 (starting with PHP and Java), and he's been working on .NET projects, Azure, Office 365, SharePoint and a lot of other stuff. He's also Microsoft MVP for Office Development.

This is his personal professional (e.g. professional, but definitely personal) blog.

Latest posts by Antti K. Koskela (see all)

• HttpContext.WebSockets.IsWebSocketRequest always null in .NET Core? - July 27, 2021
• Docker-compose fails on Windows with “Error while fetching server API version: (2, ‘CreateFile’, ‘The system cannot find the file specified.’)” - July 20, 2021
• Azure DevOps suddenly 404s for your project? Easy fix! - July 13, 2021