Memory Leak when creating msgraph client

[erictg]

Explanation

When starting a basic test program for msgraph, go program fails to start with msgraph imported. When monitoring HTOP while the program is running, massive amounts of memory are used up. I have no idea why this is happening, as this is just a rest package. It shouldn't be doing anything that memory intensive.

Steps to reproduce

Run the following.
Note the code does not fail with msgraph commented out and azidentity running. It always fails with msgraph.

package main

import (
	"fmt"
        "log"
	msgraphsdk "github.com/microsoftgraph/msgraph-sdk-go"
)

func main() {
	log.Println("trying to get creds...")
	// get credentials
	// cred, err := azidentity.NewClientSecretCredential(tenantID, clientID, clientSecret, nil)
	// if err != nil {
	// 	log.Fatal(err)
	// }

	// log.Println(cred)

	log.Println("created credential")

	client, err := msgraphsdk.NewGraphServiceClientWithCredentials(nil, []string{})
	if err != nil {
		log.Fatal(err)
	}
}

Relevant version numbers:

(note I am intentionally using older versions in order to use azidentity 1.3.0-beta.1 for az workload identity. This specific case is not using workload identity, but exists in the same code base)

• github.com/microsoftgraph/msgraph-sdk-go v0.57.0
• github.com/Azure/azure-sdk-for-go/sdk/azcore v1.2.0
• github.com/Azure/azure-sdk-for-go/sdk/azidentity v1.3.0-beta.1
• github.com/Azure/azure-sdk-for-go/sdk/internal v1.0.0
• github.com/Azure/azure-sdk-for-go/sdk/storage/azblob v0.6.1
• github.com/AzureAD/microsoft-authentication-library-for-go v0.7.0

Impact

This is completely blocking my progress in development. I may end up writing custom rest calls to msgraph in the meantime because this is unusable

Related Issues

• build hangs when importing package #312 may be related

[rkodev]

Hi @erictg, The current issue is not a result of a memory leak but is because of the size of the SDK. While we are working continuously on improving the sdk perfomance, this is an issue that was reported and worked on here.

It would be helpful to share the details of the device running the package i.e RAM and CPU.

One of the options currently is using the kiota for a self serve style SDK where you get to choose only the packages that you want for the SDK. Please keep updating to the latest weekly release as performance improvements are an ongoing task.

[erictg]

My computer has 16Gb of ram and an i7 processor running fedora 37 and Go 1.19

I don't understand why the SDK would consume 16Gb of ram, that really doesn't seem right even with a large SDK.

[rkodev]

Hi @erictg, What disk drive are you using HDD/SSD, could you please share the filesystem usage while running the build.

[erictg]

@rkodev I am using an SSD and the file system is btrfs

[andrueastman]

@erictg Any chance you can confirm if this is still an issue for you on the latest sdk version?

[microsoft-github-policy-service]

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.