Memory issue LabVIEW won't deallocte

Hello,
I was wondering if anyone could help. I am running LabVIEW 2012 and playing with manipulating data from a reasonably large file 40Mb using a lot of String Arrays.
Everything runs ok, the problem I am having is that everytime I run the VIs associated with the program, even when I shut them down LabVIEW is keeping them in memory, so my Ram usage is going up to about 3GB each time and I cannot get it to reduce without shutting down LabVIEW which is reallly started to prove frustrating. I have put in a few de-allocation elements but that doesn't seem to be solving it. I was just wandering if anyone know a magic command to deallocate all VIs in LabVIEWs memory without me having to shut down completely.
I know I could make the whole thing more memory efficient by not using String arrays and instead just using a single string but that is not the problem as each VI individually handles it fine and I dont have any indicators on my top level VI which would be holidng it up?
Any ideas welcome.
Thanks!

Sorry, I will have to study this later, but just glancing at it shows quite a few questionable things:
in snipped.png:
the "time taken" will most likely show always zero, because both frames execute in immediate succession, in parallel to the rest of the code. what is the purpose?
reshaping a 2D array to a 1D array could be done with the "reshape" primitive. Doing a sucessive "array to spreadsheet string" followed by "spreadsheet string to array" seems very Rube Goldberg. 
The entire code is a constant dance between different representations (1D array, 2D array, cluster, cluster array, spreadsheet string, etc.) Are you sure this could not be done a bit simpler?
In snippet 2.png:
"request deallocation" does not care about execution order, so placing it inside a sequence frame is meaningless.
LabVIEW Champion . Do more with less code and in less time .

