Reg: Virtual Memory Problem in BOData Integrator XI System

Hello,
We are currently extracting data from a table with around 830,000 records and performing the necessary analysis and place it on our reporting database. While processing the data in our BODI XI batch jobs we are receiving the following error. The ulimit -m is set to unlimited. Is there any other setting which I should look out to resolve this issue. Thanks in advance.
Regards,
Vijay.
Error :
=====
(11.5) 09-24-09 17:11:56 (W) (1626232:0258) SYS-170114: memoryMonitor
                                                        Warning: Your system is running low on process virtual memory space. Available virtual memory is <2025> megabytes.
(11.5) 09-24-09 17:11:56 (W) (1626232:0258) SYS-170114: memoryMonitor
                                                        Warning: Your system is running low on process virtual memory space. Available virtual memory is <2025> megabytes.
(11.5) 09-24-09 17:11:57 (W) (1626232:0258) SYS-170114: memoryMonitor
                                                        Warning: Your system is running low on process virtual memory space. Available virtual memory is <2025> megabytes.
(11.5) 09-24-09 17:11:58 (W) (1626232:0258) SYS-170114: memoryMonitor
                                                        Warning: Your system is running low on process virtual memory space. Available virtual memory is <2025> megabytes.
(11.5) 09-24-09 17:11:59 (E) (1626232:0258) SYS-170117: memoryMonitor
                                                        Cannot continue executing the job due to insufficient process virtual memory.
(11.5) 09-24-09 17:12:00 (E) (852142:0001) SYS-170117: |Session LATAM_MATERIALMASTER_PULL|Workflow WF_LATAM_MM_Extract|Dataflow DF_LATAM_MM_Extract_Staging
                                                       1-4-Cannot continue executing the job due to insufficient process virtual memory.
(11.5) 09-24-09 17:12:03 (E) (852142:0001) SYS-170117: |Session LATAM_MATERIALMASTER_PULL|Workflow WF_LATAM_MM_Extract|Dataflow DF_LATAM_MM_Extract_Staging
                                                       1-4-Cannot continue executing the job due to insufficient process virtual memory.

Hi,
Can you please check whether the server is running or is it in a starting state.
I believe that your server has not completely started . Please check.
Thanks & Regards,
Vijith

Similar Messages

Virtual Memory problem

I needed more RAM in my machine. So in the interim (while I was waiting for the RAM to arrive), I bumped the Virtual Memory setting to its maximum from the default value of RAM+1MB.
When I restarted the computer, it started to boot and then failed with error 113. I looked the error up and it said I had a probable hardware problem associated with Virtual Memory.
I tried all sorts of things to get the computer started again but the only way I found to get booted again was with the original Install CD.
After starting with the CD, I trashed the Memory pref file thinking it was controlling my VM setting. Nope.
Ultimately, I had to do a fresh install of the OS (9.2.2) to get control of the machine again.
What a pain.
Was there some other way to reset my VM setting back to default besides what I did?
Gary

Hi, Gary -
Getting rid of the VM setting may take trashing both the Memory Preferences and the System Preferences files (both of those files show a new mod time when I make an adjustment to that setting in the Memory control panel).
For what it's worth, if the new RAM you get takes the total installed RAM to 1.0GB or more, VM will be disabled automatically in OS 9. If this is the case, you may need to adjust the Preferred memory allocations for some programs upwards.
On the other hannd, you'll probably notice that the machine responds a bit faster with VM off. My G4 has 768MB RAM, so I can have VM on. However, I keep VM off - I prefer the resulting behavior of the machine.
To allow for VM being off I've increased the Preferred allocations for most programs, some a little, some a lot. For example, I've increased the Preferred setting for Diablo II to about 480,000 to allow for VM being off (the specs for DII state VM must be on, but that's not true provided enough RAM is made available to it).

Virtual memory in a hyper-v failover cluster

Hi all,
We have a window 2008 R2 hyper-V failover cluster working fine. It has two hosts, with 104 GB of memory on each of them.As I added new virtual instances I had been updating memory.
The point is that as I do that page file for virtual memory has been growing and now System volumen has only 20 GB free space.
I had like to go on adding memory for new virtual instances, so I need to fix this problem. Which is the recommended configuration for this? Can I disable virtual memory as long as I have an enormous quantity of physical memory available?
Thank you very much.
Kind regards,
David.

Hi,
that enormous page file at Hyper-V Servers make no sence.
We do not need to configure virtual memory for physical Memory that is assigned to VMs.
Check this for more informations:
http://blogs.technet.com/b/rwagg/archive/2010/03/08/how-big-should-pagefile-sys-be-on-a-server-2008-hyper-v-server.aspx
Hope that helps
Regards
Sebastian

JVM virtual memory footprint

I'm running java processes (specifically Tomcat) on a linux system with not too much available memory and I run into a lots of problems as java seems to consume a lot more memory than it would need.
To understand the problem I created this "unit test":
[root@vps download]# ulimit -v unlimited
[root@vps download]# java -version
java version "1.5.0_14"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_14-b03)
Java HotSpot(TM) Client VM (build 1.5.0_14-b03, mixed mode)
[root@vps download]# ulimit -v 230000
[root@vps download]# java -version
java version "1.5.0_14"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_14-b03)
Java HotSpot(TM) Client VM (build 1.5.0_14-b03, mixed mode)
[root@vps download]# ulimit -v 220000
[root@vps download]# java -version
Error occurred during initialization of VM
Could not reserve enough space for object heap
Could not create the Java virtual machine.As you can see the java vm won't start up when the allowed virtual memory is under 230 Mb, which is an amount of memory I can't give java in a virtual server. I have tried limiting the memory consumption with any memory option I could find (starting with the famous -Xmx and -Xms ones) but always with the same results and problems.
By running Tomcat and using "top" I noticed java requests over 250 Mb virtual memory, while actually using only around 35 Mb. I would be glad to allow this process to reserve up to 100Mb in virtual memory, but over that seems crazy, since I perfectly know my tomcat instance will never require that much memory and since I cannot "afford" all that memory usage from a single process. With that kind of consumption I can't even stop tomcat using the ordinary script (the shutdown.sh script will start another vm to send the stop signal to tomcat but since the first one is already consuming 250 Mb virtual memory and the second one tries to allocate as much I will get the heap error message as my server can't allocate that much total memory on top of the other processes).
What solutions are there to stop java from reserving memory it won't use?

