summaryrefslogtreecommitdiff
path: root/MEMORY-LEAK
diff options
context:
space:
mode:
authorJaroslav Kysela <perex@perex.cz>2003-02-04 14:56:07 +0000
committerJaroslav Kysela <perex@perex.cz>2003-02-04 14:56:07 +0000
commit0ec98511765fd7d9bcf64066348bd1e708f11560 (patch)
tree2b89942f43730a525bb9c7ccd0c9e9a72d75f381 /MEMORY-LEAK
parentfd52ee0085b6c04e564e13bc1c0ad3edb85ea5a2 (diff)
downloadalsa-lib-0ec98511765fd7d9bcf64066348bd1e708f11560.tar.gz
Initial version
Diffstat (limited to 'MEMORY-LEAK')
-rw-r--r--MEMORY-LEAK13
1 files changed, 13 insertions, 0 deletions
diff --git a/MEMORY-LEAK b/MEMORY-LEAK
new file mode 100644
index 00000000..d9677d8d
--- /dev/null
+++ b/MEMORY-LEAK
@@ -0,0 +1,13 @@
+
+
+ Memory leaks - really?
+ ----------------------
+
+Note that some developers are thinking that the ALSA library has some memory
+leaks. Sure, it can be truth, but before contacting us, please, be sure that
+these leaks are not forced.
+
+The biggest reported leak is that the global configuration is cached for
+next usage. If you do not want this feature, simply, call
+snd_config_update_free_global() after all snd_*_open*() calls. This function
+will free the cache.