A9-Spinning Beach Ball-Indexer Crash-LLS:1.0.318

Doing Bible Index, resource file AGNT.logos4 (downloaded to LLS:1.0.318) crashes Indexer => A9 home page non-responsive with spinning beach ball and Logos4Indexer process still exists, but doing nothing. Using Activity Monitor utility to display all processes hierarchically and looked in Indexer-stderr.log to verify. Force quit does not close A9 non-responsive home page, but kill does.

$ ps -aef | grep Log

501 794 809 0 0:01.58 ?? 0:11.34 /Applications/Logos Bible Software 4.app/Contents/MacOS/Logos Bible Software 4 -psn_0_143395

501 798 799 0 0:00.23 ?? 0:01.87 /Applications/Logos Bible Software 4.app/Contents/MacOS/Logos4Indexer.app/Contents/MacOS/Logos4Indexer

501 1171 738 0 0:00.00 ttys000 0:00.00 grep Log

$ kill -9 809 799

Relevant Indexer-stderr.log lines:

01/08/2010 01:15:23 | INFO | 7 | BibleIndex | (Timed) Indexing LLS:1.0.318

assertion "nIndex >= 0 && nIndex < m_nSize" failed: file "../../../Libs/MFCLib/CObArray.h", line 99

Stacktrace:

Log files attached:

0624.Archive.zip">http://community.logos.com/cfs-file.ashx/__key/CommunityServer.Discussions.Components.Files/75/0624.Archive.zip:550:0]

Assertion failed is same as previous post about resource files: LXX, NASB95, and RWP crashing indexer during Resource Identification

http://community.logos.com/forums/p/8706/72374.aspx

Grinning again - deleted all content in Logos4.dmg disk file, copied Data, Documents, Shared, and Users folder from initial A8 download. Created Logging folder and copied log.config file - deleted known A9 Indexer crashing resources:

$ pwd

/Users/briggsr/Library/Application Support/Logos4/Data/qofvuuiv.o15/ResourceManager/Downloaded/LLS:1.0.301

$ ls -l

-rw-r--r-- 1 briggsr staff 31107472 Dec 30 20:01 LXX.lbxlls

$ rm L*

$ touch LXX.lbxlls

$ ls -l

-rw-r--r-- 1 briggsr staff 0 Jan 8 07:44 LXX.lbxlls

$ cd ../LLS:1.0.318

$ ls -l

-rw-r--r-- 1 briggsr staff 7863994 Dec 30 21:43 AGNT.logos4

$ rm A*

$ touch AGNT.logos4

$ ls -l

-rw-r--r-- 1 briggsr staff 0 Jan 8 07:47 AGNT.logos4

Rebooted computer, deleted Logos4 content (Logging and Users) from Logos4Indexer autostart, attached dmg file:

$ hdiutil attach /Volumes/Valet/Downloads/Logos/Logos4.dmg -mountpoint "/Users/briggsr/Library/Application Support/Logos4" -nobrowse

/dev/disk2 GUID_partition_scheme

/dev/disk2s1 EFI

/dev/disk2s2 Apple_HFS /Users/briggsr/Library/Application Support/Logos4

Launched A9 - prompted for Developer Tools group member - Crash LLS:1.0.209 (kill non-responsive A9)

01/08/2010 08:46:58 | INFO | 6 | BibleIndex | (Timed) Indexing LLS:1.0.209

assertion "nIndex >= 0 && nIndex < m_nSize" failed: file "../../../Libs/MFCLib/CObArray.h", line 99

Stacktrace:

Plan to keep identifying Index crashing resources this weekend.

Keep Smiling Smile

Find more posts tagged with

Comments

J.R. Miller

Thanks for investigating and reporting this stuff :-)

Keep Smiling 4 Jesus :)

https://community.logos.com/discussion/comment/72708#Comment_72708

After more than 3 dozen crashes, wondering about difference between Identifying Resource and Bible Index crashes - both raise assertion failure - now suspect assertion being case sensitive (reason near end of post):

assertion "nIndex >= 0 && nIndex < m_nSize" failed: file "../../../Libs/MFCLib/CObArray.h", line 99

After removing and touching many logos4 resources (simulate download failures), noticed repeating Bible Index crash pattern - assertion failure always 3 lines after Bible Index started additional library indexing thread:

01/10/2010 18:57:37 | INFO | 7 | BibleIndex | Starting additional library indexing thread.

01/10/2010 18:57:37 | INFO | 6 | BibleIndex | (Timed) Indexing LLS:1.0.196

01/10/2010 18:57:37 | INFO | 7 | BibleIndex | (Timed) Indexing LLS:1.0.318