ingoio256 wrote:
First I quote yourself from another (someway similar) thread:
"Under Linux, the OS allows over-allocation of memory (which means it can reserve memory that it doesn't have the physical RAM or swap file to back it up with)"
If I was able to do that my problems would be solved: in fact my system doesn't have enough physical+swap memory, but since a lot less will be used by java processes if I was able to instruct the system to allocate it even if it's not available I would have my problems solved.
Any idea about where I can find help on doing that?It may already be doing that; under Linux, I believe it only looks for memory to back up the allocation when the page is touched. Whether the java process touches all the memory it allocates, I don't know. Maybe it behaves differently when there's no page file.
The second question is the following:
I noticed java processes on the windows system don't use as much virtual memory as it happens in my vps: the reported virtual memory allocation is just slightly above the used physical one. Does that depend on a different implementation or does it happen after some time the jvm is running, with unused virtual memory being given back to the system? If the latter was right it would partly ease the problem as I would just need for the java process to be running for a while and then I would have some system resources released. If it's not the case... how can I have linux behave similarly to windows? As in this case it seems more efficient ;)Regarding the memory usage difference, I don't know why that is.
I've seen people say that the Sun JVM doesn't return memory to the OS after it allocates, but I'm not sure of this. This is another aspect that a different JVM implementation could help with. I think IBM and BEA both have their own implementations you could check out.

Pagefile/virtual memory vs. ram

is it better to run straight in the ram than rather in the pagefile?
what is better?

Different Types of Memory (HD vs. RAM):
The two, most common, kinds of memory in your computer: Hard Disk space which is usually measured in Gigs or Gigabytes(GB), and RAM which is measured in Megabytes (MB)
Hard Drive: Think of your Hard Drive (HD) as storage space. It is used for long term storage of large amounts of data. The HD itself is a metal disk on which your data is saved as magnetic zeros and ones (binary data). When you turn your computer off, any data you "saved" onto the HD will remain there to be accessed again the next time you turn your computer on. Reading files and data from the HD is fairly slow compared to the speed of RAM. When you turn your computer on, it reads the operating system, or OS, from the Hard Drive and loads it into RAM where it can be accessed very quickly.
RAM: RAM is better referred to as Memory. RAM is a "chip" that plugs into a slot inside your computer. Because it has no moving parts like a HD, data stored in RAM can be accessed very quickly. When you open a file that you saved on your Hard Drive, a copy of the file is loaded into RAM where you can make changes to it. You must then "save" the file if you want to make the change a permanent one. Saving the file updates the information which is saved on your HD. When you quit an application, the data for that program and any files you had open are removed from the RAM, freeing up the memory to be used by the next application. When you turn off your computer, all the data which was held in RAM is removed, so any unsaved files will be lost. The next time you turn your computer on, the OS will be loaded into RAM again. That is another reason why it's good to reboot your system before taking on any memory hungry applications (online games) if you have had your System on for awhile.
Virtual Memory: On a PC(most operating systems) you can turn on Virtual Memory in order to increase your RAM when you can't install an actual chip to add more physical memory. Virtual Memory is very slow because it is using the HD (slow) to store data which is normally stored in RAM (fast). If you must use Virtual Memory, only set it to twice the amount of the physical memory which is installed. For example, if your computer has 32 MB of physical RAM installed, set Virtual Memory to a maximum of 64 MB. If you change your Virtual Memory settings; you must restart your computer to have Virtual Memory settings take effect.
If you are getting a message on your PC about not having enough memory, it is probably a problem with your RAM and not your Hard Drive space. Do not start deleting files off of your HD to try and free up more memory. You either need to install more RAM (memory chips), quit other open applications to free up some RAM, or increase the memory requirements for the specific application where you are experiencing the problem.

