summary refs log tree commit diff
diff options
context:
space:
mode:
authorgiraffedata <giraffedata@9d0c8265-081b-0410-96cb-a4ca84ce46f8>2019-03-13 21:38:59 +0000
committergiraffedata <giraffedata@9d0c8265-081b-0410-96cb-a4ca84ce46f8>2019-03-13 21:38:59 +0000
commita89994b0245cf4ba40222bd0b66fce80bc9bc4a4 (patch)
treed1ca1c0138d15fb38c0e0f143bd575fd81fee828
parentebfec1b842c189ee719b94208ff162b1d188b728 (diff)
downloadnetpbm-mirror-a89994b0245cf4ba40222bd0b66fce80bc9bc4a4.tar.gz
netpbm-mirror-a89994b0245cf4ba40222bd0b66fce80bc9bc4a4.tar.xz
netpbm-mirror-a89994b0245cf4ba40222bd0b66fce80bc9bc4a4.zip
miscellaneous update
git-svn-id: http://svn.code.sf.net/p/netpbm/code/userguide@3569 9d0c8265-081b-0410-96cb-a4ca84ce46f8
-rw-r--r--pamtopng.html6
1 files changed, 4 insertions, 2 deletions
diff --git a/pamtopng.html b/pamtopng.html
index 00223f16..64b39e72 100644
--- a/pamtopng.html
+++ b/pamtopng.html
@@ -271,8 +271,10 @@ gradually improve the display as more data arrives.
 <p>When you specify this option, <b>pamtopng</b> must hold the entire image in
 memory at once, whereas without it, the program holds only one raster row at a
 time.  If you don't have enough memory for that, you might suffer extreme
-slowdowns or failure.  <b>pnmtopng</b> does not have this limitation (it holds
-only one row at a time in memory even when generating an interlaced PNG).
+slowdowns or failure - not just in the process running <b>pamtopng</b>, but
+potentially throughout the system that shares memory with it.  <b>pnmtopng</b>
+does not have this limitation (it holds only one row at a time in memory even
+when generating an interlaced PNG).
 
 <p>This option was new in Netpbm 10.86 (March 2019).