Bug#1009710: libglfw3: valgrind finds memory leak

[Bérenger]

Package: libglfw3
Version: 3.3.2-1
Severity: minor
Tags: upstream
X-Debbugs-Cc: berengermorel76 at gmail.com

When writting a minimal C program with glfw3, valgrind find leaked
memory.

Code of the program:

```
#include <GLFW/glfw3.h>

int main()
{
	glfwInit();
	glfwTerminate();
}
```

Compiling and running with:
```
clang test.c $(pkg-config --libs glfw3)
valgrind --leak-check=full --show-leak-kinds=all --log-file=log  ./a.out
```

will generate the report showing the leaks. You will need to install
several dbgsym packages to see the whole stacks, though.

-- System Information:
Debian Release: 11.3
  APT prefers stable-debug
  APT policy: (500, 'stable-debug'), (500, 'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-8-amd64 (SMP w/4 CPU threads)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: runit (via /run/runit.stopit)

Versions of packages libglfw3 depends on:
ii  libc6     2.31-13+deb11u3
ii  libgl1    1.3.2-1
ii  libx11-6  2:1.7.2-1

libglfw3 recommends no packages.

Versions of packages libglfw3 suggests:
ii  libegl1     1.3.2-1
ii  libgles1    1.3.2-1
ii  libgles2    1.3.2-1
ii  libosmesa6  20.3.5-1
ii  libvulkan1  1.2.162.0-1

-- no debconf information