Since 0.7RC10 I've been getting this message box when I close foobar2000
---------------------------
Error
---------------------------
metadb_handle leaks, 48 objects
---------------------------
OK
---------------------------
naturally the number of objects vary, the last db related thing I did before I started noticing this was nuke the database.
- mig
sorry, should've searched
- mig
Well, I searched.
When a system shutdown is iniated, Foobar throws metadb_handle leaks, 1 objects, but only if it is playing at the time. It closes normally if I quit it directly. It does this with only the dlls of standard outputs, inputs and ui loaded. Using RC10, and both RC11s.
Poking in the dark, I collected the following random factors: it doesn't depend on the codec, on output, on database being enabled, it remains in fact when every single checkbox is cleared, and the formatting strings can be zeroed out

. This is consistent across two XP SP1 systems and a 98 SE.
So, what gives?
You most likely have an old component that doesn't properly close the metadb handles, try getting the most updated version of the 3rd party components that you use.
- mig
QUOTE
It does this with only the dlls of standard outputs, inputs and ui loaded.
...
Whoa, then that's something that zZzZzZz would have to look at....
- mig
Can't reproduce. Please post a list of DLL files in your "components" directory and your .cfg file if possible.
musicmusic
Sep 6 2003, 03:59
For what its worth, i also get metadb_handle leaks only when i shut down my computer but then again i do have a bunch of 3rd party components installed. Ill turn on my desktop in a min and see if i can work out what is causing it..
edit: never mind, easily reproduced on laptop with clean install (default components from normal installer from frontpage), just loggoff whilst playing.
happy_harry
Sep 6 2003, 05:05
Hi!
I get the same message too, only when shutdown.
I have no other plugins installed, I've even trie the lite version, same happened.
I repeat: no 3rd party dlls!
i have no other plugins installed too and get this error.
These pretty much sum it up. It's happening with the bare minimum, foo_ui_std, foo_input_std and foo_output_std, and the config file can be in it's default state. I can't believe you can't reproduce.
upNorth
Sep 6 2003, 06:23
I haven't had this problem after I updated foo_dbsearch and foo_history, but I still wonder if this error can be harmful in any way?
So it happens only when exiting windows; that would explain it, thanks.
No, this error isn't really harmful, it's more like information for component developers about memory leaks; it's been there since 0.6 but apparently noone noticed its previous form (logged to debugger console).
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please
click here.