Ticket #342 (assigned defect)

Opened 11 months ago

Last modified 8 months ago

ferret segfaulting

Reported by: anonymous Owned by: dbalmain
Priority: major Milestone:
Component: component1 Version:
Keywords: Cc:

Description

Hi, I notice in our stderr log (we use litespeed server for our rails app and AAF) it is filled with these: /var/lib/gems/1.8/gems/ferret-0.11.6/lib/ferret/index.rb:768: [BUG] Segmentation fault ruby 1.8.5 (2006-08-25) [i486-linux]

It happens every couple of days, more often if our site gets more traffic. Unfortunately litespeed doesn't have a timestamp in its stderr log, so I can't track it back to the query that produces this. If you have any ideas on what might be causing this, it would be appreciated. Have been having this problem for as long as we've been using ferret (1yr+), so I don't think its anything new that you've added.

Attachments

Change History

Changed 11 months ago by dbalmain

  • owner changed from somebody to dbalmain
  • status changed from new to assigned

Thanks, I'm working on this.

Changed 8 months ago by anonymous

Hey Dave, Any update on this? Thanks, Chris

Changed 8 months ago by dbalmain

I'm working on increasing the test coverage in Ferret 100% (or as near as I can get). That is unfortunately the best I can do without a test script to reproduce the error. If you or anyone else would like to help out and speed things up, working out how to reproduce the error would be great. There has been a lot of work done in Ferret since the last release. The reason I haven't put out another release yet is that there have been changes to the index format and there could be some. I want to get all index format changes into a single release so everyone only needs to update their index once.

Add/Change #342 (ferret segfaulting)

Author



Change Properties
<Author field>
Action
as assigned
as The resolution will be set. Next status will be 'closed'
to The owner will change from dbalmain. Next status will be 'new'
 
Note: See TracTickets for help on using tickets.