Is there a page/word limitation for PBB creation (Logos crashes)

I have built several new personal books since the 4.3 announcement. works great (though I wish there was an "import" feature for multiple file-conversion--> Personal Books).

My latest one, though seems to crash my Logos on both my systems. I have a .DOCX that is just over 1000 pages. i can start the build process but it always fails with a Logos not responding error that when i click okay, closes Logos.

any assistance is appreciated.

Find more posts tagged with

Comments

John Sheeley

This is from one of the pages about Personal Books:

Add multiple documents to your book. If your source
document is very long, it may help to break it up into more than one
.docx file so you can navigate the book by article. Each .docx file
listed in the "Add Body Files" section of the Edit dialog will be
treated as an article in your book. You can rearrange the content of the
book by dragging and dropping one file above or below another file.

Brent Hoefling

https://community.logos.com/discussion/comment/275902#Comment_275902

I assume that If I have to do this, my TOC and Index will not be used/linked - as they would be on teh first doc and the last one. this wasn't a concern with my previous PBB converts becuase they didn't have a toc or index. do they even convert?

Rich DeRuiter

My latest one, though seems to crash my Logos on both my systems. I have a .DOCX that is just over 1000 pages. i can start the build process but it always fails with a Logos not responding error that when i click okay, closes Logos.

any assistance is appreciated.

What's probably happening is that such a large resource is overtaxing your system and/or the software in some way. If you have limited RAM and/or hard drive space, I'd look at a system issue. If you've got plenty of system muscle, you may have exposed a limitation in the software. It's also possible that there is something in your file that is causing the crash.

If you would like to help the programmers see and perhaps solve the issue, enable logging (instructions below) and post those logs here. I'd suggest not posting your source file here, since it's so large, and you'd be making it available to the whole world. If tech support wants it, ask for an email address to send it to.

Until then the suggestion above, to break up the file into several sections may (or may not) help. Since I don't know how the PB Tool works, I can't say that it would (maybe someone else knows). If you do break up your file, I'd suggest working with files of no more than about 100 pages each. Try one first, then try two (combined). If all works well, you can keep adding one at a time, until you find the limit, or try the whole thing and see what happens. It may be worthwhile to break your work up into "volumes" to make the compilation process more manageable. Breaking up the project may expose a problem with the file, as opposed to a problem with, or limitation of the software/hardware.

Instructions for enabling logging:

Carefully follow all the instructions in the link below:
http://wiki.logos.com/Diagnostic_Logging

Then run Logos and see if you can repeat the issue that caused the crash. Make sure to post all the log and txt files here for review.

Here are the Wiki instructions for how to upload logs.
http://wiki.logos.com/Uploading_Logs

Bohuslav Wojnar

I don't think there is any limit for the number of pages in PBB. I have done a number of Bibles (each from just one docx file) and it haven't got any problems. It has to be some other cause.

P.S. Each Bible is about 1600 pages.

Alan Gerling

https://community.logos.com/discussion/comment/275910#Comment_275910

I've had the same issue with very large books, and will follow the directions you have posted! (My system is a brand new system with quite a bit of muscle)

Brent Hoefling

https://community.logos.com/discussion/comment/275910#Comment_275910

6747.Logos4.logThank you.

Here's my Bug Report:

Bug: PBB causes Logos to crash
Description
When converting DOCX (over 1000 pages), the Logos system crashes.

Steps to reproduce

Launch logos 4
Tools, Personal Books
Add book, enter metadata, add file(s), begin building

Actual Result
After some time, the system crashes. an error message pops up that Logos is no longer responding and it closes the Logos system when click OK

Expected Result
Instead of crashing I expected Logos 4 to have added a Personal book to my library.

System Specs
Desktop | Windows Experience Index: 3.3 |

System

	Manufacturer	ASUSTeK Computer Inc.
	Model	EP121
	Total amount of system memory	4.00 GB RAM
	System type	64-bit operating system
	Number of processor cores	2

Storage

	Total size of hard disk(s)	60 GB
	Disk partition (C:)	13 GB Free (60 GB Total)

Graphics

	Display adapter type	Intel(R) HD Graphics
	Total available graphics memory	1696 MB
	Dedicated graphics memory	64 MB
	Dedicated system memory	0 MB
	Shared system memory	1632 MB
	Display adapter driver version	8.15.10.2302
	Primary monitor resolution	1280x800
	DirectX version	DirectX 10

Network

	Network Adapter	Atheros AR9002WB-1NG Wireless Network Adapter
	Network Adapter	Bluetooth Device (Personal Area Network)
	Network Adapter	Microsoft Virtual WiFi Miniport Adapter
	Network Adapter	VMware Virtual Ethernet Adapter for VMnet1
	Network Adapter	VMware Virtual Ethernet Adapter for VMnet8

Notes

	The gaming graphics score is based on the primary graphics adapter. If this system has linked or multiple graphics adapters, some software applications may see additional performance benefits.
	Caution: Based on the results of the WinSAT Disk assessment, your system drive may have slower response times under some workloads. Performance results will depend on the specific applications used and the amount of memory available. If your experience is satisfactory, no action is needed.

