Veit,

What OS / compiler were you testing this with? I'm not sure, but this could
be due to the same threading issue we already aware of. Were you able to run
the atomic tests from the test suite successfully?

As you know, a move to using boost::threads is in our agenda. Done right,
this could resolve a lot of other threading issues as well. In the meantime,
try perhaps applying the threading related fixes Ben has pushed recently to
his branch (ben_working), and let me know how it goes.

HTH,

Itamar. 

-----Original Message-----
From: Veit Jahns [mailto:nuncupa...@googlemail.com] 
Sent: Friday, March 19, 2010 1:01 PM
To: clucene-developers@lists.sourceforge.net
Subject: [CLucene-dev] Multithreaded write and search

Dear all,

in our application we have several threads writing and searching on the
index. Writing and searching isn't a problem as long the IndexSearcher isn't
updated,i.e. deleting the old and creating a new IndexSearcher. But if the
IndexSearcher is updated, then the application crashes. Not every time, but
with high probability.

The problem is also occurs also, if every search thread has it's own
IndexSearcher. Then an update isn't needed. But the applications crashes
too, because---I suppose---the IndexSearcher is deleted at the end of the
thread.

I think it's a bug. But I don't exclude that I made an error in reasoning.
So any hint is much appreciated.

I wrote a test case and putted it in the file TestThreading.cpp The complete
file is attached to this e-mail.

Kind regards

Veit



------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
CLucene-developers mailing list
CLucene-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/clucene-developers

Reply via email to