Low Virtual Memory-Satellite M115 S3154

I constantly have Low Virtual Memory problem and have to clear and reset my paging file regularly. System memory 504 Mb RAM on Satellite M115 S3154. Have paging file min & max set at 1000. Upon clearing paging file and reset everything runs fine for a while then slowly grinds to a halt until I can't do anything until I reset again. HAve also tried running System Mechanic to manage virtual memory, but problem continues. Any help would be greatly appreciated. I seem to have already done what previous posts have suggested. Thanks!
Solved!
Go to Solution.

stropical wrote:
When you say increase the physical memory what I have to do? Thanks
Increasing the physical memory means increasing the RAM, in this instance. Your computer spec says 2GB but upgradeable to 4GB. Here is a one person’s recommendation on how much virtual memory should be allocated, i.e., 2-3X your memory. (Some will recommend min if you have enough memory.)
http://www.gilsmethod.com/how_to_optimize_windows_vista_swap_file

Memory problem with after effects... help!

hello,
i am having a strange issue where my pc will lock up after i minimize After Effects and try to access the file (quicktime, wmv, etc...) i just created. i am new to AE but i'm sure this isn't normal.
any help here would be greatly appreciated.
bilbob7624

Mmh, if it gives you virtual memory errors, you have too many system processes running and your RAM is full. Not directly related to AE, but it explains the delays. What happens is, that any additional program you launch on such a crammed system forces other memory pages to be moved into the swap file so that RAM becomes available, making things slow in terms of user feedback. it also sometimes effectively disables file associations (it's a timeout in Windows' internal messaging system). Do you by any chance use Render Multiple Frames Simultanously? If so, try to render without it. Other than that there is not much you can do but sift through task manager and your Services control panel and see, which applications and tools consume al lthe resources, then try to disable unnecessary stuff. This would in particular apply to the millions of tools that place themselves in the system tray like virus scanners, update checkers, messengers, other widgets. Also close down other programs during rendering. Even a simple thing like a web browser can consume more than 120 MB of RAM (Firefox with a few extensions).
Mylenium

CFMX 6.1's Virtual Memory Use problem!!

I appologise for the long post in advance...
Ok... so I have this script that, using cfdirectory, will
check a directory for any files that may have been uploaded, if
there are files, it loops through the results and reads the files
one at a time, line by line, using the FileReader.cfc (Uses the
Java FileInputStream, InputStreamReader, and BufferedReader to
provide a way to incrementally read large files). The files are
just pipe "|" delimited data, each line represents a record for a
db table.
Now as it's reading each line, it will perform some basic
string parsing to clean up the file line to make sure the data is
valid, blah blah blah and then it will write that "cleaned" line to
another file using FileWriter.cfc (Java component once again). Once
it's completely done reading the original file, it will close it
and it will open the new "cleaned" version of the file, read it
(FileReader.cfc), create an INSERT statement and then update the
database table.
Now... this all works GREAT... until it has to loop through
more than a few files... 3 - 4 files are NO problem! works like a
charm, but throw 6 - 8 files at it and it dies, not a timeout mind
you but an actual "java.lang.OutOfMemoryError" (now, I've tried
making all the files exactly the same (just changed the name) and
the weird thing is, it takes longer and longer to process each as
it goes through the loop... I have the script write some stats as
it's looping:
FILE 1 STATS
Name: COA0607_Intranet1.DAT
Status: Import Successfull
Line Count: 32,971
Processing Time: 74,237ms
FILE 2 STATS
Name: COA0607_Intranet2.DAT
Status: Import Successfull
Line Count: 32,971
Processing Time: 82,018ms
FILE 3 STATS
Name: COA0607_Intranet3.DAT
Status: Import Successfull
Line Count: 32,971
Processing Time: 94,476ms
FILE 4 STATS
Name: COA0607_Intranet4.DAT
Status: Import Successfull
Line Count: 32,971
Processing Time: 145,108ms
I know what you guy are probably thinking; "Woah man... CF
isn't really meant to do that kind of processing...", I know, trust
me I know... however, I really neeeeeed it too lol.
Ok, so as the script is running, I watch the Virtual Memory
use of jrun.exe, processing say 3 - 4 of these files brings up the
usage to approx 300,000k which yes, is a LOT but that's fine...
this process is meant to run at night via a Scheduled Task...
When I run more than 4 files, things start to get ugly, keep
in mind that these are EXACTLY the same files just re-named
differently. The script will start lagging BIG time and on the last
file (usually the last file) I'll see the memory usage spike from
350,000K all the way up to 600,000K and that's when it throws the
"java.lang.OutOfMemoryError" and dies... I've tried commenting out
the part of the script that updates the db, but still get the same
problem...
So... what gives? How come CF Server does this??? I mean, it
runs fine for the first few files... and then WAM, it dies... sorry
for the long post... any insight here is VERY much appreciated...
it would be AWESOME if the wonderful folks at Adobe could shed some
light on this for me : )
CFMX 6.1 version: 6,1,0,83762
Windows XP Pro SP2
Intel P4 2.8Ghz
1Gb of Ram

quote:
Originally posted by:
Mr Black
300M memory usage while using "incremental" file reader??
Looks like it is "incremental" only in the sense that it increments
memory usage. Did you try non-Java C/C++ file reader tags?
Well I did try cffile originally... and it didn't even run...
lol

Virtual Memory Allocation problem

When I run compile some source code in F90, I receive the following error message:
/usr/bin/ld: can't vm_allocate() buffer for output file of size 1699768758 ((os/kern) no space available)
What seems to be happening is that the system wants to allocate a large amount of memory. I have over 14 Gb of virtual memory available and over 2.5 GB of RAM available. Another forum ( http://www.archivum.info/gnu.gcc.help/2007-08/msg00083.html ) said the memory needs to be contiguous. I need to compile this, and I have sufficient memory to do so. What must I do to make this work?
I tried the following:
cd /usr/bin
sudo mv ld ld32
sudo ln -s ld64 ld
This did not solve the problem as now the error says:
ld64-62.1 failed: 32-bit pic-base out of range in atexitcommon from /usr/local/gcc/4.2.2-32/lib/gcc/powerpc-apple-darwin8.9.0/4.2.2/crt3.o

I'm assumming that your operating system is Windows NT 4, Windows 2000, or Windows XP. For others reading, this is a link to the above referenced KnowledgeBase article.
NI-DAQ does not require you to invoke the VirtualLock function. NI-DAQ will page lock the buffer passed to the SCAN_Start function. It is possible that, since the buffer has already been paged locked by your code, that there are insufficient resources (i.e., kernel-mode Page Table Entries (PTEs)) available for NI-DAQ to page lock the buffer.
Remove the invocation of the VirtualLock function and see if that helps.
Geoffrey Schmit
Fermi National Accelerator Laborary

Internal Hard Drives Disappeared, Finder Memory Problem

Hello Helpful Folks,
I recently installed an addional internal Hard Drive, and an additional 1GB SDRAM. This worked great for a day, but the next morning, after powering up, system was extremely sluggish, and after much deadline-induced impatient problem solving, has gone from bad to worse (system refuses to acknowledge existence of internal Hard Drives). I apologize in advance for the length of this post, but as
the devil is in the details, I figure too much info is better than not enough.
Following is a breakdown of my system: AS IT LAST WORKED; RECENT UPGRADES; and MY LAME ATTEMPTS AT PROBLEM SOLVING THAT HAVE MADE THINGS WORSE. Please don't interpret my all caps as shouting, just trying to organize this post for better clarity.
System is dedicated to Video Editing with FCP 3, running under OS 9.2.2. System is "off the Grid", i.e. no network, no internet, no printer, no gaming devices. System was purchased new in July 2001, by a friend. At one point I know this system had an Airport card, which was removed prior to my purchase in 2003. I can't remember what else it may have had installed in its history, but here's what it has now:
SYSTEM AS IT LAST WORKED:
**bold items are upgrades Original Owner or I installed with no apparent problems**
Power Mac G4 "Quicksilver" 2001
867 PowerPC G4, 256 L2, 2MB L3
-1 Stick "ValueRAM - KVR 133 x 64 C3/512" in PC 133 DIMM slot **
- "Virtual Memory" was turned off years ago due to conflict with FCP 3
-2 empty DIMM slots
-1 60 GB internal HD (Maxtor Ultra ATA/100), 1 partition, formatted HFS+, jumpered as "Master" on Internal ATA 2 ID=0 (which as I understand it is ATA/66 speed)
-1 Pioneer "Superdrive" DVD-R/W/CD-R/W on Internal ATA 0 ID=0
-NVIDIA GeForce2 MX with 32MB SDRAM in AGP Slot, feeding a 17" Apple Studio Display.
-PCI Display Card "formacGA7" - not attached to any external device, not sure what its intended purpose is.**
-3 Empty PCI Slots
-OEM Keyboard attached to Monitor's rear USB port.
-Microsoft 3 Button Wheel mouse with "IntelliEye" (wheel is 3rd Button) connected to Keyboard USB port (right side).**
-2 OEM FireWire (400) ports
-2 OEM USB (1) ports
Peripherals that have worked in various configurations with this system over the past 3 years:
-3 OWC Mercury Elite ("Oxford Chipset") Externally powered, External FireWire(400) 200GB Hard Drives, 1 partition each, formatted HFS+, daisy-chained to either of the FireWire ports.
-1 Canon GL1 MiniDV camera, attached either to the other FireWire port, or to the last drive in the chain, depending on my urgency/laziness factor. BTW, FCP 3 has worked flawlessly controlling this Cam for logging and Batch Capturing.
Applications on System Hard Drive that I have OEM CDs for:
-OS 9.2 - (I think I remember that OS X was removed from system due to conflicts shortly after original purchase)
-FCP 3
-DiskWarrior (version unknown, purchased from Alsoft in 2003)
-OWC Intech Hard Disk SpeedTools ver 3.5
Other CDs I have:
OEM CDs for Power Mac G4:
-Software Install, OS 9.2, CD vers 1
-Software Install, OS 10.0.4, CD vers 1
-Software Restore, OS 9.2 & 10.0.4 CDs vers 1, Discs 1-4 of 4.
-OEM Apple Hardware Test; Power Mac G4, SW vers 1.2.1
Applications on system Hard Drive that I don't have CDs for, that I rarely use, but I'd like to keep:
-After Effects 5.0
-QuickTime Player 6.0.2
-Toast Audio Extractor 1.1
-Toast Titanium 5.0.2
Applications on system Hard Drive I use if my wife is busy on our Windows XP machine:
-Photshop 6.0
-Microsoft Word & Excel
# of other Applications on System Hard Drive I either don't use or may be integral to the system: 260
# of Control Panels:
-Enabled: 34
-Disabled: 0
# of Extensions:
-Enabled: 174
-Disabled: 0
note: a number of the applications and extensions are for AOL, Quickbooks, Microsoft Money and the like, as well as other things I don't use (Airport, USB printers, Networking, etc.)
Smart things I did:
-Regularly made backup copies of my FCP projects to the external drives.
-Bought a copy of MacDrive so I can see what's on my External Drives on the XP machine.
-Printed out System Profile before I installed upgrades.
-Thoroughly searched this discussion board for and gathered as much info as I could before upgrading.
Dumb things I did:
-Made a copy, but not a clone, of my System Folder to one of the external drives when I first got it.
-Didn't keep any sort of separate log of what's on the External Drives.
-Never ran any sort of Disk Maintenance, even after one of the Externals crashed (DiskWarrior saved my butt on that).
-Ignored some of the advice on this discussion board.
Really dumb thing I did without even realizing it:
Captured all media for a rush job onto my internal system Hard Drive, as well as storing and using massive jpgs for the same job on that same drive...
Which led to painfully slow rendering times, and crashes caused by "Error: Out of Memory", which I interpreted as "Must buy more memory" and not "must make sure I'm not trying to edit media stored on system drive, especially with massive jpgs that I should reduce"
RECENT UPGRADES:
Here's what I did, and how I did it:
Turned off system, disconnected all External FireWire Devices, disconnected Monitor, opened case, touched various metal parts of case and power supply to discharge any Static, unplugged power cable.
-Installed 2 512MB sticks of "Lifetime" PC 133 SDRAM; total System RAM is now 1.5GB, all 3 DIMM slots now occupied.
-Installed 1 Maxtor "DiamondMax" Ultra ATA/133 100GB Hard Drive (8 MB buffer) as "Slave" (no jumper) in top of U-Carrier above System Hard Drive; attached to middle of original Apple ribbon cable, attached available power plug.
Taped spare jumper to inside of empty drive bay, noting origin and date. Did NOT push PMU button. Carefully closed case. Reconnected Monitor, did NOT reconnect any FireWire devices. Powered System on, but did NOT perform PRAM reset.
I don't remember the exact order of what happened next, but I think: System booted up normally, a window popped up saying a new drive had been found, would I like to intitialize it?, which I did as Mac OS extended, and then named. If I was instructed to restart, I did so, otherwise did not. Clicked on "about this Mac" and saw that it now showed 1.5GB RAM. I then went about moving Media/Render files off the System drive (and one of the Externals) onto the Internal Drive, with a combination of FCP's Media Manager, and dragging from the Finder. After files had copied, dragged Media/Render files from System Drive to Trash. Opened FCP project, had FCP re-link to new locations of missing files. Saved, closed, and re-opened project, set Capture/Scratch disc to new internal Drive. At some point I changed FCP's Memory Allocation from whatever it was to 512000KB Minimum, and 900000KB Prefered (and I hope I got all those zeroes right). Did NOT restart after changing Memory Allocation, unless a window popped up instructing me to do so, in which case I did. Re-opened my project, rendered a few thing at a noticeably increased speed, saved everything, emptied the Trash, shut everything down, and called it a night as it was 4:30 am.
A few hours later, I plugged the MiniDV and an External Drive into the FW ports and powered up the System. It was behaving extremely sluggishly. I would click on something, the pointer would turn into a wristwatch (sometimes with the minute-hand moving, sometimes not) and like an actual minute later, what I'd clicked on would open. All three drives were on the desktop, still had their files, and "About this Mac" still showed 1.5GB total Memory. So I powered down, disconnected the FW devices, waited a bit, and powered back up. Same sluggish response. I tried to open my FCP project file, and instead got a Window that said something to the effect of "The Application associated with this document could not be found". I think I tried to open FCP from the Applications folder on the System Drive and got the same message (I'd only had 3 hours sleep, no coffee, my client had died, and his family was coming for whatever I had in a few hours).
LAME ATTEMPTS AT PROBLEM SOLVING THAT HAVE MADE THINGS WORSE
Panic had set in, which never solves anything, so I don't remember what order I performed which tasks, between searching for clues in this forum, and convincing myself that that would be faster than trying to compose a question, waiting for a response, etc.
The first two things I did, and I can't remember which I did first (both from Keyboard Commands during Restart):
Rebuild Desktop
PRAM Reset
Neither of those solved the problem, so I continued.
I tried restarting without extensions.
I would get errors that said something like "Not Enough Memory to Open Finder".
I tried booting from Disc 1 of the Software Restore Disk, which only wanted to destroy my data.
I tried booting from the OS 10 disk, with the same result.
I was finally able to boot from the OS 9.2 Software Install Disk, and actually saw both internal drives on the desktop, and the 1.5GB RAM in About this Mac. I tried to allocate more memory to Finder, but was informed that "Cannot Perform Requested Operation. This operation requires versions above 8.0".
I think at this point I decided that I must have too many extensions, and started disabling ones I thought irrelevent to my cause (mostly anything that said "AOL", "Airport", "Ethernet", "Printer", "Modem", "Speakable", and a couple things called "Open TPT".
It gets worse. Then I decided to turn off some "unnecessary" things via the control panels, but somehow managed to disable the control panels themselves: AppleTalk, DialAssist, File Sharing, Modem, Mouse (as I saw that Microsoft Mouse was among the others), Remote Access, Speech, USB Printer Sharing, and possibly TCP/IP.
That certainly didn't help anything (though upon restarting from the OS 9.2 Disc I was able to see the extensions and control panels in their respective "Disabled" folders in the System Folder). But I still wasn't able to get more Memory to Finder.
So, I decided a few more PRAM resets might help, which succeeded in making both Internal Hard Drives disappear. I tried booting up from the DiskWarrior disc, but even the Mighty DiskWarrior couldn't find the drives. I performed the longer, in depth version of the Apple Hardware Tools tests, which reported that everything's fine (including the new RAM), but made no mention of the Hard Drives at all. The deadline having long passed, I shut the system down. I read through more posts and tech articles, etc.
I searched my External drives with MacDrive on my XP, and found the drive that has the copy of my System Folder (which shows all extensions and control panels as enabled); not sure if the Quicksilver will boot from that, I don't know what the Keyboard command for booting from a FireWire drive is (if there is one) and the drive itself only has 900MB of free space.
I can't find any reference to Internal ATA drives anywhere in the MacDrive documentation; if it was possible I'd put them into the XP, get the files off the Mac drives, reformat them and install OS9 from the Discs.
This is where I am now:
The Quick Silver is still powered down. I removed the Microsft mouse and replaced it with the OEM Apple mouse. I opened the case, and removed the PRAM/Backup battery (manufacture date: July 2001). Couldn't find my voltmeter, so took the bat to Radio Shack and bought a new one. Had the Radio Shack guy test the old one: it showed 3.69 volts still. Have not installed the new battery yet. The case is still open, waiting for any advice any of you might have to offer.
Thank you all so much for your patience in perusing and pursuing this.
Sincerely,
Patterson
Power Mac G4 Quicksilver 867 Mac OS 9.2.x 17" Studio Display, 512MB RAM

Thank you Rodney and John,
The jumpers are correct for both Maxtor Drives.
Rodney, you are correct in that the initial problem (slow rendering/"out of Memory" crashes) was caused by my not realizing I'd stupidly captured several GBs of media to my system drive, and not checking which drives those files were on (as I'd assumed I'd put them on one of my external media drives) once that problem presented itself.
Before I'd determined what I'd done, I bought the extra RAM. After I'd found the media files on the System Drive, and saw that my dedicated media drives were too full to easily move them, I decided to buy an additional Internal drive so that I could:
-Move the Media onto it relatively quickly and finish my urgent project.
-Juggle all my media into a more organized fashion for archiving (as most of my projects are on-going long-term affairs)
-Wipe it, Partition it, and clone my System Drive onto it, as a spare bootable drive in case my OEM System Drive failed.
Copying the Media files onto the New Drive and moving the System Drive's Media files into the Trash worked great: huge improvement in Rendering, etc.
Before shutting down for the night I Emptied the Trash, and was pleased with the amount of space I'd freed up on the System Drive.
My guess is that the System Drive was terribly fragmented, having been subjected to intense use over the past 5 years without any sort of Drive Maintainence, and deleting that massive amount from it in one shot caused my extreme system sluggishness upon Startup the next day.
My subsequent lame attempts to solve the sluggishnes ultimately resulted in my losing access to both drives.
Today, I replaced the Backup Battery, pushed the PMU, re-attached the AC, and Powered Up with the case open as per your suggestion.
It was trying for a few minutes (the gray screen went black at one point, and then returned to gray) before presenting me with the flashing question mark.
There was, however, a quiet but distinct "buzzing" sound that would alternate: 1 sec "buzz", one second silence, one second "buzz", one second silence, etc. coming from the drives, even after the "?" appeared.
I powered down, removed the Ribbon and Power Cables from the new "Slave" drive, and powered up again, with the exact same results.
I powered down, removed the Ribbon and Power cables from the original "Master" drive, reinstalled the Jumper on the New Drive as "Master", plugged the End of the Ribbon and the Power cables into the New "Master" drive and powered up. The screen went to the "?" within 20 seconds instead of 4+ minutes, and no more "buzzing".
I put the Apple Hardware Tools Disk in, ran the "long" test, and everything came out fine.
I have to abandon this for now, but thanks again for your previous advice, and any more you may have!
Cheers,
Patterson

Memory Problems with Adobe PDF iFilter for 64-bit

In preparation to rebuild my Windows Search Index, I installed the Adobe PDF iFilter for 64-bit on my system (Vista Business 64). When I finally rebuilt the index, I wasn't too surprised by what I saw happen, namely, the SearchFilter.exe process would kick in whenever I wasn't using the system and just eat RAM. One time I turned it on and it had allocated over 4,000 MB (and my system only has 4,030 MB available) so of course it was forcing all the other processes to hard fault (ie. everything was moving like molasses--for example, it took 20 minutes to put the thing to sleep). But I just let it do it's work, figuring that perhaps this was to be expected relative to the small library of PDF's that I've accumulated on my computer, ranging from LaTeX generated text files, to containers for hi-res scans. So, after a day and a half of basically not using my laptop, everything finally calmed down and I enjoyed the benefits of searching the content of my library from the Windows Start menu--for a short while.
However, to my dismay I've encountered the problem that this freezing of my computer would now occur after everytime I download a new PDF (in this particular case they were Google Books scans) and then left the computer to idle. Again, the SearchFilter.exe would allocate all of my RAM for itself and just push everything else onto the Virtual RAM, which means the SLOWEST possibly fetching you can get. I had to uninstall as this was making my computer unusable for 15-30 minutes after each idle. Everything is back in working order without the iFilter, but I would like to know if anyone has reported such problems on x64 systems. Obviously, I will also report the problem to Microsoft, since the search engine should certainly have the precaution to handle such memory problems.   However, it is a problem that is created by the Adobe PDF iFilter interacting with the Windows Search engine.

Hello,
We believe we have figured this out. It looks like it has to do with the length of the default folder location for the Adobe iFilter.
I was able to reproduce the issue and the following resolved it for me. See if this resolves it for you all as well.
Here is how to get Adobe Version 11 PDF filter to work.
1 . If you haven’t already, run the following in SQL Server:
Sp_fulltext_service ‘Load_os_resources’, 1
Go
--you might also need to run:
sp_fulltext_service ‘Verify_signature’,0 --This is used to validate trusted iFilters. 0 disables it. So use with caution.
--go
2. Stop SQL Server. (Make sure FDHost.exe stops)
3.
Uninstall the Adobe ifilter (because it defaulted to having spaces or the folder name is too long).
4.
Reinstall the Adobe iFilter and when it prompts for where to install it, change it to: C:\Program Files\Adobe\PDFiFilter
5.  Once the installation finishes, go the computer’s Environment variables. Add the following to the PATH.
C:\Program Files\Adobe\PDFiFilter\BIN
NOTE: it must include the BIN folder
NOTE: If you had the OLD location that included spaces, remove it from the path environment variable.
6. Start SQL Server
7.  IF you had an existing Full-text index on PDFs, drop the full-text index and recreate it.
8. You should now get results when you run sys.dm_fts_index_keywords('db','tblname') --Note: Change db to be the actual database name and tblname to be the actual table name.
Give this a try and see if this fixes yours.
Sincerely,
Rob Beene, MSFT

Memory problems: computer freezes on heavy memory usage

Ever since I changed the internal hard drive of my MacBook Pro (I installed a Seagate Barracuda 1Tb disk), I have the following problem:
Whenever an application needs a lot of memory (for example Parallels installing a new Windows system, or Acrobat Pro optimizing a big PDF file), the computer progressively freezes. What I mean by freezing is that I can still move the mouse cursor, but clicking has no effect, and there is no interaction whatsoever with the GUI. Even the clock on the menu bar stops.
I never had the problem before. I guess that under normal conditions the Finder will always keep a few Mb of RAM for its own use. After all I have 4Gb of RAM installed.
Is there some way I can prevent the computer from freezing? Has this something to do with VM? Ever since I changed the hard disk, this problem happens once or twice every day, and the only solution is to force a restart, losing all my work…
Thanks in advance for any advice…

First, do not assign more than half your available RAM to a VM. It's best to let the VM software's configuration to select the amount used by its defaults.
Second, watch how many concurrent applications you attempt to use. Monitor your memory usage in Activity Monitor. If the Available RAM (Inactive RAM plus Free RAM) is low and Free RAM is near zero, then you have too many concurrent applications running. This forces the system to start using the disk-based virtual memory file. With too many apps swapping into the vm file disk thrashing will occur that ultimately can lead to the computer appearing to freeze up or to actually freeze up.
Of course your alternative is to install more RAM if in fact you are over-taxing what you have now. You may find the following helpful reading:
About OS X Memory Management and Usage
Reading system memory usage in Activity Monitor
Memory Management in Mac OS X
Performance Guidelines- Memory Management in Mac OS X
A detailed look at memory usage in OS X
Understanding top output in the Terminal
The amount of available RAM for applications is the sum of Free RAM and Inactive RAM. This will change as applications are opened and closed or change from active to inactive status. The Swap figure represents an estimate of the total amount of swap space required for VM if used, but does not necessarily indicate the actual size of the existing swap file. If you are really in need of more RAM that would be indicated by how frequently the system uses VM. If you open the Terminal and run the top command at the prompt you will find information reported on Pageins () and Pageouts (). Pageouts () is the important figure. If the value in the parentheses is 0 (zero) then OS X is not making instantaneous use of VM which means you have adequate physical RAM for the system with the applications you have loaded. If the figure in parentheses is running positive and your hard drive is constantly being used (thrashing) then you need more physical RAM.

Memory problem with ITS

Hello friends,
we are having memory problem with integrated ITS.. on one application server all memory of ITS is getting exhausted. We think few users take lots of memory and it never gets released.
I checked Note 742048 - Integrated ITS, memory requirement in application server but parameters looks ok. Sometime, when i kill a user session in SM04, some part of memory was released. However i am not able to find which sessions are taking max memory as i do not see any workproess active in SM50.
in SITSPMON :
Memory Consumption: Overview
Sessions:     27      24,710,431 Bytes       915,201 Bytes/Session       2,433,8
Templates:            14,793,306 Bytes
    Sess. & Templ.    39,503,737 Bytes     Currently available to ITS: 81.92MB o
ITS Session     memory type     Peak          Memory     Total     Current
USER 001 2463     Session Memory     1,955,757     938,597     7,574     723
USER 001 2503     Session Memory     2,008,621     965,245     9,181     930
USER 001 2523     Session Memory     2,412,477     856,925     11,327     82
thanks
ashish

and what is 2463 is line : USER(user ID) 001(Client) 2463(??) Session Memory 1,955,757 938,597 7,574 723 as this is not a work process ID.]
Basically i am trying to correlate ITS session with SM04 Session of user.

