On Mon, Oct 20, 2003 at 07:28:14PM +0200, Dirk Meyer wrote: > That's odd. This can oly happen if you a new child faster than the old > one, e.g. you walk through the playlist very fast. Have you traced the > bug any deeper? You may catch the bug now, but I still wonder why it > happens.
The bit of code I commited today should help spot the issue when it crops up. > This should also not happen. The write functions has a try-except > around it. I thought so, but nevertheless I caught a few of them. > Again, this should work. There is a try catch around plugin init. You > should see the trace but freevo shouldn't die. But if a plugin crashes > later, this is not handled. Right; the problem arose when the Amazon plugin was contacting amazon. For some reason, Amazon returned a 404 on the query. (It worked again later) but something like that shouldn't crash Freevo. I modified the plugin to deal with the 404, but since many of the plugins rely on data from external sources, it might be a good idea to keep them sandboxed so bad external data doesn't cause problems. ------------------------------------------------------- This SF.net email sponsored by: Enterprise Linux Forum Conference & Expo The Event For Linux Datacenter Solutions & Strategies in The Enterprise Linux in the Boardroom; in the Front Office; & in the Server Room http://www.enterpriselinuxforum.com _______________________________________________ Freevo-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freevo-devel
