https://issues.apache.org/bugzilla/show_bug.cgi?id=56645
--- Comment #6 from Eric Covener <[email protected]> --- (In reply to Takashi Sato from comment #5) > (In reply to Takashi Sato from comment #2) > > (In reply to Eric Covener from comment #1) > > > I notice there is no checking of the return code for lock/unlock of those > > > mutexes. They could be failing > > > > OK, I try to put trace logs to log whether lock/unlock success or not. > > I tried. lock/unlock succeed... > > Then, I tried to migrate apr_skiplist to apr_array, then works fine (of > cource performance is bad and may have memory leaks)! > It seems apr_skiplist has some bug. You might try Yanns patch. I don't know anything about the skiplist impl, but I don't know what might get moved while other threads add/remove unrelated entries. In that case, his lock would unfortunately be required. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