assertion "nIndex >= 0 && nIndex < m_nSize" failed: file "../../../Libs/MFCLib/CObArray.h", line 99

Pondered whether several dozen bible logos4 resources (English, Greek, and Cairo fragments) have indexing issues or thread spawning has potential context issue (or 32/64 bit addressing issue) or case sensitivity.

Moved Logos for Mac 1.2.2 Resources elsewhere - only used Logos 4 downloads for attached log and crash files - simulated download failure only for LXX.lbxlls (avoid identifying resource crash):

8311.Archive.zip

Indexer-stderr.log comments:

Navigation Index Item Visitor has variety of recurring errors (many Bad Reference):

01/10/2010 18:54:17 | ERROR | 3 | NavigationIndexItemVisitor | Discarding empty milestone for reference: %israelAndTheMiddleEastToday (at 8455787:0)

01/10/2010 18:55:18 | ERROR | 3 | NavigationIndexItemVisitor | ReferenceSupersets for wn is null.

01/10/2010 18:55:50 | ERROR | 3 | NavigationIndexItemVisitor | Bad Reference: bdb.1.1.1 (at 1547:132)

Occurs once:

01/10/2010 18:55:12 | ERROR | 3 | NavigationIndexItemVisitor | Unknown/Unimplemented data type: gnt/92065.

Many Navigation Indexes were created quickly (less than a second). Resource discovery finished - about 15 minutes.

Some Baggage missing:

01/10/2010 18:56:21 | WARN | 5 | Libronix.DigitalLibrary.Logos.LogosResource | Unable to open baggage at Images/FRESHSTDEV.jpg

01/10/2010 18:56:29 | WARN | 5 | Libronix.DigitalLibrary.Logos.LogosResource | Unable to open baggage at Images/LOGOS4HELP.jpg

01/10/2010 18:56:37 | WARN | 5 | Libronix.DigitalLibrary.Logos.LogosResource | Unable to open baggage at Images/OPENTEXTGNT.jpg

Bible Index has many resources that NeedsIndexing, but consistently crashes. Clicking Cancel when asked for "Developer Tools" group authorization.

Suspect tmp command file error is cascading effect from Bible Index crash.

/tmp/mono-gdb-commands.FEuS5s:1: Error in sourced command file:

Unable to access task for process-id 2533: (os/kern) failure.

Logos4.log comments:

Seems odd to move Resources from Downloaded folder to ScannedResources folder then delete ScannedResources folder, followed by discovering resources in Resources folder:

2010-01-10 18:40:52.2861 3 Info ResourceManager Moving resource from '/Users/briggsr/Library/Application Support/Logos4/Data/qofvuuiv.o15/ResourceManager/Downloaded/PDF:DIAGANALYSIS/DIAGANALYSIS.logos4' to '/Users/briggsr/Library/Application Support/Logos4/Data/qofvuuiv.o15/ResourceManager/ScannedResources/DIAGANALYSIS.logos4'.

2010-01-10 18:40:52.2861 3 Info ResourceManager Deleted 'ScannedResources' folder (/Users/briggsr/Library/Application Support/Logos4/Data/qofvuuiv.o15/ResourceManager/ScannedResources).

2010-01-10 18:40:52.3760 3 Info LocalFileResourceDiscoverer Discovered resource at /Users/briggsr/Library/Application Support/Logos4/Data/qofvuuiv.o15/ResourceManager/Resources/LCV.lbslcv: DB:LCV (2009-10-26T07:11:21Z)

A9 comments:

Even though Data, Documents, and Users folders were moved to trash, trash emptied, and copied from elsewhere - A9 sometimes showed home page vis Preparing Library vis Downloading…(null) dialog boxes. If Home Page displayed, after BibleIndex crash, tried GO menu to Library - did see book covers and titles, but double clicking any one crashed A9. Currently Logos 4 base package upgrade has expanded Resource list in my Logos for Mac 1.2.2, but unable to read any book in Logos4 A8 or A9 using Mac OS X 10.6.2 Snow Leopard - opportunities to improve - also been fun sharing case sensitive information and repeating Alpha crashes - looking forward to revisions

If A9 left running overnight, LogosIndexWorker effectively would show elapsed time with 0 progress:

01/10/2010 09:40:19 | DEBUG | 3 | LogosIndexerWorker | 0.0000 = 0.25 * (1.00 * 0.00 + 0.00 * 0.74 + 0.00 * 0.26 + 0.00 * 0.00) after 592.0

Waking Snow Leopard from Sleep would crash A9.

Note: using iMac with 2.4 GHz Intel Core 2 Duo running Mac OS X 10.6.2 with case sensitive file system for crashes. Activity Monitor shows variety of 32 and 64 bit processes.

