[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference vaxuum::online_bookbuilding

Title:Online Bookbuilding
Notice:This conference is write-locked: see note 1.3.
Moderator:VAXUUM::UTT
Created:Fri Aug 12 1988
Last Modified:Mon Jul 15 1991
Last Successful Update:Fri Jun 06 1997
Number of topics:440
Total number of notes:2134

423.0. "Exceeded memory errors With V2.0" by ELUDE::GREMBOWICZ () Wed May 01 1991 12:03

    I'm getting an Exceeded memory capacity error on my bookbuild.
    
    We just upgraded to DOCUMENT V2.0 and the Writer's Toolkit.  I got the
    error when I built to the BOOKREADER destination using CUP.ONLINE.
    
    A little history:
    
    A couple of weeks ago (before the installation), the online bookbuild
    got memory exceeded errors. The culprit seemed to be DGAPPA.SDML, which
    had two very long formal examples.  To correct the problem, I added
    lots of <valid_break> and <online_chunk> tags.  (Yes, I've heard that
    you're not supposed to need  <online_chunk> tags in formal elements, 
    but it worked for me before on another book, so I tried it again.)  
    It worked.  My book built.  Great!
    
    With the new version of DOCUMENT and the Toolkit, I got errors (fatal,
    I believe) because I had <online_chunk> tags in formal examples.  So,
    yesterday, I took out the <online_chunk> tags.  My online build bombed.
    
    Here's part of the log:
    
    %TEX-I-LINETOOSHORT, Line too short - on page [1024]
    %TEX-E-NOROOM, Exceeded memory capacity:
    -TEX-I-MEMORYSIZE, Main memory size = 131072 words
    %TEX-I-SHOWCONTEXT, '                   \unhbox '
    %TEX-I-SHOWCONTEXT, '->\unhbox '
    %TEX-I-SHOWCONTEXT, '                      \voidb@x '
    %TEX-I-SHOWCONTEXT, '->\leavevmode '
    %TEX-I-SHOWCONTEXT, '               \kern \obeyedspacewd '
    %TEX-I-LINE, Error occurred on or around line number: 446
    %TEX-I-SHOWCONTEXT, ' '
    %TEX-I-SHOWCONTEXT, ' 'standard definition of city or town';'
    %TEX-I-FILENAME, 'DOCBLD:[RDBDOC.GDDD$REF]DGAPPA.TEX;8'
    -TEX-I-ONPAGE, on page [1295]
    
    %TEX-I-PAGESOUT, 1294 pages written.
    -TEX-I-OUTFILENAME, 'DOCBLD:[RDBDOC.GDDD$REF]DGPROFILE.DVI_BOOKREADER'
    %DOC-E-ERROR_FORMATTER, Errors found by the text formatter
    
    The .LOG, .LIS, and the DGAPPA.SDML file are available in 
    ROERG::USER1:[GREMBOWICZ.PUBLIC]:
    
    DGAPPA.SDML;4       DGPROFILE.LOG;57    DGPROFILE.LOG;56
    DGPROFILE_BOOK.LIS;54                   DGPROFILE_BOOK.LIS;53
    
    
    Thanks,
    
    Helen
    
    
    
     
         
T.RTitleUserPersonal
Name
DateLines
423.1<valid_break>VAXUUM::UTTMary UttThu May 02 1991 11:373
    <valid_break> should solve the problem in that context.
    
    Mary
423.2How many <valid_break> tags?ELUDE::GREMBOWICZThu May 02 1991 12:078
    Hi Mary,
    
    The examples do have <valid_break> tags in them---probably an average
    of a tag every 10-15 lines.  I'll try putting more tags in, but what's 
    a reasonable number?
    
    Helen
     
423.3Not the only book running out of memoryWEORG::JALBERTThu May 02 1991 20:2016
Hi Mary,

I work with Helen in NUO and her book is not the only book that is running
out of memory. We have at least 3 others. One of them was running out of
memory before we installed V2.0 though. The other two are running out of
memory on a formal table and a formal example. The formal table has 
<TABLE_ATTRIBUTES>(multipage\wide\maximum\controlled) and has 
<TABLE_ROW_BREAK>(FIRST) and (LAST) tags. I don't know what else to
do with a formal table to make it not bomb for Bookreader.

The formal example that is bombing has <VALID_BREAK> tags every 10 - 15
lines. I am really stumped and getting very frustrated with this. To me
it shouldn't be running out of memory on formal anything's. 

Sally

423.4CUPMK::ROBINSONJohnWed May 08 1991 12:516
I'm having a similar problem, with a "bookreader-only" book.  In my case,
I've replaced online popups containing bulleted lists with hotspots and
hotspot targets.  As online popups, the book builds.  As hotspot targets,
the "exceeds memory capacity" error occurs.  Why is there a difference between
the two?
423.5VAXUUM::UTTMary UttWed May 08 1991 13:011
    Please post the log file from the failed build.
423.6workaroundVAXUUM::UTTMary UttThu May 16 1991 10:328
    This was fixed offline with a workaround which allows the use of
    <online_chunk> in formal elements. The problem needs further
    investigation, but if anyone else is having this problem, send
    mail.
    
    Thanks,
    
    Mary
423.7Still having "memory exceeded" problemCTHQ3::BMITCHELLAny noun can be verbedMon Jul 01 1991 14:1244
 I'm also having the memory exceeded problem discussed in this note. I posted
 a note about in the DOCUMENT conference and got a pointer to this file.  I've
 tried the workarounds suggested here (specifically, using <TABLE_ROW_BREAK>s 
 in the tables that seem to cause the problem, and adding <SET_ONLINE_TOPIC>
 (HEAD2) at the beginning of the whole thing (we're not using any <HEAD3>s))
 but that hasn't helped.

 I've got a large document being built from about 80 .SDML files.  The Post-
 Script version works fine, and the Bookreader build worked fine until 
 VAX DOCUMENT was upgraded to V2.0 on our system, which may or may not have 
 something to do with it - we added two appendices to the document since we 
 last processed it with V1.2-B of DOCUMENT, and the problem seems to be with 
 the tables in one of the appendices.

 The pertinent section of the log file now looks like:

%TEX-I-LINETOOSHORT, Line too short - on page [223]
%TEX-E-NOROOM, Exceeded memory capacity:
-TEX-I-MEMORYSIZE, Main memory size = 131072 words
%TEX-I-SHOWCONTEXT, '...mpcsB \endgraf \squashprevdepth }'
%TEX-I-SHOWCONTEXT, '                                          }\fi \fi \iftempf
lag '
%TEX-I-SHOWCONTEXT, '->\body '
%TEX-I-SHOWCONTEXT, '              \let \next \iterate \else \let \next \relax \
fi \next '
%TEX-I-SHOWCONTEXT, '...artfalse \fi \settablerowbox '
%TEX-I-SHOWCONTEXT, '                                          \emittablerow 1\n
exttablero...'
%TEX-I-LINE, Error occurred on or around line number: 13482
%TEX-I-SHOWCONTEXT, '\\}'
%TEX-I-SHOWCONTEXT, '   '
%TEX-I-FILENAME, 'USER06:[TOOLS.Q3FY91]Q4_PORTFOLIO.TEX;7'
-TEX-I-ONPAGE, on page [223]

%TEX-I-PAGESOUT, 222 pages written.
-TEX-I-OUTFILENAME, 'USER06:[TOOLS.Q3FY91]Q4_PORTFOLIO.DVI_BOOKREADER'
%DOC-E-ERROR_FORMATTER, Errors found by the text formatter
$ exit $status + 1 + f$verify(verify_context)
  TOOLS        job terminated at  1-JUL-1991 12:02:52.62


  Any help will be appreciated.  Regards,

   - Bruce
423.8Mary works Magic!CTHQ3::BMITCHELLErrrrorr prowneWed Jul 10 1991 11:512
    Re .7:  FYI, Mary Utt kindly helped me solve this problem offline with
    the fix mentioned in .6 (Thanks Mary!). 
423.9Thank *you* !VAXUUM::UTTMary UttWed Jul 10 1991 11:501
    
423.10yawn - another miracle routinely done :-)EPS::DEVRIESBy their notes ye shall know themFri Jul 12 1991 12:235
.8 >         -< Mary works Magic! >-

Why the exclamation point?  We knew it all along!

Mark
423.11Magician or Engineer same thing nowadaysMJFITZ::FITZELLgot those multi authoring cross platform bluesFri Jul 12 1991 14:525
    		-< Mary works Magic! >-
    Yep just walk by her office sometime and you can hear the magic
    incantations floating out.
    
    &*^%$#@TEX *&^%@$#system 
423.12Thanks, guysVAXUUM::UTTMary UttFri Jul 12 1991 16:063
    I get by with a little help from my friends!
    
    Mary
423.13Hip Hip HoorayIJSAPL::KLERKZeal matched only by audacityFri Jul 12 1991 20:2815
  Before Mary gets too excited - I think all of the V2 people have been
  wonderful in their own little ways to solve problems for us before customers
  found out.

  A thank you to all.

  And I fear the worst for the future now all have moved to different places,
  starting with Tortilla Flats...

  (I got a job opening message on cleaning the CUIP/DOCUMENT area recently.
  Lousy pay (no weekly return trip to Amsterdam) but interesting to anyone
  who wants to have a peek into the Secrets Of DOCUMENT now they are all gone)

  Theo