Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Duplicate
-
Affects Version/s: 1.6
-
Fix Version/s: 1.6.1
-
Component/s: o.c.jsword.index
-
Labels:None
-
Environment:
Windows XP Media Center Edition 2002 SP3, fully patched. Java 6 SE Update16
Description
I have begun exhaustively testing every Bible module to see whether it can be indexed for searching.
Though the majority of modules can be indexed successfully, there are still many that cannot.
Of those that cannot, most fail at 0% of the progress indicator, but there are some that get beyond that and still fail.
Here are the results so far, listing only those that failed, and for now at least, omitting the beta modules from Wycliffe, which are still to be tested.
I have not distinguished which repository the module was installed from.
Fail at 0% :
ASV, BWE, Chamorro, Common, Darby, FinPR, FreCrl, FreLSG, GerSch, ItaDio, ItaRive, JPS, LO, Maori, Montgomery, OrthJBC, PL_BW1997, RNKJV, RST, RWebster, RusVzh, SpaSEV, Swahili, TischMorph, Uma, Vulgate, Weymouth, Xhosa, YLT.
Fail at > 0% of progress :
2TGreek 70%
Murdock 12%
PolBybTysia 4%
Swe1917 2%
SweFB1998 49%
These non-zero results might be a good clue to the root cause.
– David Haslam
Attachments
Issue Links
- duplicates
-
-
- Closed
-
Activity
After restarting from webstart, of the failed items above, I have since succeeded to index these:
PolBibTysia, RWebster, SomKQA, SpaSEV, Swe1917, TAMIL, TELUGU, TischMorph, Vulgate, Xhosa, YLT,
In this test run, I did not attempt to index any modules that might be av11n.
Together with the previously run's Java heap error as a symptom, this might suggest that failure to index a module with av11n could cause memory leakage or some such fault in the internal system, that afterwards prevents some good modules being indexed.
Typo. In previous comment, APBGK should have read APBGRK.
I have some changes to check in that I think will handle the problem with JPS. I found a place or two where it went off into la-la land and got the heap problem.
There is a memory leak in the program that happens when indexing one Bible after another. Most people will index only one or two in a given session and will never hit the problem.
I'm looking for the leak and I think I have found it, but i'm not sure. Anyway, I suggest indexing 3-5, shutting down and starting back up to see if that prevents the heap and out of memory errors.
Indeed, I was indexing one Bible after another. The suggested workaround makes sense.
Encountered first when module WLC was selected.