Comments
log file inclosed - EDIT, additional: This log was after I split the file into four equivilant files. it did the same thing when I tried with one large file. thoguth I would capture teh log when woirking with smaller files as that appears to be what is preferred.

Rich DeRuiter

https://community.logos.com/discussion/comment/275972#Comment_275972

6747.Logos4.logThank you.

The log shows the problem with the PBB, though I don't recognize the "Sinai.Message" error stands for (sounds ominous).

Were there not any other log and txt files in the directory? This one is the most important and most helpful, but the others may also contain helpful information.

You say that you divided the file into four parts. Did you try to compile all four parts together, or one at a time?

I hope programmers see this one, because it's all a bit new for us.

Brent Hoefling

https://community.logos.com/discussion/comment/275974#Comment_275974

that was the only one (I used the CTRL-launch method to engage logging). and yes, I saw the messages there as well, but meant nothing to me, even as an application repackaging engineer. [;)]

Melissa Snyder

https://community.logos.com/discussion/comment/275981#Comment_275981

that was the only one (I used the CTRL-launch method to engage logging). and yes, I saw the messages there as well, but meant nothing to me, even as an application repackaging engineer.

Hi Brent,

Does your source document(s) contain any nested tables?

Rich DeRuiter

https://community.logos.com/discussion/comment/275981#Comment_275981

that was the only one (I used the CTRL-launch method to engage logging). and yes, I saw the messages there as well, but meant nothing to me, even as an application repackaging engineer.

The column on the far left is the date/time stamp (obviously). The next is the thread # of the event being processed. Then the event status (Info/Warn/Error are the three I see typically). Then the info, the warning or error message itself.

In your log, the last three lines show the error ("Sinai.Message Failed to load image from C:\...\temp\tmp4???.tmp") on thread 22. Looking up the list, we see thread 22 is working on the PB conversion utility.

What I don't know is if "load image" means that it could not load a graphical image, or whether it could not load a part of the data 'image' of the compiled resource stored in the tmp file (which is my assumption). (However, if your docx file includes images, try compiling without them and see what happens.)

Have you successfully converted any files into a working PBB? If not, try something very short (one page, or less). If that fails, post the logs here too.

One thought that just crossed my mind is that you might want to try running this with your anti-virus turned off (or 'paused'). Before doing that, I'd disconnect from the internet and any other network you're on. My thought here is that your anti-virus may be protecting the file while it scans it. Turning it off temporarily may allow the software/system to deal with the issue of the anit-virus not letting go of the files quickly enough. -- I know. It's a long shot.

Another long-shot: You may also try turning off everything in your system tray that you can safely turn off, make sure L4 is the only program running, and start the process and walk away from the computer until it finishes or crashes. If the issue is system resources, this may just get you over the hump.

Brent Hoefling

https://community.logos.com/discussion/comment/275988#Comment_275988

I dont think so, but will double check. unfortuantley that is going to take a long time

Brent Hoefling

https://community.logos.com/discussion/comment/275990#Comment_275990

There are many tables (I am double checking for nesting, but I don't recall doing that) - but no images. does the same thing with AV disabled, and i am already running a lean-system, nothing to unload/not load in task manager.

Melissa Snyder

https://community.logos.com/discussion/comment/276000#Comment_276000

There are many tables (I am double checking for nesting, but I don't recall doing that) - but no images. does the same thing with AV disabled, and i am already running a lean-system, nothing to unload/not load in task manager.

There is a known issue with nested tables causing the same errors, which is why I asked. It might help us to get a copy of your source document if you don't mind. If you don't want to post it here, you can also send it to logos4feedback@logos.com.

Brent Hoefling

https://community.logos.com/discussion/comment/276001#Comment_276001

ok, there are some images i forgot about. but no nested tables that i could find. would small images cause it to crash. emailing the docx

Rich DeRuiter

https://community.logos.com/discussion/comment/276060#Comment_276060

ok, there are some images i forgot about. but no nested tables that i could find. would small images cause it to crash. emailing the docx

There have been reports of issues with images, but usually these are reported as the images not showing up after conversion. This typically happens when the image is inserted into the document by copy/paste rather than through the Insert menu/tab in Word.

I'm not sure, though, if all image types have been thoroughly tested. So it's possible that your images are causing the problem, not because of their size, but because the compiler doesn't know what to do with the image format. Since I haven't tested this feature much, I can only confirm that jpg images seem to work. I don't know if gif, bmp, or Word's clipart (wmf), or some of the other formats will work.

You could try a 10 page sample with/without and see if that causes the problem, though I suspect that with a document your size there is lots of room for other unknown issues to creep in.

Your best bet, IMHO, is to follow Melissa's advice and send your file in for review by the support/development team.

Brent Hoefling

https://community.logos.com/discussion/comment/276076#Comment_276076

thanks. already sent. I will do some more experimenting today, as I am sure the logos support folks arent working on stuff all weekend.

Brent Hoefling

https://community.logos.com/discussion/comment/276232#Comment_276232

to close this thread - thanks to logos. my issue was apparently one or more nested tables. the new 4.3 sr1 fixed the issue and it converted without a hitch. awesome!!