[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

57.0. "Ran out of memory now what do I do?" by CDROM::JAGGER () Thu Dec 29 1988 15:31

The following:

<EXAMPLE>(Creating the Popup Dialog Box\35)
  <CODE_EXAMPLE>
  <INCLUDE>(dub5:[harmony.xwindow.orig.xtoolkit]35_top.c)
  <ENDCODE_EXAMPLE>
  <CODE_EXAMPLE>
  <INCLUDE>(dub5:[harmony.xwindow.orig.xtoolkit]35_bottom.c)
  <ENDCODE_EXAMPLE>
<ENDEXAMPLE>

gave me the following error:

%TEX-E-NOROOM, Exceeded memory capacity:
-TEX-I-MEMORYSIZE, Main memory size = 131072 words
%TEX-I-LINE, Error occurred on or around line number: 4301
%TEX-I-SHOWCONTEXT, '            main\_wid'
%TEX-I-SHOWCONTEXT, '                     get, "Info",                /\* parent and name \*/'
%TEX-I-FILENAME, 'DUB5:[HARMONY.XWINDOW.DEVEL.XTOOLKIT]XTOOLKIT_MOD3.TEX;1'
-TEX-I-ONPAGE, on page [83] 

%TEX-I-PAGESOUT, 82 pages written.
-TEX-I-OUTFILENAME, 'DUB5:[HARMONY.XWINDOW.DEVEL.XTOOLKIT]DECTOOLKIT_BOOK.DVI_BOOKREADER'
%DOC-E-ERROR_FORMATTER, Errors found by the text formatter

Should I break up the file into more pieces? Is this problem due to the 
ONLINE DOCtype that I used? The original person who created the book says she 
split  the example into two parts so that it would work with the ESDP Style 
15B Doctype, to output to a postscript printer.

Thanks 
TOM
T.RTitleUserPersonal
Name		DateLines
57.1CLOSET::UTTThu Dec 29 1988 15:5610
    Tom-
    
    Will you send me the 35_top.c and 35_bottom.c files, or send me a
    pointer to them? I suspect they are quite large (that's usually the
    case when TeX runs out of memory), but I see no reason why that coding
    would not work for the online doctype. 
    
    Thanks,
    
    Mary
57.2I ran out of memory too ...PSYCHD::MICHAELSKaren MichaelsTue Mar 14 1989 15:30274
When I try to build my book with changebars, TEX runs out of memory.  But when I
build without changebars, it builds fine.  The following is my logfile.  Do you 
have any idea what my problem may be?

     ---Karen

-------------------------------------------------------------

$	set noon
$	sh log sys$node
   "SYS$NODE" = "ORPHAN::" (LNM$SYSTEM_TABLE)
$	sh process

14-MAR-1989 13:35:33.95                      User: MICHAELS    
Pid: 2A0002A7   Proc. name: BATCH_568        UIC: [IPSE,MICHAELS]
Priority:   4   Default file spec: PSYCHD$DUA0:[MICHAELS]
$	exit 
$ set def [michaels.junk]
$ copy spec_src$:SPECIFICATION.SDML [].sdml_temp
$ DOCUMENT SPECIFICATION.sdml_temp online book -
 /NOPRINT/CONTENTS/INDEX/COND=BOOKREADER_OUTPUT
%DOC-I-IDENT, VAX Document V1.1
[ T a g    T r a n s l a t i o n ]...
%TAG-I-DEFSLOADD, End of Loading of Tag Definitions
%TAG-I-LCL_MSG01, Using online bookbuilding tools, 16-JAN-89 baselevel
%TAG-I-SETCONDTN, Setting condition BOOKREADER_OUTPUT
   on line 1 of file PSYCHD$DUA0:[MICHAELS.JUNK]SPECIFICATION.SDML_TEMP;
%TAG-I-SETCONDTN, Setting condition relation_info
   on line 1 of file PSYCHD$DUA0:[MICHAELS.JUNK]SPECIFICATION.SDML_TEMP;
%TAG-W-TAGNOTPRE, at tag <RUNNING_TITLE> on line 732 in file
   SPEC_SRC$:IPSE_SPEC_DEP_REC.SDML
   Tag <RUNNING_TITLE> invalid unless preceded by TEMPLATE_SECTION_ATTRIBUTES
%TAG-W-TAGNOTPRE, at tag <RUNNING_TITLE> on line 128 in file
   SPEC_SRC$:IPSE-SPEC-UTILITIES-MERGER.SDML
   Tag <RUNNING_TITLE> invalid unless preceded by TEMPLATE_SECTION_ATTRIBUTES
%TAG-I-ENDPASS_1, End of first pass over the input
[ T e x t    F o r m a t t i n g ]...
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOSHORT, Line too short - on page [5]
%TEX-I-LINETOOLONG, Line too long by 15.58949 points
-TEX-I-ONPAGE, on page [20] 

%TEX-I-LINETOOLONG, Line too long by 15.58949 points
-TEX-I-ONPAGE, on page [20] 

%TEX-I-LINETOOLONG, Line too long by 79.32578 points
-TEX-I-ONPAGE, on page [20] 

%TEX-I-LINETOOLONG, Line too long by 79.32578 points
-TEX-I-ONPAGE, on page [20] 

%TEX-I-LINETOOLONG, Line too long by 79.32578 points
-TEX-I-ONPAGE, on page [20] 

%TEX-I-LINETOOLONG, Line too long by 79.32578 points
-TEX-I-ONPAGE, on page [20] 

%TEX-I-LINETOOLONG, Line too long by 79.32578 points
-TEX-I-ONPAGE, on page [20] 

%TEX-I-LINETOOLONG, Line too long by 79.32578 points
-TEX-I-ONPAGE, on page [20] 

%TEX-I-LINETOOLONG, Line too long by 79.32578 points
-TEX-I-ONPAGE, on page [20] 

%TEX-I-LINETOOLONG, Line too long by 85.18265 points
-TEX-I-ONPAGE, on page [20] 

%TEX-I-LINETOOLONG, Line too long by 79.32578 points
-TEX-I-ONPAGE, on page [20] 

%TEX-I-LINETOOLONG, Line too long by 85.18265 points
-TEX-I-ONPAGE, on page [20] 

%TEX-I-LINETOOLONG, Line too long by 79.32578 points
-TEX-I-ONPAGE, on page [20] 

%TEX-I-LINETOOLONG, Line too long by 39.1697 points
-TEX-I-ONPAGE, on page [20] 

%TEX-I-LINETOOLONG, Line too long by 85.18265 points
-TEX-I-ONPAGE, on page [20] 

%TEX-I-LINETOOLONG, Line too long by 85.18265 points
-TEX-I-ONPAGE, on page [20] 

%TEX-I-LINETOOLONG, Line too long by 85.18265 points
-TEX-I-ONPAGE, on page [20] 

%TEX-I-LINETOOLONG, Line too long by 79.32578 points
-TEX-I-ONPAGE, on page [20] 

%TEX-I-LINETOOLONG, Line too long by 85.18265 points
-TEX-I-ONPAGE, on page [20] 

%TEX-I-LINETOOLONG, Line too long by 79.32578 points
-TEX-I-ONPAGE, on page [20] 

%TEX-I-LINETOOLONG, Line too long by 85.18265 points
-TEX-I-ONPAGE, on page [20] 

%TEX-I-LINETOOLONG, Line too long by 79.32578 points
-TEX-I-ONPAGE, on page [20] 

%TEX-I-LINETOOLONG, Line too long by 85.18265 points
-TEX-I-ONPAGE, on page [20] 

%TEX-I-LINETOOLONG, Line too long by 56.24294 points
-TEX-I-ONPAGE, on page [20] 

%TEX-I-LINETOOLONG, Line too long by 62.9981 points
-TEX-I-ONPAGE, on page [20] 

%TEX-I-LINETOOLONG, Line too long by 85.18265 points
-TEX-I-ONPAGE, on page [20] 

%TEX-I-LINETOOLONG, Line too long by 85.18265 points
-TEX-I-ONPAGE, on page [20] 

%TEX-I-LINETOOLONG, Line too long by 85.18265 points
-TEX-I-ONPAGE, on page [20] 

%TEX-I-LINETOOLONG, Line too long by 85.18265 points
-TEX-I-ONPAGE, on page [20] 

%TEX-I-LINETOOLONG, Line too long by 85.18265 points
-TEX-I-ONPAGE, on page [20] 

%TEX-I-LINETOOLONG, Line too long by 85.18265 points
-TEX-I-ONPAGE, on page [20] 

%TEX-I-LINETOOLONG, Line too long by 85.18265 points
-TEX-I-ONPAGE, on page [20] 

%TEX-I-LINETOOLONG, Line too long by 85.18265 points
-TEX-I-ONPAGE, on page [20] 

%TEX-I-LINETOOLONG, Line too long by 85.18265 points
-TEX-I-ONPAGE, on page [20] 

%TEX-I-LINETOOLONG, Line too long by 79.32578 points
-TEX-I-ONPAGE, on page [20] 

%TEX-I-LINETOOLONG, Line too long by 85.18265 points
-TEX-I-ONPAGE, on page [20] 

%TEX-I-LINETOOLONG, Line too long by 79.32578 points
-TEX-I-ONPAGE, on page [20] 

%TEX-I-LINETOOLONG, Line too long by 85.18265 points
-TEX-I-ONPAGE, on page [20] 

%TEX-I-LINETOOLONG, Line too long by 85.18265 points
-TEX-I-ONPAGE, on page [20] 

%TEX-I-LINETOOLONG, Line too long by 85.18265 points
-TEX-I-ONPAGE, on page [20] 

%TEX-I-LINETOOLONG, Line too long by 79.32578 points
-TEX-I-ONPAGE, on page [20] 

%TEX-I-LINETOOLONG, Line too long by 85.18265 points
-TEX-I-ONPAGE, on page [20] 

%TEX-I-LINETOOLONG, Line too long by 85.18265 points
-TEX-I-ONPAGE, on page [20] 

%TEX-I-LINETOOLONG, Line too long by 85.18265 points
-TEX-I-ONPAGE, on page [20] 

%TEX-I-LINETOOLONG, Line too long by 85.18265 points
-TEX-I-ONPAGE, on page [20] 

%TEX-I-LINETOOLONG, Line too long by 85.18265 points
-TEX-I-ONPAGE, on page [20] 

%TEX-I-LINETOOLONG, Line too long by 85.18265 points
-TEX-I-ONPAGE, on page [20] 

%TEX-I-LINETOOLONG, Line too long by 85.18265 points
-TEX-I-ONPAGE, on page [20] 

%TEX-I-LINETOOLONG, Line too long by 85.18265 points
-TEX-I-ONPAGE, on page [20] 

%TEX-I-LINETOOLONG, Line too long by 85.18265 points
-TEX-I-ONPAGE, on page [20] 

%TEX-I-LINETOOLONG, Line too long by 85.18265 points
-TEX-I-ONPAGE, on page [20] 

%TEX-I-LINETOOLONG, Line too long by 85.18265 points
-TEX-I-ONPAGE, on page [20] 

%TEX-I-LINETOOLONG, Line too long by 15.58949 points
-TEX-I-ONPAGE, on page [22] 

%TEX-I-LINETOOLONG, Line too long by 15.58949 points
-TEX-I-ONPAGE, on page [22] 

%TEX-I-LINETOOLONG, Line too long by 79.32578 points
-TEX-I-ONPAGE, on page [22] 

%TEX-I-LINETOOLONG, Line too long by 79.32578 points
-TEX-I-ONPAGE, on page [22] 

%TEX-I-LINETOOLONG, Line too long by 79.32578 points
-TEX-I-ONPAGE, on page [22] 

%TEX-I-LINETOOLONG, Line to
57.3VAXUUM::UTTThu Mar 16 1989 16:4510
    A similar problem recently was reported to me by mail. I looked into it
    and made some changes to the change bar stuff; these changes will be
    available in the next version of the online bookbuilding tools, which
    should be available early next week. I would appreciate it if you would
    rerun your book under that baselevel and let me know if you still have
    problems. 
    
    Thanks,
    
    Mary
57.4double check your coding, tooMARKUP::DEVRIESFixed in next versionWed Mar 22 1989 11:2676
    There are lots of things that could trigger the NOROOM error in
    the presence of change bars.  Sometimes the problem is in the TeX
    macros, as Mary's fix attests.
    
    Sometimes, though, the problem is incorrect SDML coding.  Below
    is a note taken from the DOCUMENT notes file describing a user error
    that triggered the memory-exhausted condition.
    
    Mark
    --------------------------------------------------------------------
    
                   <<< W7_:[NOTES$LIBRARY]DOCUMENT.NOTE;1 >>>
                    -< VAX DOCUMENT problems and questions >-
================================================================================
Note 729.1                     TEX-E-NOROOM error                         1 of 1
COOKIE::JOHNSTON                                     57 lines   7-MAR-1988 20:32
           -< <mark> in table and missing delimiter is the problme >-
--------------------------------------------------------------------------------

The user found the problem -- it was a combination of the infamous <mark>
tags and a missing delimiter in a table row.  The code shown below should have
had a delimiter (started a new argument) after "Autoloop":

<table>
.
.
.
<MARK>
.
.
.
<table_row>(<literal>(Bit<10>)\Autoloop - 
                                          ^^^^ delimiter should have gone here

Read/Write in Initialize, Diagnostic and Run States. Inoperable in the Reset 
State and when RESET_L is asserted.
When set to a 1, 
the SSI State machine is placed in write mode. The Storage Array Index
(SSI Control Reg bits<2:0>) must be initialized and the number of words to be tested must be 
written into the Transfer Word Count(SSI Control Reg bits<5:3>) when the SSI Control 
Register is written.
The IOP writes data into the storage array location indexed by The Storage 
Array Index by writing to the SSI Data register. After each word is written to 
the storage array, the storage array index is incremented. 
Once the Storage Array Index exceeds the Transfer Word Count, the Busy bit is 
set to a 1 and the SSI state 
machine will shift the data out to the target device. As each word is 
loaded into the shift register, the word is complemented in the storage array.
Once all the words have been shifted out the data is transferred into the 
target device's output latches. The data in the output latches will be loaded back into the shifter
and shifted back to the SAFE where it will be compared against the transmitted 
data. If a mismatch occurs, SSI Transfer Error(STE) bit<literal>(<9>) of the 
SAFE/IOP Status Register is set to a 1. A maskable interrupt to IOP will be 
generated.)
.
.
.
<ENDMARK>

<ENDTABLE>

Without the delimiter, the file went into a seemingly endless loop (27 
minutes to process a file that should take 3 minutes).  

Adding the delimiter, the file processed as expected.  This was surprising
because the lack of a delimiter should simply have forced the text to be
written in the wrong column.  And in fact, this is how the table processes if
the <revision> tag is removed.  The presence of the <revision> tag, enabling 
the <mark>, results in the near-endless loop. 

Either deleting <revision> (suppressing <mark>) or putting the <mark> tags 
inside the table row corrects the TEX-E-NOROOM error.


Rose
57.5pointer to lotsa notesMARKUP::DEVRIESFixed in next versionWed Mar 22 1989 11:3056
    There are lots of notes in the DOCUMENT notesfile dealing with revision
    bars, and several of them address problems exceeding memory capacity.
    Below is note 5.65, the directory of all DOCUMENT notes with the
    REVISION_BARS keyword.  You may wish to check into some of these
    notes if you continue to have problems.
    
    Mark
    ---------------------------------------------------------------------
                   <<< W7_:[NOTES$LIBRARY]DOCUMENT.NOTE;1 >>>
                    -< VAX DOCUMENT problems and questions >-
================================================================================
Note 5.65                        Keyword listing                        65 of 86
VAXUUM::ROBINSON "anna canna panna"                  40 lines   9-MAR-1989 16:19
                               -< revision_tags >-
--------------------------------------------------------------------------------

               <<< CLOSET::W7_:[NOTES$LIBRARY]DOCUMENT.NOTE;1 >>>
                       VAX DOCUMENT problems and questions
Created: 30-JUL-1987 18:40         1975 topics        Updated:  9-MAR-1989 09:52
                   -< Read Notes 1.1 and 5.1 before writing >-
 Topic  Author               Date         Repl  Title
--------------------------------------------------------------------------------
    43     TLE::MICHAELS     15-SEP-1987     3  TEX informationals about revision bars
    98    ATPS::SPM_FODEN    23-SEP-1987     2  %tag-w-nothidenam 
   120   MARTY::FRIEDMAN     28-SEP-1987     3  Change Bars
           TLE::SAVAGE       28-SEP-1987   120.1  Same here :-(
         CASEE::CLARK        29-SEP-1987   120.2  Change bars on a 3-page table are a mess
        VANISH::DINGLEY       1-OCT-1987   120.3  <try more frequent use>
   126   SLIMY::SEARLE       30-SEP-1987     9  Problems with <MARK> <ENDMARK that span multiple <PARAMITEM> tags?
        COOKIE::JOHNSTON      1-OCT-1987   126.1  Add more <mark><endmark> 
         SLIMY::SEARLE        2-OCT-1987   126.2  Narrowed bug down to <MARK> near <ALIGN_AFTER> tags, I think
          AITG::CARRASCO     17-NOV-1987   126.5  <MARK>ing <TABLE_ROW>s is a pain
   168  COOKIE::JOHNSTON     12-OCT-1987     1  Unmatched <mark> <endmark> gets real ugly
   246  IJSAPL::KLERK        29-OCT-1987     6  <update_range> runs DECTeX forever...
         DELNI::COLELLO      10-FEB-1988   246.6  merged files
   366  COOKIE::JOHNSTON      6-DEC-1987     7  Rumors about auto <mark> <endmark>
        LEROUF::STADTELMEYER  8-DEC-1987   366.2  CHANGEBAR V2.0 kick-off
        LEROUF::STADTELMEYER  9-DEC-1987   366.4  Phase 0 for CHANGEBAR V2.0
        LEROUF::STADTELMEYER  8-FEB-1988   366.7  <MARK>({BAR | ZIGZAG | WAVE}) for CHANGEBAR!
   385  RDGENG::VAL_K         9-DEC-1987     1  <MARK> problems
   551  DECWET::CUSTER       22-JAN-1988    11  <MARK> & <ENDMARK> tags create bogus spacing
        DECWET::CUSTER        2-FEB-1988   551.3  Within Code Examples
        DECWET::HUNT         16-FEB-1988   551.10  one-line change bar
   556   CASEE::BROWN        23-JAN-1988     3  Exceeding memory capacity on full book-build
         CASEE::BROWN        25-JAN-1988   556.2  Well-known .... but still a tricky little devil..
        IJSAPL::KLERK        25-JAN-1988   556.3  How about making a CASEE of it...
   610  DICKNS::WELLCOME      4-FEB-1988     6  Need help doing UPDATE of TOC
        DECWET::CUSTER       15-FEB-1988   610.2  <MARK>/<ENDMARK> within <HEAD> tags
   679  CONRAD::SERACK       22-FEB-1988     6  <MARK_DELETION> tag
   703  REGENT::GALLAGHER     1-MAR-1988     3  Did I break it?!
        REGENT::GALLAGHER     2-MAR-1988   703.3  
   729  COOKIE::JOHNSTON      7-MAR-1988     1  TEX-E-NOROOM error
        COOKIE::JOHNSTON      7-MAR-1988   729.1  <mark> in table and missing delimiter is the problme
   841   VIDEO::HASTINGS      7-APR-1988     0  How to get change bars with two column REPORT.TWO?
   867  VANISH::DINGLEY      13-APR-1988     9  more <mark> problems
  1185    JVAX::JOHNSON      14-JUL-1988     3  Changebar variants