By the way, a different vendor has a Mac product that requires case insensitive file system (developers had quite diverse use of shift and caps lock when typing various items). One smallish partition on my Mac is case insensitive (seldom used), yet Logos A9 works, including LXX.lbxlls - log files attached for comparison (All Background Tasks completed). Mac OS X 10.5.8 did use additional A9 Bible Indexing thread - Activity Monitor shows CPU up to 195.1 busy - also all processes 32 bit - had many Native Normalize String errors during Bible Index:

01/11/2010 00:15:44 | ERROR | 7 | DocumentIndexer | Error while normalizing bytes: 0x05d9 0x05e9 0x05e8 0x05d0 0x0307 0x05dc 0x0307

01/11/2010 00:15:44 | DEBUG | 7 | DocumentIndexer | Returned string from NativeNormalizeString is ???????

2541.Archive.zip

For grins, tested A9 on Mac OS X 10.5.8 case sensitive file system using 3rd bootable partition on my iMac (2 primary boot partitions: 10.6.2 and 10.5.8 case sensitive with one for a case insensitive product along with one for data storage).

Learned Identifying Resources for LXX.lbxlls crashes - wonder if assertion logic case sensitive (e.g. expecting all upper or lower case characters for range of 26 characters)

01/11/2010 08:20:15 | DEBUG | 3 | LogosResourceDriver | Identifying resource file located at /Users/briggsr/Library/Application Support/Logos4/Data/qofvuuiv.o15/ResourceManager/Downloaded/LLS:1.0.301/LXX.lbxlls

assertion "nIndex >= 0 && nIndex < m_nSize" failed: file "../../../Libs/MFCLib/CObArray.h", line 99

Simulated download failure for LXX.lbxlls and relaunched A9 - likewise wonder about case sensitivity for assertion repeat:

01/11/2010 08:45:51 | INFO | 8 | BibleIndex | Starting additional library indexing thread.

01/11/2010 08:45:51 | INFO | 7 | BibleIndex | (Timed) Indexing LLS:1.0.196

01/11/2010 08:45:51 | INFO | 8 | BibleIndex | (Timed) Indexing LLS:1.0.318

assertion "nIndex >= 0 && nIndex < m_nSize" failed: file "../../../Libs/MFCLib/CObArray.h", line 99

Keep Smiling

Tom Philpot (Faithlife)

https://community.logos.com/discussion/comment/74283#Comment_74283

Thanks for the update on case sensitivity. None of the Mac devs run case sensitive file systems here (and since we're sharing a lot of Windows core code), there could very well be cases we've not ironed out. For now, it's safe to say we don't support case-sensitive file systems. We'll try to take a look at the code and see if we can fix the issue with a minimum of pain.

Just so I can help track down the issue, can you list which volumes are mounted as case-sensitive (and where they're mounted) on your systems that are experiencing the crash?

Thanks.

Keep Smiling 4 Jesus :)

https://community.logos.com/discussion/comment/74286#Comment_74286

My iMac has 4 partitions with 3 bootable. Holding option key down while starting up or rebooting causes menu to appear - can choose which partition to mount as root (with other partitions mounted in /Volumes). All available bootable partition(s) appear in option menu: internal disk partition(s), optical drive with bootable media, and external disk partition(s).

/dev/disk0s2 "Snow Leopard" Mac OS X 10.6.2 with journaled case sensitive file system - Logos4/data/qofvuuiv.o15 using hdiutil to attach logos4.dmg as "/Users/briggsr/Library/Application Support/Logos4" - primary crash configuration - tried case insensitive and case sensitive journaled file systems in logos4.dmg - same L4 Alpha crash behavior.

/dev/disk0s3 "Leopard" Mac OS X 10.5.8 with journaled case sensitive file system - also used Logos4/data/qofvuuiv.o15 (quicker to copy existing A8 downloaded resources with some updates), but did not attach disk image file.

Note: when Mac OS X 10.7 ships (possibly 2011 or 2012), plan to change "Leopard" volume name (possibly Lynx or Cougar), install OS X 10.7 cleanly using case sensitive journaled file system and restore profile stuff from time machine backup.

/dev/disk0s4 "Valet" journaled case sensitive file system - data storage

/dev/disk0s5 "zMac" Mac OS X 10.5.8 journaled case insensitive system - Logos4/data/qdbxuc64.ayc - A9 indexing completed, able to read Logos resource in library.

By the way, Apple's disk utility can be used to resize and split existing partitions. Also can easily copy one partition to another. In fact, before Apple shipped Snow Leopard, that partition contained a bootable copy of Leopard - installed Mac OS X 10.5 to Leopard then booted installation DVD so could use disk utility to copy Leopard partition to Snow Leopard (drag and drop restore => source and destination).

In contrast, cloning Windows configurations takes more effort - needs sysprep to regenerate system id (needed for computer domain accounts). Windows is very sensitive to disk partition number used during installation - not nice to change partitioning after installation, Windows can become unusable since drive letter mapping associated with partition numbering.

Technical observation: Windows NTFS can be tweaked to be case sensitive - for POSIX compatibility.

For now, plan to keep using Logos for Mac 1.2.2 on Mac OS X 10.6.2 with case sensitive file system while hoping and praying for Logos4 improvements.

Pondering copy of "Snow Leopard" to case insensitive file system for Logos4 Alpha testing - could use external disk drive.

Historical note: Mac OS X could not use case sensitive file system for boot partition for several versions - perhaps Apple Developer connection could share some lessons learned. Imagine Mac OS X Reference Library article: "Porting to Mac OS X from Windows win32 API" already known:

http://developer.apple.com/mac/library/documentation/Porting/Conceptual/win32porting/win32porting.html

along with Mac OS X File System Overview whose guidelines contain this assumption:

Assume Case Sensitivity

Avoid the assumption that you can perform case-insensitive file comparisons or searches. Mac OS X supports many file systems that use case to differentiate between files. Even on file systems (such as HFS+) that support case insensitivity, there are still times when case may be used to compare filenames. For example, CFBundle and NSBundle consider case when searching bundle directories for named resources.

Try testing your software on volumes (such as UFS) that do distinguish files by case.

http://developer.apple.com/mac/library/documentation/MacOSX/Conceptual/BPFileSystem/Articles/FileSystemGuidelines.html#//apple_ref/doc/uid/20002296

Keep Smiling

Keep Smiling 4 Jesus :)

