5508 upgrade to 7.6.100 memory leak

We have a single 5508 running 7.6.100 with just over 300 Ap's. I've noticed since our upgrade, we're having some problems. The bigest, is a reboot. When the system comes up, the memory is sitting at about 56%. It creeps up to about 86% and then reboots on its own. Don't really like that. Anyone seen this or got a resolution to this?

Maybe you can try the newer firmware, 7.6.110.X?

Similar Messages

WLC 5508 upgradation from 7.4.100.0 to 7.4.110.0

Hi All,
We have upgraded the wlc from 7.4.100.0 to 7.4.110.0. where we found after reboot the configuration has failed to load with the below errors.
Cryptographic library self-test....passed!
XML config selected
XML root tag XML_mapping_variables not found
XML root tag XML_mapping_variables not found
XML root tag XML_mapping_variables not found
XML root tag XML_mapping_variables not found
XML root tag XML_mapping_variables not found
Parse error at line 6:
not well-formed (invalid token)
Validating XML configuration
Read HA Config before validation
octeon_device_init: found 1 DPs
readCPUConfigData: cardid 0x6070001
Parse error at line 3:
unclosed token
XML root tag XML_config_variables not found
XML root tag XML_config_variables not found
XML root tag XML_config_variables not found
XML root tag XML_config_variables not found
Parse error at line 5:
unclosed token
We have reloaded the configuration on the controller. What might be cause for this.??
Regards,
Channa

Did you try to factory default the WLC and rebuild it from scratch? You shouldn't have any issues when upgrading, but when you upgrade and the configuration gets corrupt, there is noting you can do, except to rebuild the WLC. If this is part of an HA AP SSO setup, then you need to make sure you reset the peer and then the primary. Question is.... are you running HA AP SSO and if not, is the WLC working fine after a reboot?
Scott

Huge memory leaks after upgrading from kernel 2.6.38(?)

My system began leaking memory some months ago and I've little to no idea what is causing it. The closest hint I can give is that I think these problems started around upgrading from Linux 2.6.38 to 2.6.39 and have continued with 3.0 aswell. Sometimes my whole system freezes due to extensive swapping (HDD usage led stays lit), sometimes it stops after consuming almost all of my 4 GB RAM.
I think the leak has to come from inside the kernel because all sysmon apps claim no application is eating too much RAM yet the system memory consumption is at 100 % or even using swap. Even after I kill Xorg the memory usage will stay at least at 2.0 GB, when it should be less than half a gig.
I'd like to guess the blame is on Nouveau, because it was giving me a hell of a time back with Linux 2.6.39. It had a habit of freezing my system when re-enabling suspended compositing (both with Kwin and Mutter). Also video playback was corrupted sometimes. These probs have since been fixed with Linux 3.0.
I cannot name any spesific app that might trigger this memory leaking. I don't play any games and mainly use Firefox, Chromium and VLC day in, day out.
There seems to be absolutely no way of reclaiming the reserved memory than rebooting the whole system. I have even tried unloading Nouveau.
I am currently running the [testing] repo with ~daily upgrades.
Last edited by Verge (2011-08-16 14:04:09)

OK, this kind of surprised me. No wonder I couldn't find any relevant stuff while googling for kernel issues. I have had Strigi disabled for some time now because it is miserably broken, but I now disabled the whole Nepomuk too. Let's see if my problem now goes away or what...
The release of KDE 4.7 Beta 1 actually lines up with the launch of Linux 2.6.39 so this really might be the case. I moved to KDE 4.7 already with the first beta.
Last edited by Verge (2011-08-16 14:30:37)

Memory Leak in Report after upgrading from Crystal Reports 10.5 to 13.0.1/2

