indexing bug
Comments
-
Dave Hooton said:
I'm sure the problem will be resolved by allowing an update from 4.0c to the latest version 4.2b SR-1
[sigh]
Gotta remember to look at that first line first.
Help links: WIKI; Logos 6 FAQ. (Phil. 2:14, NIV)
0 -
I was using a system with Windows 7 quad core (have returned it to get Intel in same config rather than AMD) and had the same problem with indexing - protected memory error. I solved it by copying over my Vista installation which worked to the Windows 7 computer - see the Wiki about installing on multiple pcs. From that point forward it seemed to work ok. It involved deleting certain folders on the Windows 7 computer in the Data folder for L4 and then copying over those same folders from the working Vista installation I have. The copying was done after a fresh install of L4 without allowing it to do a download of resources or a fresh indexing. See this article http://wiki.logos.com/Quick_Installation_onto_multiple_computers. I believe it was method 2 that I used. Either way it worked for me.
0 -
Dave Hooton said:
Personally puzzling about what is different about my pair of 64 bit Windows 7 Service Pack 1 configurations that can index my entire library and ones not working.
I don't think it is connected with 7 SP1, nor any hardware issue (been down that path too many times). Reverse Interlinears are particularly suspect but Logos have yet to reproduce the error for themselves.
Not know if connected with Windows 7 Service Pack 1; so far have not seen a protected memory error without Windows 7 Service Pack 1, as noted by Bradley => http://community.logos.com/forums/p/35501/270780.aspx#270780 (have seen 4.2b SR-1 and 4.3 RC 1)
After rereading Bradley's earlier replies => http://community.logos.com/forums/p/35501/269914.aspx#269914
wondering what anti-virus and anti-malware software is installed ? (possibly real time scanning interference)
On one laptop have AVG Free Edition 2011, version: 10.0.1390; newer laptop has Avast Free Ant-Virus 6.0.1203 (both laptops can completely rebuild Logos 4.3 RC 1 indexes: newer laptop is noticeably faster: Bible index done in 14m 54.6s vis 35m 41.4s and Library index done in 1h 26m 54s vis 2h 19m 13s; appears 2nd generation 2.00 GHz Quad Core i7 is bit faster than 2.26 GHz Core 2 Duo).
While researching, found one article using SQL Server CE with similar error => http://stackoverflow.com/questions/2423458/attempted-to-read-or-write-protected-memory-sql-compact-and-net that was fixed by changing database connection code (software).
Keep Smiling [:)]
0 -
Tim Engwer said:
I believe it was method 2 that I used. Either way it worked for me.
Most likely Method 2. But good to know that it solved your indexing problem.
Dave
===Windows 11 & Android 13
0 -
The "IndexingException: Attempted to read or write protected memory" crash appears to be related to the new AMD A6 and A8 chips. See the update I posted here: http://community.logos.com/forums/p/36252/275076.aspx#275076
0 -
The only way that I was able to work around it was to do the 'method 1'
copy of a working installation from my old Intel-based desktop to my AMD A8-based laptop. It seems that having a working index from the initial installation and updating from there helped to avoid whatever the initial indexing was hitting.Thanks
Mike
0 -
Any work arounds other than having a indexed copy lying around?; I'm starting to get pretty frustrated.
0 -
I've ordered an AMD A6-3400M system for testing, which I hope will let us reproduce and fix the issue. As I mentioned, this is one of the strangest bugs that I've ever seen, so we may be a week or more out from a fix.
The only known workaround is to use an Intel CPU...
0 -
On a hunch, I tried setting the AFFINITY of LOGOSINDEXER.EXE To a single core (0); It finished without problem, when before it crashed repeatedly; I'm running on an AMD A6-3400M APU with Radeon(tm) HD Graphics 1.40GHZ)
I suspect the problem occurs when you're taxing the core of the CPU that's dedicated to the graphics card on a chip
Hopefully this helps other users in the same boat!
0 -
Thanks for this feedback! That's a great workaround (and I wish I had thought of it).
I'll pass your suggestion on to Tech Support so they can let our other affected customers know.
0 -
This bug should be fixed in 4.3 SR-1; run "update now" to check for updates and install the latest version.
0
said:
