Details
-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Won't Fix
-
Affects Version/s: 2.2.7
-
Fix Version/s: None
-
Component/s: Indexer
-
Labels:None
-
Environment:
Model Name: iBook G4
Model Identifier: PowerBook6,7
Processor Name: PowerPC G4 (1.2)
Processor Speed: 1.42 GHz
Number Of CPUs: 1
L2 Cache (per CPU): 512 KB
Memory: 1.5 GB
Bus Speed: 142 MHz
Boot ROM Version: 4.9.3f0
Serial Number (system): 4H53304VSE6
Hardware UUID: 00000000-0000-1000-8000-00112442D52E
Sudden Motion Sensor:
State: Enabled
Version: 1.0Model Name: iBook G4 Model Identifier: PowerBook6,7 Processor Name: PowerPC G4 (1.2) Processor Speed: 1.42 GHz Number Of CPUs: 1 L2 Cache (per CPU): 512 KB Memory: 1.5 GB Bus Speed: 142 MHz Boot ROM Version: 4.9.3f0 Serial Number (system): 4H53304VSE6 Hardware UUID: 00000000-0000-1000-8000-00112442D52E Sudden Motion Sensor: State: Enabled Version: 1.0
Description
1. Perform a search for any Greek text (other foreign languages not tested)
2. The index creation process will begin, the bar will fill up and look complete, but then MacSword crashes.
3. Relaunching MacSword immediately afterward causes another crash.
4. Upon 2nd relaunch, MacSword opens.
5. Upon Re-searching for Greek text, MacSword attempts to create another index file, and crashes.
Attached are two crash logs, one for the ABPGRK text and one for the 2TGreek text.
Thank you for all of your hard work, I love this program.
Attachments
Activity
As far as I am aware, no. But apart from the Greek modules, I have only tried English modules. The index creation is touchy I have found, though. I created indexes for the ABP and KJV, but I found that any other resources intensive applications (i.e. a video game making MacSword run in the background) made for a high likelihood of a crash. So I had 2 or 3 crashes before I quit the game and let MacSword have the entire gamut of resources.
I have successfully created indexes for LITV, MKJV, YLT, NKJ, and ABP. Those Greek ones are the only ones, to my knowledge, which don't work. If you want, tonight I'll try and download some other foreign language bibles and see if they cause a crash.
Are the crash logs helpful? Should I continue providing them for future crashes on this issue?
The PolBibTysia and NovaSahidica both index just fine.
Hi Joshua.
Yes. Crash logs are normally helpful.
I've tried indexing those two modules on my hardware where my PowerBook G4 (1 GB) should be the most similar to yours. Both modules indexed fine but I had no other application open at the time and so MacSword had enough of resources.
Watching with activity monitor the memory usage is steadily rising until it reaches 190 MB physical a little after the progress bar is at the end (which is when the indexing is finished and the index is stored to disk by SearchKit).
And there is also the problem. I tried to keep resource usage low while looping though the bible and adding to the index but the last step, when SearchKit stores the gathered index to disk that's something I have actually no control over.
Your crash log proves this because the crash happens in a SKIndexFlush method which is one of SearchKit's methods to store the index to disk.
I believe that this is because of too low resources of memory.
Have you tried indexing after a fresh restart of your system?
Manfred
Well, you were right, it worked after a fresh restart of the system. I generally have close to a gig of free RAM at all times while running OSX though, so I would think that would be enough. As of now, however, I am happy. Thanks for your wonderful work, your suggestions, and for responding diligently.
Yeah, I would have thought that 1 Gig free mem should be enough. Maybe it is a combination of physical and available virtual memory???
Anyhow, thanks for your detailed report. I'll close this for now.
If you have more issues just let me know.
Manfred
Hello Joshua.
Does this happen to none greek modules as well?
I still have an iBook G4, maybe the same than you, and I will do some tests.
Regards,
Manfred