comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » Allocating memory in LINKIMAGE program
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
Re: allocating memory [message #56346 is a reply to message #20680] Thu, 18 October 2007 11:52 Go to previous messageGo to previous message
Karl Schultz is currently offline  Karl Schultz
Messages: 341
Registered: October 1999
Senior Member
R.G. Stockwell <noemail@please.com> wrote:
>
> <jtmcahill@gmail.com> wrote in message
> news:1192673434.544923.139390@i38g2000prf.googlegroups.com.. .
>> So, I have this large model file that I need to open. Although it is
>> 650MB I should be able to open it in IDL on my pc computer which has
>> ~4GB of Memory. However, it keeps telling me insufficient memory.
>> However, if I try to open it in IDL on a linux machine with ~2GB
>> memory I can open it no problem. Is there a way to make my windows
>> based pc cooperate and allow me to open this file that should be no
>> problem to open?
>>
>> Thanks,
>> Hawaiianite
>
>
> The problem may be fragmentation of your ram by the many
> dlls loaded by windows and other programs. I'd remove everything
> you can from the startup (and other automatically loading programs)
> and reboot (remove spyware, antivirus, firewalls, mail programs, but
> be careful not to forget to turn them back on). That may help.

Each Windows process gets its own 32-bit virtual address space. So,
eliminating other processes won't help the IDL process in terms of
virtual address space fragmentation, but might help overall system
performance by reducing paging demand.

What you do need to look out for is various types of "junkware" that
causes extra DLL's to get loaded either for every process on the machine
or only for processes with windows. The Windows OS does a pretty good job
of placing system DLL's in the virtual address space of each process in
order to leave a big contiguous free space in the middle. But these
non-Microsoft add-ons are sometimes notorious for plopping themselves
into the middle of this free space, which directly effects the size
of the biggest chunk you can allocate later from IDL.

One of the biggest problem programs used to be the software that you
could optionally install with nVidia and ATI video cards. Some of these
"value-add" packages would add items and do-dads to the window title bar
to let you tweak things, etc. I found that by turning these off or rebasing
the offending DLL's, I could ease the problem. I don't know if these
sorts of programs are causing these problems today, but it's worth turning
off these extra gadgets just to see if it helps.

--
Karl Schultz kws@frii.com
There are 844,739 ways to enjoy a Waffle House hamburger.
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Using IDL from a perl script
Next Topic: Lonlat2reg.pro vs. Grid program

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Sat Oct 11 16:21:30 PDT 2025

Total time taken to generate the page: 0.64386 seconds