I'm currently having an issue with crystal reports 13 (Visual Studio 2010), We have recently updated our CRM Solution to use the newer crystal reports runtime as we are now using Visual Studio 2010,
We have a client who has a report which contains a sub report which basically contains a Image pulled from a MSSQL Database as a BLOB Image Field which is basically scanned images relating to the report, Previously the report worked fine before the Client Updated our CRM Solution to the latest version, Now for each individual page which has the scanned image the application is swallowing 100 MB of ram, as there are around 32 of these scanned images and our solution is a 32 bit application we are getting out of memory errors due to the whole 2GB addressable to a 32 bit process limitation,
The images are around 4MP and stored in JPG format in the database so should not be consuming over 100mb of ram per image displayed by the report even if they are being stored uncompressed in RGBA Format,
Likewise when viewing the pages of the report manually after a specific page (when the amount of memory addressable by a 32 bit application gets hit) the images just don't display and then any pages with the image are not being displayed and not giving an error / exception.
I have tried re-saving the .rpt files to cause them to be in the newer crystal reports format and this is still happening, likewise I have tried un-installing the 13.0.1 and installing the 13.0.2 runtime.
I am just about to check SQL which pulls the image for the sub report, although I am sure for each sub report it should only be pulling one row with one jpeg image in case the sub report is holding quite a few images but only displaying the first.
Likewise If all else fails I will try re-creating the report as I have experienced issues with some other specific reports doing strange things after being updated from the 2008 runtime which I really am not liking the idea of due to how fiddly crystal reports can be, It is good and does the job but takes far longer than some other solutions to get what you are trying to achieve done.
This report had been working fine for 2+ years before the client updated to the most recent version of our CRM Software.
Has anyone else experienced simular issues with the latest runtime.

I have just been reviewing the code for this and it appears that the sub report is pulling all of the images,
It is strange that previously this was working fine seems like the newer runtime does not dispose of the data once it has been displayed on a sub report which would explain memory leak as it will call the select again pulling approx 60 images which are probably approx 8 - 900KB plus sub report + uncompressed image to display and then filtering.
I am about to modify this report and will post if fix i put in place resolves the issue.

Memory leak since upgrade to 1.6?

Hi,
We have a server which has been running nicely for about 9 months on HTMLDB 1.5. However since we upgraded to 1.6 we are getting regular errors as follows:
ORA-04031: unable to allocate 131092 bytes of shared memory ("large pool","unknown object","session heap","kgich").
restarting the database fixes the problem for a while but after a day or 2 it happens again.
There have been no other changes except the upgrade to 1.6, could there be something causing a memory leak in the new version?
Our server is running Linux with 1GB memory and is dedicated to the HTMLDB instance.
Steve

Steve,
Instead of bouncing your database, have you thought of increasing your large_pool_size initialization parameter?
This would not be a memory leak. If anything, it would be a function of more memory required per page view than before. Just out of curiousity, is this dedicate server mode or MTS?
Joel

Plugin-container.exe takes over and uses 100% of my CPU locking me out and leaving my PC non-functioning. Is this a bug, or a memory leak, in the Firefox software? Can anything be done to fix this problem?

In looking at Windows Task Manager I found that plugin-container.exe was taking over 100% of my CPU and my system was frozen. Is this a memory leak or other bug?

Thank you! I have been having problems with Adobe Flash since downloading the new 11.1 version. I will download it again and reinstall it, hopefully that will correct the problem.

OBVIOUS MEMORY LEAK iTunes about:10.6.3.25 (upgraded from 32 to 64) but iTunes*32 process is in memory. clicking on a song to play or right clicking it adds 5MB. Did 32 have this problem and didn't uninstall correctly or is 64 broken too.

OBVIOUS MEMORY LEAK
iTunes about:10.6.3.25
windows 64 bit Home on AMD64 HP G60 laptop
downloaded and installed "iTunes32Setup.exe"
saw the problem and uninstalled it
downloaded and installed "iTunes64Setup.exe"
iTunes about:10.6.3.25
now i see process "iTunes.exe*32
it is ok when it play song list
but ***** UP MEMORY when i click on another song to play. apparently it doesn't release previous player thread
OR,
if you right click on a song, the memory will blow up antother 6MB and won't release it...can do it all day long
-- until run out of memory and iTunes freezes...without any of my changes.
sooooo.. is it the uninstaller or is iTunes64Setup.exe mispackaged or do both have memory problems on AMD 64 ?

