Krzysztof Foltman wrote:
>> Has anyone else been able to reproduce the bug? Does this patch seem to
>> help? Be sure to test first with a debug build.
>
> I can't try to reproduce the bug, as I still don't have the Internet
> connection at home. However, I think you can try to do it using low
> zombification timeout, like 500 ms or less (which is how Hollunder found
> the analogical bug in Calf). Of course, if you set it too low it will
> zombify even from minor slowdowns, which I guess is worse than
> occasional xrun - but could be nice for some debugging/testing.
Thanks! I'll mull that over... and also try to find what my timeout is
currently. At the moment I can occasionally make it happen on one or two
machines without manually tweaking the 'timeout.'
>> * All logging is disabled. When the logging thread
>> is actively processing it's data, it locks the queue.
>> Anything in a process() cycle that wants to add
>> something to the logging queue has to wait. (At
>> least... as far as I can tell. :-))
>
> Despite trylock? I don't understand.
(ERROR|INFO|WARNING)LOG() don't use try_lock, or else log messages would get
dropped. For example (object.cpp:281-285)....
void Logger::info_log( const char* funcname, const QString& class_name,
const QString& logMsg )
{
if ( !Object::is_using_verbose_log() ) return;
pthread_mutex_lock( &__logger_mutex );
That's the same mutex locked by loggerThread_func()... also *not* try_lock'ed.
Peace,
Gabriel
------------------------------------------------------------------------------
OpenSolaris 2009.06 is a cutting edge operating system for enterprises
looking to deploy the next generation of Solaris that includes the latest
innovations from Sun and the OpenSource community. Download a copy and
enjoy capabilities such as Networking, Storage and Virtualization.
Go to: http://p.sf.net/sfu/opensolaris-get
_______________________________________________
Hydrogen-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/hydrogen-devel
