double free or corruption backtrace

[GoogleCodeExporter]

We are exploring search options for use within the Fedora Project, and in our 
tests of running the crawler (indexer), we are running into an occasional 
backtrace. It seems to be almost at random, I don't notice anything in common 
about the URL it hits before the backtrace each time.

I've attached the backtrace, and happy to provide any more information we can 
to help get this solved.

What version of the product are you using? On what operating system?

indexer from dpsearch-4.53-pqsql

[root@junk09 dpsearch]# cat /etc/redhat-release 
Red Hat Enterprise Linux Server release 6.2 (Santiago)

[root@junk09 dpsearch]# uname -a
Linux junk09.qa.fedoraproject.org 2.6.32-220.4.1.el6.x86_64 #1 SMP Thu Jan 19 
14:50:54 EST 2012 x86_64 x86_64 x86_64 GNU/Linux

Please provide any additional information below.

Again, if there's anything we can do, we're happy to work with you try to and 
get this fixed. :)

Original issue reported on code.google.com by codebl...@elrod.me on 13 Feb 2012 at 7:38

Attachments:

• bt

[GoogleCodeExporter]

Perhaps you've faced a bug when libcrypto had been used in multithread indexer 
without safety locks. This issue has been fixed in snapshot of 4.54 version. 
Please try it: 
http://dataparksearch.googlecode.com/files/dpsearch-4.54-2012-02-14.tar.bz2

Original comment by dp.max...@gmail.com on 14 Feb 2012 at 10:45

[GoogleCodeExporter]

Hi, I tried the snapshot you linked to and the indexer is still randomly 
failing in the same way. Is there any other information I can provide that 
would be helpful in getting this fixed? We really like the looks of Datapark so 
far, aside from this issue. :-).

Thanks!

Original comment by codebl...@elrod.me on 15 Feb 2012 at 12:56

[GoogleCodeExporter]

How many indexing threads do you run simultaneously (the value for -N switch)?

Original comment by dp.max...@gmail.com on 15 Feb 2012 at 9:41

[GoogleCodeExporter]

Please try fresh snapshot: 
http://dataparksearch.googlecode.com/files/dpsearch-4.54-2012-02-15.tar.bz2

I've moved SSL initialisation to the right place.

Original comment by dp.max...@gmail.com on 15 Feb 2012 at 12:11

• Changed state: Fixed