Unfortunately I was able to repeat the memory leak even with turning the Toolbar off. To replicate the problem, I was able to watch the memory leak each time I actively selected a new song with the iTunes open. I was able to repeat the leak with and without both Spotify and TuneUp Companion running and not running. The only thing I noticed is when both Spotify and iTunes were open, the memory leak from iTunes added insult to injure with Spotify which kept trying to sync up with iTunes local library which would crash Spotify as well. But I can confirm the memory leak is in iTunes 10.6.3.25 (looking forward to 10.6.4 fixing the problem).

DataSocket memory leak problem (2VO0SF00) -- more info?

When upgrading to LabVIEW 8.5 recently, I noticed the following known issue in the readme file:
"ID: 2VO0SF00
DataSocket/OPC Leaks Memory using ActiveX VIs to perform open-write-close repeatedly
If you call the DataSocket Open, DataSocket Write, and DataSocket Close functions in succession repeatedly, LabVIEW leaks memory. Workaround — To correct this problem, call the DataSocket Open function once, use the DataSocket Write function to write multiple times, and then use the DataSocket Close function."
Looking back, I think this problem may have been present in previous LabVIEW releases as well, and might be giving rise to a problem that's been dogging me for quite some time (see my thread, "Error 66 with DataSockets", http://forums.ni.com/ni/board/message?board.id=170&thread.id=187206), in addition to general slow/glitchy behaviour when my VI's have been running continuously for a long time. But in order to determine whether or not this issue affects me, and how I should go about fixing it in the context of my own programs, I need a bit more information about the nature of the issue itself and the inner workings of the DataSocket VI's. Any help or insight the community can provide into this would be greatly appreciated!
Here are my questions:
It is my understanding from the "known issue" description above that the memory leak happens when you have a DS Open wired to a DS Write wired to a DS Close, all inside a loop (example 1), and that the suggested workaround would be to move the DS Open and DS Close functions out of the loop on opposite sides, wired to the DS Write which remains inside the loop (example 2). Is this correct?
Does this leak also happen when performing DS open-read-close's repeatedly (example 3)?
What happens when a DS Write (or DS Read) is called without a corresponding DS Open and DS Close (examples 4a and 4b)? Does it implicitly do a DS open before doing the write operation and a DS close afterwards? What I'm getting at is this: would having an isolated DS Write (or DS Read) inside a loop, not connected to any DS Open or DS Close functions at all, cause this same memory leak?
If one computer is running the DS server and a second computer is running the VI with the repeated open-write-close's, on which computer does the memory leak occur?
In my question #1 workaround (example 2), the DS Open and DS Close outside the loop are routed through a shift register and in to and out of the DS Write inside the loop. If the DS connection id goes into the DS Write "connection in" and then splits and goes around the DS Write and out to the DS Close, without coming out of the DS Write "connection out" (example 5), will the memory leak still be avoided? I.e. if the DS Write function doesn't have anything connected to its "connection out", will it try to do an implicit DS Close?
If the VI causing the memory leak is stopped, but LabVIEW stays running, will the leaked memory be reclaimed? What if the VI is closed? What if all of LabVIEW is closed?
FYI, in the examples above "x1a" is a statically-defined DataSocket on the DS server running on the computer Max, to which the computer running the example VI's has read/write access. My actual application has numerous VI's and hundreds of DataSocket items, many of which are written to / read from every 50-100 ms in the style of examples 4a and 4b.
Does anyone have any idea about this stuff?
Thanks in advance,
Patrick
Attachments:
examples_jpg1.zip ‏63 KB
examples_vi1.zip ‏40 KB

