Re: segfault with two parallel soup_session_sync_new



Michael Bell wrote:
> I implemented some stress tests which include parallel calls of
> soup_session_sync_new. The result is a segfault under Solaris. The
> crashing test runs under libsoup 2.2 because this is still the default
> version on Solaris.

2.2 is unfortunately now "ancient" in open source years, and since 2.4
involved large rewrites, it's not clear that any bugs you find in 2.2
will still exist in the current version.

> lwp #2, #3 or #4 causing the segfault. All other threads are just
> waiting. Any ideas what's going on?

Nope, but it looks like they're all crashing inside the GType system.
It's possible that if you create at least one SoupSession first to
initialize/register everything before creating others in parallel, then
the parallel creations after that won't crash.

(Also, it's a little weird to be creating lots of SoupSessions in
parallel anyway. Most applications will only need one SoupSession, and
you can use a single SoupSessionSync from multiple threads.)

-- Dan


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]