https://community.logos.com/discussion/comment/74741#Comment_74741

Living & learning - found Mac OS X command to display file system format (perhaps add some debug output):

$ diskutil info /dev/disk0s2

Device Identifier: disk0s2

Device Node: /dev/disk0s2

Part Of Whole: disk0

Device / Media Name: Untitled

Volume Name: Snow Leopard

Escaped with Unicode: Snow%FF%FE%20%00Leopard

Mounted: Yes

Mount Point: /

Escaped with Unicode: /

File System: Case-sensitive Journaled HFS+

Type: hfs

Name: Mac OS Extended (Case-sensitive, Journaled)

Journal: Journal size 24576 KB at offset 0x801000

Owners: Enabled

Partition Type: Apple_HFS

Bootable: Is bootable

Media Type: Generic

Protocol: SATA

SMART Status: Verified

Volume UUID: 673D9363-8B72-3A94-9635-90C067D807C8

Total Size: 274.6 GB (274582630400 Bytes) (exactly 536294200 512-Byte-Blocks)

Volume Free Space: 144.3 GB (144328339456 Bytes) (exactly 281891288 512-Byte-Blocks)

Read-Only Media: No

Read-Only Volume: No

Ejectable: No

Whole: No

Internal: Yes

By the way, this mount output shows "Snow Leopard" mounted as root:

$ mount

/dev/disk0s2 on / (hfs, local, journaled)

devfs on /dev (devfs, local, nobrowse)

/dev/disk0s3 on /Volumes/Leopard (hfs, local, journaled)

/dev/disk0s4 on /Volumes/Valet (hfs, local, journaled)

/dev/disk0s5 on /Volumes/zMac (hfs, local, journaled)

map -hosts on /net (autofs, nosuid, automounted, nobrowse)

map auto_home on /home (autofs, automounted, nobrowse)

/dev/disk1s2 on /Volumes/TimeMachine Drive (hfs, local, nodev, nosuid, journaled)

Keep Smiling

Tom Philpot (Faithlife)

https://community.logos.com/discussion/comment/77692#Comment_77692

Living & learning - found Mac OS X command to display file system format (perhaps add some debug output):

Nice, Thanks for the tip! It's nice to have sys admins and developers in the user base

Tom Philpot (Faithlife)

https://community.logos.com/discussion/comment/74283#Comment_74283

After more than 3 dozen crashes, wondering about difference between Identifying Resource and Bible Index crashes - both raise assertion failure - now suspect assertion being case sensitive (reason near end of post):

As I responded to JonathanFranklin in another thread, I'm going to try and give this some serious attention next week because it seems that at least part of the crashes are not related to case-sensitive file systems. It looks like there could be several problems here since there are crashes in a couple of different places.

Thanks for all the detailed analysis.

Tom Philpot (Faithlife)

https://community.logos.com/discussion/comment/77785#Comment_77785

As I posted in another thread, I think I've fixed this issue for A12.