Hi Meghan,
Yes, some of the larger VIs in my application do write to / read from several hundred DataSockets, so it's not feasible to use shift registers for each one individually, and hence why I'm passing the references into an array, etc.
Your Alternate Solution 2 is more along the lines of something that would work for me. However, my actual code has a lot of nested loops, sequences and DataSocket items which are not all written to in the same frame, so this solution would still be difficult to implement: it would be cumbersome to unpack the entire 500-element reference id array and build a new one (maintaining the positions and values of the unaffected elements) every time I write to some small subset of the DataSockets.
I think I have a solution which solves the problem and is also scalable to the size of my application -- I've attached it as Example 7. Do you think this will avoid the memory leak? It's the same as your Alternate Solution 2, except that instead of building a new array out of the DS Write reference outs, each reference out replaces the appropriate element of the original array.
If I understand you correctly, in order to avoid implicit reference opens and closes, a DS Write needs to have both it's reference in and reference out wired to something. Thus, even though my Example 7 replaces an element of the array with an identical value, and therefore doesn't actually change the array (which would be a silly thing to do normally), the DS Writes have their reference outs wired to something, and eventually in a convoluted way to a DS Close, so it should avoid the memory leak.
Just out of curiosity (I don't think anything like this would apply to my application or any fixes I implement), when would the implicit reference close happen in the attached Example 8? The DS Write has its reference in and reference out both connected to temporally "adjacent" DS Writes via the shift register, so perhaps it wouldn't try to close the reference on each loop iteration? Or would it look into the future and see that there is no DS Close and decide to implicitly do that itself? Or maybe only the DS Write on the last loop iteration does this?
Thanks for bearing with me through this,
Patrick
Attachments:
example73.JPG ‏40 KB
example83.JPG ‏14 KB

HTTPService + XML Load + Memory Leak

Hi all....
I have noticed a memory leak in my application. This leak was
not apparent when the application was completed some months back
which is what left me a little confused as all I have done since
was upgrade to Flex 3 and possibly updated / changed my Flash
player.
I think I have found the cause to this problem (below) but am
not 100% sure that it is the "actual" problem or any reasons to
back my thoughts up, so have listed what I have checked / tried
along the way (maybe I have missed something)....
My Discovery Process:
I started profiling my application but did not find anything
out of the ordinary. I did a code walk-through double checking I
had cleaned up after myself, removing and even nulling all items
etc but still to now success - the leak is still there.
I have profiled the app in the profiler for reasonably long
periods of time.
All the classes etc being used within the app are consistent
in size and instance amount and there is no sign of any apparent
leak.
I am using a HTTPService that is loading XML data which I am
refreshing every 5 seconds. On this 5 second data refresh some
class instances are incremented but are restored to the expected
amount after a GC has occurred. The GC seems to take longer, the
longer the app is running, therefore more and more instances are
being added to the app, but when the GC eventually runs it "seems"
to clear these instances to the expected amount.
After scratching my head for a while I decided to make a copy
of my application, rip everything out, and focus in my data load,
where I found a problem!
I have now just a HTTPService that loads an XML file every 5
seconds, and this is all I currently have in the app (as I ripped
the rest of the code out), e.g:
Code:
<mx:Application xmlns:mx="
http://www.adobe.com/2006/mxml"
....... creationComplete="initApp()" >
<mx:HTTPService
id="httpServiceResults"
url="
http://myIP:myPort/myRoot/myXML.cfm"
resultFormat="e4x"
result="httpResultHandler(event)" />
<script....... >
private var timerPulse:Timer;
private function initApp():void
httpServiceResults.send();
timerPulse = new Timer(5000, 0);
private function httpResultHandler(event:ResultEvent):void
timerPulse.start();
timerPulse.addEventListener(TimerEvent.TIMER, timerRefresh);
public function timerRefresh(eventObj:TimerEvent):void
timerPulse.stop();
timerPulse.removeEventListener(TimerEvent.TIMER,
timerRefresh);
timerPulse.reset();
httpServiceResults.send();
</script>
</mx:Application>
This is pretty much the code I am currently using and it
leaks.
I ran and monitored this in both the profiler and the
activity / task manager, and after running the app for 1800 seconds
(30 min) in the profiler, the memory size grew from 50mg to 165mg
just sending the HTTPService.
I tried loading the service in multiple ways including in AS
rather than MXML creating new instances of it each time, resetting
it, nulling it etc... but nothing prevented this memory increase.
I then tried to load the XML using different methods such as
using the URLRequest and URLLoader which again caused a memory
leak.
What still confuses me is that this leak did not exist in the
previous version and not a great deal has changed since then apart
from upgrading to Flex 3 and possibly upgrading my Flash payer
(which I believe is a possible cause)
After looking into this issue a bit more deeply, I read a few
blogs / forums and other people are experiencing the same problems
- even with a lot bigger leaks in some cases all when reloading
large sets of XML data into Flex - however, I as of yet found no
solution to this leak - people with a similar problem believe it is
not due to a memory leak more a GC error, and others pointing
towards the Flash Player itself that is leaking - I don't really
know.
Findings so far during investigation of this issue:
* App leaks for both HTTPService and ULRRequest / URLLoader
methods
* App only leaks when calling a data loader
* The size of the leak seems to depend on the size of the
XML being loaded
* The size of the leak also seems to be affected by the
applications heaviness - the greater seems to enhance the leak
An interesting factor I have noticed is that if I copy the
XML from my "myXML.cfm" that I link to in my HTTPService and copy
the contents of the file into my own XML file stored within the
Flex project root itself: ""myXML.xml"" the leak disappears... like
it seems to link when loading the XML over a network, however as my
network knowledge is not great I am not sure what to make of this -
any ideas???
Could the connection to the XML document cause leaks??? is
there anything else that could cause this leak??? have I something
in my code sample that could cause this leak??? or could any of the
other things I have mentioed cause this leak???
Any help / ideas would be greatly appreciated.
Thanks,
Jon.

I also observed heavy memory leak from using httpservice with
XML data. I am using Flex3 builder under Linux. My Flex application
polls httpservice every 10 seconds. The reply is a short XML
message less than 100 bytes. This simple polling will consume 30+
MB of memory every hour. I leave it idling for several hours and it
took 200 MB of memory. No sign of garbage collection at all.

Memory Leaks in TS3.0 OI's

Using TestStand 3.0, LV 7.1(witht 7.1.1 Update), Win2K, 3GHz P4, 512Mb.
Have written a custom OI, (Sort of based on the Simple OI that ships with TS3.0, but heavily tweeked).
Now I've had problems with memory leaks...... I've read the other posts on this issue and they don't seem to answer these problems.
Now going back a step, To confirm I'm not doing something stupid, I ran the OI's that ship pre-built with TS, with the "Benchmark.seq" sequence about 10-15 times(Tracing ON, Reports ON, Test UUT Entry Point). This seems to show that each run "leaks" about 92Kb each run. Now that doesn't seem much but test 1000units a day, and that will eat up around 100Mb of RAM, and that ridiculous! Its not the report in this case as thats only a few lines of text
With the OI that I've built up, leaks about 112Kb of RAM on the same Sequence. I'm not using the standard controls (eg Execution View) to display the progress, but using the Trace message to get what test last executed and putting the value in a table, I'm sure I've close off the references and acknowledged the UI messages recieved from TS when I've finished using them(using mainly the Close Reference.vi on all refs/SequenceContexts/Property Objects....ect, and acknowledging the UI Message when finished with it)
When running a "Real" test sequence on a test rig the situation is many times worse(can be 100's Kb per run depending it seems on the size of results file), I assume as the results are stored somewhere in TS between UUT runs.
Questions:
Why is there what seems like memory when leak running TS(even with the prebuilt OI's)?
How to minimise this leaks?
Which refs need particular attention, and whats the right method of closing them properly?
How to purge the TS runtime engine of the stored results between each run in "Test UUT's", and get it to free up the memory? (I assume this is why the memory it rising alot while testing with a sequence running real tests).
Does this happen with TS3.1?
Any help much appriciated, as this problem is really slowing things down here.

Hi
If you are sure that you are leaking when you generate html/XML reports, then you should consider upgrading to 3.1.
The changes to work around a leak in IE is very extensive and is not available for TestStand 3.0
Below is the text from TestStand 3.1 readme which gives you more details.
"In TestStand, the sequence editor report tab and the Custom UI Report control use the Microsoft Internet Explorer ActiveX control to display html and XML reports. Each time the Internet Explorer control updates the report, the Internet Explorer control does not always release its internally allocated memory. If the control is updated continuously over an extended period of time, the TestStand process memory use increases. TestStand 3.0 used the control in a way such that the failure to release memory occurs more often. TestStand 3.1 contains workarounds that limit the amount of memory the control fails to release. Note that when using on-the-fly reports, the Internet Explorer control is only used when the control is visible. "
You can also consider using txt reports, which will also confirm that it is related to html/XML reports and not anything else.
I hope helps.
Regards
Anand Jain
National Instruments.

Why do I get Memory Leaks in case 1, but not in case 2?

I recently investigated into memory leaks, since we got some when a Window is opened/closed several times.
I discovered the following behavior with ListView:
If I make several instances of a Window, which contains a ListView which uses a fix list as items, there are leaks. (Case 1)
If I make several instances of the ListView directly there are no leaks. (Case 2).
For me both cases seems equal, there's just another wrapper (the window) around the ListView in case 1.
Can someone explain what's going on?
import javafx.application.Application;
import javafx.collections.FXCollections;
import javafx.collections.ObservableList;
import javafx.scene.Scene;
import javafx.scene.control.ListView;
import javafx.scene.layout.VBox;
import javafx.stage.Stage;
public class TestApp3 extends Application {
    public static void main(String[] args) throws Exception {
        launch(args);
    ObservableList<String> items = FXCollections.observableArrayList("Item1", "Item2");
    public void start(final Stage stage) throws Exception {
        VBox root = new VBox();
        for (int i = 0; i < 100; i++) {
            SubStage subStage = new SubStage(); // Case 1
            subStage.show();
            subStage.hide();
//            ListView<String> listView = new ListView<String>(); // Case 2
//            listView.setItems(items);
        System.gc();
        System.out.println((Runtime.getRuntime().totalMemory() - Runtime.getRuntime().freeMemory()) / 1024 + " KB");
        Scene scene = new Scene(root);
        stage.setScene(scene);
        stage.show();
    private class SubStage extends Stage {
        public SubStage() {
            ListView<String> listView = new ListView<String>();
            listView.setItems(items);
            Scene scene = new Scene(listView);
            setScene(scene);
}EDIT: If I use a TableView in the Substage, there are NO leaks. So is this an issue of the ListView?
Edited by: csh on 10.09.2012 07:40

There is file activity if Open Config Data.vi is being called. The error is just due to not being able to find the configuration/.ini file. Root cause could be a few things: the INI file was deleted/not moved/invalid path/whatever. And the "create file if necessary" input to your use of Open Config Data.vi must be set to False for whatever reason.
Side note:
There were a couple changes to the Config VI's between v6 and v7.
If you were relying on using the default FALSE in Close Config Data.vi in LV6.1, you have to change your code.
From LV7 Upgrade Notes:
<snip>
• The configuration file path input of the Open Config Data VI is a required input. You must specify the configuration file path even if you open a reference to a configuration data object.
• The default of the write configuration file? input of the Close Config Data VI is TRUE. In LabVIEW 6.1 and earlier, the default is FALSE.
<snip>
=====================================================
Fading out. " ... J. Arthur Rank on gong."
Attachments:
OpenConfigData_v7Help.jpg ‏19 KB

Firefox 17 huge memory leak

Since the last update today, Firefox seems to got a huge memory leak. After one hour idle on some pages it was up to 750MB memory usage, and constant 100% load of one CPU core.
Looks like something is not going well with the garbage collection, if I visit http://www.robertsspaceindustries.com/forums/forum/forum-category-2/ for example.
Had to disable the graphic hardware acceleration, because of the newly introduced "clear type" font bug.
Edit: May also be related to mail.google.com, which I have running in an app tab.

For what it's worth, I had exactly the same problem (except that it's on Linux) since the upgrade to 17.0. When I disabled greasemonkey, the problem instantly disappeared, so it looks like the compatibility with greasemonkey got broken.
Likewise, I'm very disappointed with the frequent bugs/annoyances that come with the rolling upgrade system; I find myself more and more using Chromium because of it. Mozilla really needs to give people the option to run a stable branch that receives security updates only.

T61 with memory leak on XP for driver battc.sys

Hi
I have an issue with XP where the battc.sys module that is part of Windows XP and responsible for the kernel side of monitoring the battery status. This module continually leaks memory until I have no more kernel paged resources left and programs start to fail on my laptop.
I raised a support case for this with Microsoft and after some investigation and upgrading to the latest T61 power drivers that were released a few days ago on the Lenovo site, MS support told me it is a fault of the T61 and that I would need to disable Microsoft APCI support to stop this memory leak from occuring and to take the issue up with Lenovo.
I have used the verifier tool to confirm that it is the Windows XP SP3 battc.sys memory module leaking.
I am running the latest T61 drivers and fully patch with MS drivers on SP3.
As MS have told me it is the fault of the T61 I am posting this issue here.
Thanks
Stephen

It is memory available to the kernelwhich itself does not show under a process in task manager as far as I am aware (unles it is taken account as part of the system process).
The best way to measure the available kernel memory space available is by using sysinternals procexp.
You need to download procexp and also install the windows debugging tools from Microsoft. Then in procexp set the "Options > Configure Symbols : Debughlp.dll path" to the new debughlp.dll installed with your debu tools and set the symbols path to srv*c:\Symbols*http://msdl.microsoft.com/download/symbols
Then you can choose in procexp "View > System Information" and see the used and total paged and non-paged kernel memory space.
poolmon helps monitor all the symbols that are taking up this memory and verifier lets you drill down to the exact module and the changes in memory for a module that is occuring.
Here are two really good links on it
http://blogs.msdn.com/ntdebugging/archive/2006/12/18/Understanding-Pool-Consumption-and-Event-ID_3A0...
http://blogs.msdn.com/ntdebugging/archive/2008/05/08/tracking-down-mmst-paged-pool-usage.aspx
In my poolmon i notice that Mmst and battc are taking alot of memory after my computer has been running for some time. Mmst being high is normal but battc should not continually be growing as it is which is why I raised the case to MS but they want verification it is not a Lenovo issue.

How do I report a major memory leak problem with Firefox 3.6.10 in WinXP?

After I installed Firefox 3.6.9 on a WinXP desktop, I occasionally had minor memory leak problems, reflected by getting "out of virtual memory" messages. I upgraded to 3.6.10 when notified that it was available and that it supposedly fixed stability problems. Ever since then, whenever I use Firefox, it starts out quick as a flash, but very rapidly slows down to a crawl, and has twice brought my system to a halt. IE does not cause this, nor any other program I use, but the execution speed of all programs slows as badly as Firefox. If I knew where to get older versions, I would back up to 3.6.9 or earlier. The situation now prevents me from using Firefox much at all.

Im running windows 7, Firefox 3.6.10 and before i updated to 3.6.10 my CPU never went above 10% with Firefox open. Now it can spike well above 50% and i have nothing different from when i had 3.6.9 to now when i have 3.6.10.
There is no evidence for me to suggest one of the additions i have is causing it, its all pointing to Firefox itself and the last update.

APEX 4.1.1 Memory Leak in IE7

Hi,
We busy upgrading our apex and db from 3.0/10G to 4.1.1/11.2G and notice that there appears to be a memory leak when using APEX. At one stage we have had IE7 using over a gig of memory.
When you load or refresh your page IE7 seems to grab on average 2-5MB of memory for each page load. At first we thought it may have been our apps or setup but this also happens when we go to app 4550 page 1 on apex.oracle.com.
How to replicate:
Open task manager to view the Memory Usage.
Using IE7
1. Go to http://apex.oracle.com/pls/apex/f?p=4550:1
2. Go back to Task Manager and note the readings once the CPU Usage for iexplore.exe has stablised to 0.
3. go back to IE7 and press F5
4. Repeat steps 2-3 and you will see the Memory usage increases.
We think this maybe due to a few jQuery UI memory leaks within IE7 and thought this bug ticket maybe of interest http://bugs.jqueryui.com/ticket/7666 (Slightly different versions but similiar experiences)
Could someone else confirm that they also experience the increasing or have had similiar problems and managed to resolve it?
TBH, it wouldn't be an issue to use another browser like Firefox to access the builder but this also affects the applications if they include APEX standard Javascript and CSS.
Thanking you in advance.
Alistair
Edited by: Alistair Laing on Jun 16, 2012 2:32 PM
Added Tags

Alistair Laing wrote:
Hi,
We busy upgrading our apex and db from 3.0/10G to 4.1.1/11.2G and notice that there appears to be a memory leak when using APEX. At one stage we have had IE7 using over a gig of memory.
When you load or refresh your page IE7 seems to grab on average 2-5MB of memory for each page load. At first we thought it may have been our apps or setup but this also happens when we go to app 4550 page 1 on apex.oracle.com.
How to replicate:
Open task manager to view the Memory Usage.
Using IE7
1. Go to http://apex.oracle.com/pls/apex/f?p=4550:1
2. Go back to Task Manager and note the readings once the CPU Usage for iexplore.exe has stablised to 0.
3. go back to IE7 and press F5
4. Repeat steps 2-3 and you will see the Memory usage increases.
We think this maybe due to a few jQuery UI memory leaks within IE7 and thought this bug ticket maybe of interest http://bugs.jqueryui.com/ticket/7666 (Slightly different versions but similiar experiences)
Could someone else confirm that they also experience the increasing or have had similiar problems and managed to resolve it?Anecdotally, yes. Don't have exact steps for replication or precise numbers, but I have noticed this in passing. On the junk that my client considers a PC suitable for web development the typical IE7 memory footprint with the APEX 3.0 builder and several other tabs running is about 52MB. Add APEX 4.1.1 and it climbs constantly until I have to pull the plug when it gets north of 150MB as the PC can't take it.
As well that I also have Firefox and 4.1.1 is still experimental at that site...
At the moment I don't have to resolve it and if I did the only option I'd propose is the replacement of IE7.
VC wrote:
Look at this http://www.bbc.co.uk/news/technology-18440979
Alistair Laing wrote:lol @ VC - I dont shop online at work :-D
I saw that eariler this week. I do agree with the concept though.So take appropriate action: charge extra for IE7 support.
The amount of work and effort involved in making our website look normal on IE7 equalled the combined time of designing for Chrome, Safari and Firefox.Is entirely accurate. If it's stated as a requirement, itemise it as an extra on the quote.
Educate management and bean counters: show them the one line of standards-compliant CSS that's all that is necessary in Safari, Chrome, Firefox and Opera (and just possibly in IE8/9/10), how it isn't supported in IE7, and the tortuous hacks and workarounds that are required to get something equivalent working there.

5508 upgrade to 7.6.100 memory leak

Similar Messages

Maybe you are looking for