Similar Messages

  • Help! Memory issues - programme won't open

    Hello,
    I have an issue when trying to open premier elements 3.  a message pops up stating:
    "the instruction @' 0x0a7bl0ez' referenced memory at '0x00000018'.  The memory could not be 'read'.
    I have tried to free up more memory and have at least 55gb free on the D Drive and 8 GB free on the C drive.  Can anyone offer any advice?
    Thanks

    Memory is not at all the same thing as hard drive space
    Memory is what the program uses to "think" with, hard drive space is the "suitcase" it uses to carry things with
    As Hunt (sorta) said, you have something wrong in your configuration and/or software that is starting when you turn your computer on... sorta like you are looking at a bird in flight so you can't think about your grocery list
    This is aimed at Premiere Pro, but may help
    Work through all of the steps (ideas) listed at http://ppro.wikia.com/wiki/Troubleshooting
    If your problem isn't fixed after you follow all of the steps, report back with ALL OF THE DETAILS asked for in the FINALLY section

  • 24 bit histogramming (memory issues)

    Hi All,
              I'm attempting to create a 24 bit histogram of code for a 24 bit ADC. For later processing of this data I require all the bins to be stored, i.e. I have found that the Histogram VI in the functions pallette will not work for 24 bit data, I'm on LV 2010 but on 32bit WinXP, (with ~4G of RAM)
        The histogram vi runs into memory issues with my data.
      Even at a more basic level if I try init a blank array with 2^24 elements of U32 (and so 16M elements in the array) each index of the array represents an adc code and is incremented each time it is aquired. when I initialise and begin using such an array I get "out of Memory" errors. I would have thought that 16M elements was not a huge dataset and it would not be problematic to find 16M of contiguous memory with the application's 2G allocation by the OS.
        I was wondering if anyone had a suitable explaination of this or could suggest a way around this issue.
        Thanks,
         dsone1
    Solved!
    Go to Solution.

    I would change a couple of things:
    Since the shift register is uninitialized, memory use will be low until the first time the VI is run in init mode, at which time the memory needs to be allocated at runtime. It is better to allocate at compile time as in my modification.
    I would recommend a globally initialized feedback node, eliminating the while loop. It also ensures an initialized array if the user forgets to run init first. (implementing the same with a shift register would also need the "first run?" primitive).
    I would move the init code before the histogram code, allowing to init and compute a new histogram concurrently.
    Here is a rough draft
    LabVIEW Champion . Do more with less code and in less time .
    Attachments:
    build_histogram_CA.vi ‏21 KB
    histogrammer.png ‏5 KB

  • Premiere Pro CS3-CONSTANT Memory issues when editing/rendering/exporting

    Alright, as said in the title I am currently using Adobe Premiere Pro CS3, and my issues are horrendous
    No matter what, within 10 minutes of editing, Premiere will warn and then crash because of memory issues, starting with the message:
    "Adobe Premiere Pro is running very low on system memory; please save your project and proceed with caution"
    Also, whenever I try to export this project, within 800 frames of a 7000 frame project (currently), it displays the message:
    "Error Compiling Movie", and then the previous message above if that hasn't already happened before
    And eventually, the program will crash out of nowhere, with random windows errors
    Here's my specs:
    Intel i7 920 Processor
    6 GB DDR3 RAM
    Nvidia 480 GTX
    750 watt power supply
    24" Dell Ultrasharp Monitor
    Now, I've noticed that whenever Premiere is getting close to crashing, my RAM gets up to around 4.7 GB being used, and then it crashes.
    I have already gone into Edit-Preferences and tried switching from Performance to Memory; that hasn't fixed anything
    I noticed that when I was just running my video over and over again, it stayed stable at 4 GB or so, so maybe its a rendering issue?
    I have already tried lowering my number of processes running at any given time, including my antivirus program (Kaspersky) and even explorer, but it still crashes no matter what.
    ========================================================================================== ========
    This is a SERIOUS issue for me, as even with all the normal crashes I could finish the video; but now I cannot even export my video at ALL without it crashing, and I have a plenty strong-enough computer to handle this, so what gives?
    Please help

    Ok, well this has been getting me nowhere
    I tried importing (both my CTRL-X method, and literally importing the project), and now the program won't even RENDER the footage, it just errors out at 800 frames (just like exporting)
    What is going on???
    I used to use Premiere Pro 2.0 all the time, on a separate computer, but I have 6 GB of RAM, is this really impossible???
    EDIT:
    And now, even after finally getting it to render (by saving after rendering before what crashed, and then starting it up and rendering again), all my footage looks like crap XP

  • Rendering and Low System Memory issues in PE9.

    Hello again.
    N.B: I am an ex-PE3 user.
    I am having a few issues with PE9.
    1. My main issue is that I am regularly getting the 'low system memory; please proceed with caution' message. I have googled it and read people's suggestions, but am not sure where to go from here. I have tried saving my file under another name, but am already up to '....E' (fifth) version of the file I've been working on this afternoon. The total time of the project is only approx 45 min's, although I will say that this 'low system memory' issue seems to be worst today, as I'm adding more still photos.
    2. One of the suggestions made by Steve G on one of the forums was to make sure projects are regularly rendered. When I hit 'Enter' to render, the little render window pops up for a split second and then disappears. And I would assume from the red line above my timeline that my file is not rendered.
    3. When I switch to 'Sceneline' view, my horizontal scroll-bar across the bottom will only drag SO far (to a certain point in my project; but definitely not to the end of my project. It is really frustrating. I sometimes can fix it by flicking between Sceneline and Timeline, but I have to do this multiple times... and it seems a ridiculous way to do it.
    It would be fantastic if someone could help me with these issues, please!
    System details:
    AMD processor 3.2 Ghz
    4 gig RAM (3.12 gig usable)
    Windows 7 Ultimate

    Hi everyone:
    Thankyou for all your suggestions.
    Sorry, Bill, but both those links give me an error message. I was all set to read them, but they won’t work, unfortunately.
    What is meant by ‘page file managed’, sorry? And do you mean ‘hard disk drives’ by HDD, or does it stand for something else in this context? I’m not sure what you mean by how do I have them allocated. Again, apologies for my ignorance. I do have only one HDD, but it is partitioned.
    The image sizes all seem to have a depth of 24, but vary in dimensions – I can see that some are quite large (around 3 mg in size, with dimensions of 4288x2848, for example). Is the actual mg-size relevant, or only the physical length and width?
    I have tried to look at the frame size of my project, but it seems to be greyed out. In pale digits, there is 720x576 written.
    Just before I sent this, I thought of one other thing to try first.
    I tried starting a ‘New Project’. I then inserted just 6 still photos, for experimentation purposes. I then hit ‘Enter’ and the Rendering window came up and appears to have rendered correctly. So I then tried looking at one of my other projects (that hadn’t previously been rendered) and tried to render it. In this case, as in for the project I am currently working hard on, the Rendering window flashes up for about ¼ of a second and then disappears.
    What is going on???
    From: Bill Hunt [email protected]
    Sent: Friday, 11 March 2011 2:00 AM
    To: rachel jewiss
    Subject: Rendering and Low System Memory issues in PE9.
    although I will say that this 'low system memory' issue seems to be worst today, as I'm adding more still photos.
    What are the pixel x pixel dimensions of those still images?
    What is the Frame Size of your Project?
    How is your Page File Managed, and what is the size? This http://forums.adobe.com/thread/632449?tstart=30 will give you some background and tips.
    Also, tell us about your HDD's, and how you have them allocated.
    For more discussion on Rendering, please see this http://forums.adobe.com/thread/794719?tstart=0.
    Good luck,
    Hunt

  • T400 win7 turbo memory issue

    I've been running Windows 7 for a couple of weeks now & had only a few minor problems.  One that won't go away is the turbo memory issue.  I load the 1.10.0.1012-8.9.2.1002 driver and after the mandatory reboot, device manager says it's running fine.  Then after every subsequent reboot when I check device manager I get an error code (10) telling me the service can't start.  Any ideas?  Searched around before posting, but saw no one posting the same problem.
    FYI, I'm running Win7 Ultimate 64bit, with a 2764CTO.  (and yes the system has turbo memory installed)
    Thanks

    Sorta fishing here, but try downloading the latest Win7 driver 8.9.0.1023 for the Intel Matrix Storage Manager from the link I posted above.
    This driver is mentioned in the Intel Turbo Memory Release Notes and may be required for Turbo Memory to work correctly.
    http://downloadmirror.intel.com/18011/eng/ReleaseNotes.pdf
    Here is the link to Intel's Turbo Memory download page.
    http://downloadcenter.intel.com/SearchResult.aspx?lang=eng&ProductFamily=Chipsets&ProductLine=Chipse...
    But I would think Lenovo would have included the Intel Matrix Storage Manager driver in their Turbo Memory driver download.
    http://www-307.ibm.com/pc/support/site.wss/MIGR-67820.html
    T500 ~ T9400 2.53GHz 1066MHz 6MBL2 ~ Vista 32bit Home ~ WXGA 15.4 LED ~ ATI Mobility Radeon 3650 ~ 4GB ram ~ Camera ~ 160GB 7200rpm HD ~ Intel Turbo Memory 2GB ~ CD-RW/DVD ~ Intel WiFi 5300

  • MSI K7N2G-ILSR memory issues

    I can't run the memory I want.  I had a GIG of Intel certified ram in a KT4 Ultra and it ran fine....but in my K7N2G  neither stick will run in any slot in any config, tried several other Sticks from my Local PC shop....the only memory that booted was ANY 266 memory.  So I
    ordered 2 sticks of Mushkin 512 PC3200 BLUE. Man...
    only one stick works and only in Dimm 3 (Green) the other stick won't work at all.  Tried each stick individually
    in each slot, then together.....CMOS cleared each time.
    So I feel this isn't a memory issue but a BIOS or Board issue, oh by the way this is my second board  that acted identical!!!
    Ned X(

    Sorry the D Bracket colors are:
    Green on the top and red on the bottom, manual saids " Decompressing BIOS image to RAM for fast booting "
    I forgot to mention that I'm using memory Samsung PC3200 400 MHZ and Tried Kingstone 2100 266MHZ and Generic Brand 2100 266MHZ.
    Thank you in advance for any help you good people can provide.
    Jesus

  • Application is not working due to memory issue

    Hi Friesnds,
    Kindly help me regarding settings in java. Scenario is like that. I have one server having two jboss versions (jboss-4.2.3 GA and jboss- 3.2.6). Each having java memory (JVM settings) 1 GB. The total memory of that server is 3 GB.
    Problem is that every two days my application is not working due to memory issue. Once i freed the memory (through run the commands - (1). sync
    (2). echo 3 > /proc/sys/vm/drop_caches
    Application works fine.
    I heared that the above command (echo 3 > /proc/sys/vm/drop_caches) can't run frequently because of server crash.
    Kindly help me regarding this issue and provide the resolution.
    Let me know if you need more information from my side.
    Thanks
    Ashish Shukla

    All of the above.  I tested on 4 different networks and had no luck, I also had friends test my network and the other networks with their iPhones and all had no issues using FaceTime.
    Also after I wiped my phone (erased all content and settings) I was able to successfully initiate a FaceTime call with no changes to my network and was also able to initiate another call when connected to another previously tested network that didn't work before.  Once I restored from backup though, FaceTime stopped working again.
    I did find this discussion: https://discussions.apple.com/thread/5163024?start=0&tstart=0
    and tried the suggestions found there too.  That discussion describes my issue I am having as well.

  • How to correct internal memory issue

    This is related to the standard SAP program SAPRCKM_MR11 in which there is one include RCKM_MR11F01 which contains a select statement :
    SELECT *
         INTO CORRESPONDING FIELDS OF TABLE t_bhistory
         FROM v_ckmlgrir
         WHERE bukrs EQ p_bukrs
         AND   ebeln IN r_ebeln
         AND   ebelp IN r_ebelp
         AND   lifnr IN r_lifnr
         AND   ekorg IN r_ekorg
         AND   ekgrp IN r_ekgrp
         AND   werks IN r_werks
         AND   bedat IN r_bedat
         AND   bsart IN r_bsart
         AND   bstyp IN ht_bstyp
         AND   vgabe IN ('1', '2', '3')  "Wareneingang/Rechnung/Nachbel.
         AND   loekz_k NE 'L'            "Loeschkz. Bestellkopf
         AND   loekz_p NOT IN ('L', 'S') "Loeschkz. Bestellposition
         AND ( frgrl   EQ space          "Freigabe unvollständig
         OR    frgrl   IS NULL )
         AND ( memory  EQ space          "Bestellung noch nicht komplett
         OR    memory  IS NULL )         "falls Feld nicht initialisiert
         AND ( xwoff   EQ space          "Wertbildung offen
         OR    xwoff   IS NULL )         "falls Feld nicht initialisiert
    bei Dienstleistungsbestellungen werden mehrfach kontierte
    Bestell-Pos. gegen das WE/RE-Konto gebucht, deshalb dürfen
    mehrfach kontierte Pos. nicht generell überlesen werden.
          AND   vrtkz   EQ space          "keine Mehrfachkontierung
         AND   wepos   EQ 'X'            "Wareneingang wird erwartet
         AND   repos   EQ 'X'            "Rechnung wird erwartet
         AND   weunb   EQ space          "Wareneingang unbewertet
         AND   stapo   EQ space.         "Item is not statistical
    There is one job FMT612P which contains this standard program and the job is going to abend
    because of the select statement given above which is because of some memory issue with the internal table t_bhistory, please give us a suggestion how we can avoid the same.

    Hi,
    I am also facing the same issue. We had copied this report into a custom report and are trying to improve performance by breaking the view into separate queries on EKKO, EKPO and EKBE.
    Can someone advise the best way to deal with this view v_ckmlgrir or a best approach to break down the view into separate queries.
    Thanks
    Edited by: Shreyas Shrikant Kulkarni on Jun 29, 2009 4:56 PM

  • Memory issue with Podcast !!!

    Hi,
    I have several issues with the Podcast App.
    - i cannot sync podcast that i have downloaded on my laptop using itunes to the iphone,
    - when i download some podcast directly on the iphone, i cannot play them, i still have to stream them,
    - i have uge memory issues and i think that the downloaded version of the podcast might be somewhere on the iphone, but cannot access / delete them (over 16 GO, i have more than 4.5 GO used for 'other', that are not related to anything...)
    i have tried to delete / reinstall the app, but this does not change anything...
    Any help ?
    Rgds

    Quote
    I have a MSI 975X Platinum rev 2 mb with a e6300 processor overclocked to 2.24ghz.
    If your CPU operates @2.24 GHz, it means that you increased FSB frequency to about 348 MHz.
    To make sure there is no misunderstanding here, let me point out the following:
    Memory frequency is ALWAYS linked to FSB frequency by the FSB/DRAM Ratio you can select in BIOS.  If you select 1:1 for example, the BIOS will show that memory frequency is 533 MHz. This value however, only applies to the default FSB clock speed of 266 MHz:
    266 MHz x 1 = 266 MHz (or 533 MHz effective DDR2-frequency).
    If your system is overclocked, what counts is only FSB/DRAM ratio, not the memory speed displayed in BIOS.  That means, if you set FSB/DRAM ration to 1:1 and FSB frequency to 348 MHz, your RAM will operate @:
    348 MHz x 1 = 348 MHz (or 696 MHz effective DDR2-frequency).
    The main question is:
    What are you talking about when you say, you can't make your RAM operate @800 MHz?
    The BIOS does not offer a proper divider to get your RAM to 800 MHz @348 FSB clock speed to begin with.
    You have the following choices if your overclock your system:
    FSB=300 + FSB/DRAM ratio = 1.33
    300 MHz x 1.33 ~ 400 MHz (or 800 MHz effective DDR2-frequency)
    FSB=320 MHz + FSB/DRAM ratio = 1:1.25
    320 MHz x 1.25 = 400 MHz (or 800 MHz effective DDR2-frequency)
    FSB=400 MHz + FSB/DRAM ratio = 1:1
    400 MHz x 1 = 400 MHz (or 800 MHz effective DDR2-frequency)
    Use CPU-Z to monitor the DRAM frequency that is actually set if you are overclocking.

  • HT1423 the memory-access door won't come off, HELP!

    Hi,
    I have a mid-2007 iMac with 1 GB of ram and i'm trying to replace it, but the memory-access door won't come off. i loosen the screw with a screw driver but it won't open and i don't know why. i want to upgrade to 4 GB.
    is there some trick to opening it thats not stated in this article? please help me, i don't know what to do :-( i really need to get lion on this thing and can't do that without a RAM update.

    Some times there's a bit of prying in order with a thin blade.
    http://eshop.macsales.com/installvideos/imac_mid_2007_mem/

  • Memory issues

    I have a 2008 Macpro...remarkable up-to -date for its age...I plan to use it for some time yet. Lately I have been a having what seems to be a memory issue. There are 12 gig of Ram installed...6x2 gig each in pairs. Sometimes on boot the screen only shows a flashing folder. I shut down and reboot, and it seems fine...but only 8gig of ram shows installed. I opened it up, unseated the boards that hod the ram, and unseated and reset all he ram, and replaced the boards. Great, all he ram shows, 12 gig again. This morning, a few days later, it did it again, showing 8. So, when I run Crucial's memory analyzer, it shows first four slots full, last four empty. A few questions...are the first four slots the top board, the last four the bottom board? This, BTW, is what it was also showing before I reseated the ram. If so, the ram in question s on a separate board. Opinions, is the ram bad, or the board, or neither? Should I reseat again and flush with contact/tuner cleaner/degreaser? Could this hurt? (it is made to clean electronics) the machine does seem ever so slightly unstable. FCP crashed once in a 5 hour edit, which it has done before but rarely. The machine itself did not crash, just the program. Can using the machine like this do more damage, or will it just not boot? I feel it is a seating or connection issue, as I have never seen ram come and go, once it is fried it's fried. The ram is still pretty pricy, but I was going to buy 4 more gigs just to fill it out. Are the two board that hold the ram identical, top and bottom? If so, is a good diagnostic tool to swap them and see what happens? Move all the ram and swap board positions, or do I risk blowing ram ? Remember, the ram did show up when I reseated, so it seems like it is I damaged. My goal would be to see if top ram stops appearing. Does ram need to be filled in order? I know in pairs, but can I just swap the boards and leave the ram, which should look like filling slots 1,2,5,6,7,8...as opposed to 1,2,3,4,5,6.  Can the boards be swapped, or are they set somehow to be 1-4 and 5-8, or is that determined automatically by their upper or lower insertion? Any other advice is appreciated. Funds are low, so I need to keep this machine running. Other info, 3.06ghz (2 quad core) Xeon CPUs, 1tb system drive, 4 TB raid5' OSX 10.6.8 dual graphics display with 512MB (can't remember card model right now). Also, can I update graphic card in this machine? I looked at it a few years ago, but the I for I found was confusing and I never got to it. I figure I might be able to get a better card pretty cheap by now. Thanks all.

    You have typed a huge list of ideas all as one paragraph with many questions in it without a single bit of white space. My eyes are not good enough to read a question, attempt to answer it, then dig through the sea of letters to find the next question.
    Your writing needs white space, which gives it a peculiar overall shape, and allows a reader with poor eyesight to return to a particular spot in the text. So I will attempt to answer some parts of your query, but will be forced to do so from memory of what you wrote.
    The Mac Pro uses Error Correcting Code (ECC) RAM. Eight extra bits are stored with each word, and checked when read back. Single-bit errors are detected, and the check bits are used to make a correction on the fly. More complicated errors are detected, and can cause your Mac to halt on a kernel panic to prevent bad data from propagating.
    ECC RAM means your Mac can detect bad memory easily at Startup, and can declare pairs of DIMMs "absent" to avoid using them.
    Contact corrosion, which was an issue with much older DIMMs, is rarely an issue with these FBDIMMs. Once re-Inserted ONCE, corrosion will not recur for a year or more.
    The upper and lower Riser-cards are identical.
    The FBDIMMs in these machines are subject to overheating and death. If Mac OS X or any program reports DIMMs as missing, at least one of the DIMMs in that pair has died (but since they are installed in pairs, both are marked absent).

  • Lenovo G560 - Issue with won't boot and black screen after HDD upgrade

    Lenovo G560 - Issue with won't boot and black screen after HDD upgrade.
     What happen: My laptop was working fine, no blue screen issue, no funny business at all. I bought a new SSD Intel 120 GB and thought it would be a good idea to replace the HDD. I shutdown and disconnected the power adapter, waited a couple of minutes and removed the battery. I opened up the back case and replaced the HDD. And put all the screws back and put the battery back in.
    Problem: The very first time I turned the power on, nothing happens besides a black screen. I pressed the dvd drive it works and opens up and closes. I waited for about 30 mins and still has blac screen. When I mean black screen, no bios menu, no logo, just a black screen with the fan sound on.
    I have tried these:
    1. Unplugged everything - battery, adapter, and pressed the power on button for about 60 seconds, nothing, the laptop turns on with the LED display on for both on and battery LED's. But nothing but black screen, no sound of windows loading just the fan and black screen.
    2. I tried putting back my old 2.5" and nothing but black screen.
    Thoughts and suggestions?
    Solved!
    Go to Solution.

    Hi Autoexit173,
    Welcome to Lenovo Community!
     As per the query we understood that you are facing issue with system not booting in your Lenovo G560 laptop.
    As you have mentioned that the system not booting, please try to remove the RAM and  turn on the system and check if you can hear any beep sound. Also try to clean the RAM slots and check for the issue.
    Click here for the steps to remove the RAM and refer page number 40.
    Hope this helps. Do post back if issue persists!
    Best regards,       
    Ashwin.S
    Did someone help you today? Press the star on the left to thank them with a Kudo!
    If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.
    Follow @LenovoForums on Twitter!

  • Question for those with memory issues on k8n neo plat

    I have been having issues with my memory on the k8n neo platinum board since i built the system last month and i just recently discovered a fact I had overlooked.
    I Have discovered that  if i test the system while it is cool (having sat turned off overnight for example), then memtest will pass the ram just fine and the system will be stable for a short period of time, generally longer if no intensive applications are used, ie. doom3 vs. websurfing).
    This system, once it heats up ( seems mostly to be the nvidia 3 nb that needs to be "hot"- that is, a probe placed in contact with the module reaches about 58+ degrees c) then the system becomes unstable and memtest, if used, fails.
    Prime95, if used on it when its cool, will usually take about an hour or so to fail, but if its used on the system when its been running a bit ( temps from nb at 58c+ and memory module hot to the touch) then it fails after about 20-30 seconds.
    I have placed an active hs on the nb in an attempt to correct this, but temps still remain high with failures occuring.
    I have spent the better part of three days testing the sytem this way and the above facts have held true in all these tests.
    I have  tested at stock ratings ( not using "auto" in bios, but using "approved ratings" of 10 x 200 for fsb and timings of 2-3-3-7 for my ram at 1:1 (which is recommended as well) since i am testing for base stability at this point;Voltages have been left at auto settings, however.
    I was wondering if anyone else with memory issues could try this out and post if this seems to be the case for you as well.
    Perhaps the memory issues on these boards are directly related to a problem with the nvidia 3 chipset running too hot?
    Does anyone have a memory issue with these boards who is using water cooling on the NB ?
     Lack of issues from people using 'problem" memory, but having no failures with water cooled nb's would support my assumption.

    Yes i did mean chipset.  
    I am using a stock hs/fan from amd, which seems to run a tad hot but, considering that I wont overclock until I can get board stable, its not an issue. (runs 35-40 idle and up to 72 intensive). I need the warranty more then the extra mhz at present.
    I removed the stock heatsink from the nvidia chipset and bought a generic chipset cooler (green, very little in the way of fins and seems to be aluminum) with a small fan.
     I used a generic silver paste from Compusa to adhere both the cpu hs and the chipset.
    I didnt lap either hs, just installed each as per instructions on artic silvers website (figured it had to go on the same way even generic).
    I also bought a kingwin thermal center which i ran probes from to the cpu, case, and nb chipset.
     I am not using it to adjust fans so those arent connected - its just a reference temp I can see at a glance, esp considering the funky bios reading this boards been known to give.
    I assume from these responces that even a nvidia 3 250 chipset shouldnt get as hot as mine?
    I asked about that from the retailer i bought this from but he seemed to think it was "ok" at 50ish celcius, but then again he didnt look too confident when he said it, lol.
    Idle right now reads on Corecenter at 28 celcius for cpu and 33 celcius for the chipset, although, I have readings of 37 c and 43 c from the kingwin thermal center, which i believe to be more accurate.
    My voltage reads at 11.67 for the 12v line at idle right now.
    The psu i got is stick from the xblade case i bought in store. (http://www.xoxide.com/xblade2.html)
    I have a dvd burner, cd drive, and two maxtor ide hd's attached to the system;The only card is the agp.
    Is there a way to check and see if the cpu ispower starved? software monitor or even an external probe perhaps?
    I havent put a probe on it, but the ram came in its own heatspreader, which gets very hot to the touch as well.
    What temps should I be looking for on these items?

  • Firefox 3.6.8 and memory issues

    After the last update to 3.6.6, I disabled plugin-container per the instructions given on the forum, and my RAM problems went away. However, after the automatic update to 3.6.8, the memory problems came back, with memory usage going up to 92%. I downgraded to 3.6.4, and turned plugin-container off again; while memory usage is currently at 84%, it is not as low as it was before the upgrade to 3.6.8. (79-80%) (There is very little difference in the websites being opened on the various tabs.)
    == This happened ==
    Every time Firefox opened
    == I upgraded to 3.6.8

    ffs guys. It's a free browser. It's cool. We love it. But can we do something about memory issues? Almost every release has huge memory leaks.
    How about halving the release points and focus on memory issues for the other half of the time. I am a long time user since way back in the day and it seems to me that instead of trying to release so many versions, we should be focused more fixing the current release.
    I say put a moratorium on new features until bloat can be fixed. These experiences are starting to give me a hardon for IE again.
    Screw new features. I can deal with plain old tabs like they are. I don't need more bells and whistles. This browser has been kicking ass and taking names for a loonnnggggg time. We don't need more bloat. Keep the security fixes coming but everything else can wait. Take a breath. Stop and smell the roses for a few weeks.

Maybe you are looking for