High Virtual memory usage when using Pages 2.0.2

Hey there,
I was just wondering whether there had been any other reports of unusually high memory usage when using Pages 2.0.2, specifically Virtual memory. I am running iWork 06 on the Mac listed below and Pages has been running really slowly recently. I checked the Activity Monitor and Pages is using hardly any Physical memory but loads of Virtual memory (so much so that the Page outs are almost as high as the Page ins (roughly 51500 page ins / 51000 page outs).
Any known problems, solutions or comments for this problem? Thanks in advance

I don't know if this is specifically what you're seeing, but all Cocoa applications, such as Pages, have an effectively infinite Undo. If you have any document that you've been working on for a long time without closing, that could be responsible for a large amount of memory usage.
While it's good practice to save on a regular basis, if you're making large amounts of changes it's also a good idea to close and reopen your document every once in awhile, simply to clear the undo. I've heard of some people seeing sluggish behavior after working on a document for several days, which cleared up when the document was closed and reopened.
Titanium PowerBook Mac OS X (10.4.8)

Error message that no virtual memory pops up & crashes when application is run for more than 1 hour

My application uses VISA serial operations. It has arrays to store data collected from various devices. I reinitialise the arrays each time the index reaches 50.
Data acquisitions is carried out in separate threads by invoking the runVI method.
When i run the application on Win XP continuaously for more than 1 hour it gives an error message that no more virtual memory to complete the task and the system hangs up.
I open the serial port only once and close it when the application is terminated. But serial read/write operations are done continuaously
Is the error caused due to memory leakage? How can i solve the problem. It's very urgent and i shall be thankful if i ge
t the help.

Yes, it sounds like a memory leakage (either that or you're trying to run an advanced app on an old computer w/ little memory and a small hard drive).
Things to try:
1. Ensure it's only labview, and not say labview and another application interacting. This isn't a likely case, but you never know what people have on their boxes and I've seen some weird things with virus scanners. Hit Ctrl-Shift-Esc to get the task manager. Go to processes and watch the memory consumption (click Memory twice to sort in descending order) of the various processes. If labview keeps rising, you've got a leak.
2. If only a reasonable amount of memory is being used, double check your page file settings (read virtual memory).
From the Control Panel
Select System
Select
Advanced Tab
Under Performance, select the Settings button
Select Advanced Tab
Under Virtual Memory, let windows dynamically adjust the page file (and any XP speed tweakers out there can now chime in about how wrong this is. This essentially allows windows to keep upping the virtual memory as needed by various processes.
3. Find the leak. In LV Tools->Advanced->Profile VIs. Turn on memory stats. Start the profiler. Start your vi. If the vi crashes labview totally, you'll have to keep hitting snapshot to find the leaky vi (the one that's memory keeps growing).
4. Upload the vi to the forum so we can give it a looksee.
G'luck
2006 Ultimate LabVIEW G-eek.

Reg: Virtual Memory Problem in BOData Integrator XI System

Similar Messages

Maybe you are looking for