Safari web process - memory leak?

Mac Pro seemed to have slowed to a crawl.
Safari 5.1.2 on SL 10.6.8
Activity Monitor showed I was low on memory - over 7GB was being used by 'safari web process' - slowly close all open pages until only left with two - one was simply the 'bing' home page, the other a page that had failed to load.
Anyone else had this kind of thing recently?

Safari has a known memory leak. Open teh Activity Monitor, sort the list of apps by Real Memory column. You will find one called Safari Web Content. This is the cause. If you are running an safari extensions, they use SWafari Web Content to run, you can try turning off your extensions to see if that helps. About the only know fix now, is to close safari regularly. 5.1.2 was suppose to close some leaks but has not. There are reports you can run safari in 32bit mode but I haven't confirmed if this helps or not.

Similar Messages

Process memory leak issue solaris 10

I have a process which has a memory leak issue. I ran this process on solaris 9 as well as solaris 10. When i run prstat command i get a different output for two. Funny thing is that memory leak noted in solaris 10 is much more than that in solaris 9 e.g if it is 1 MB in solaris 9 then its 4 MB in solaris 10.
What can be possibly causing this ? Is this related to kernel implementation on diff solaris ?

I have a process which has a memory leak issue. I ran this process on solaris 9 as well as solaris 10. When i run prstat command i get a different output for two. Funny thing is that memory leak noted in solaris 10 is much more than that in solaris 9 e.g if it is 1 MB in solaris 9 then its 4 MB in solaris 10.
What can be possibly causing this ? Is this related to kernel implementation on diff solaris ?

Finding Process Memory Leak?

I have been tracking down memory leaks in a Java server-based application. I recently ran the application for several hours, and monitored memory usage with both JConsole and the Unix �top� command. I encountered some behaviors that I don�t understand.
With JConsole, I observed that the heap memory usage was fairly constant over time. The Code Cache space, however, gradually increased in size over the life of the test. I expected some increase as additional methods in the application were executed, but it seems that eventually the rate of increase would level out. It did not. Any ideas why that might happen?
The resident memory (as reported by top) increased significantly over the life of the test. Using pmap and jmap, I was able to determine that the heap space was increasing (even though JConsole reported that the heap was constant.) So, it seems as though the heap usage of the application is constant, but the heap usage of the process is still growing? I am using Java HotSpot VM for Solaris (1.6.0-b105).
Any suggestions or insight would be appreciated.

I'm not sure exactly what you're saying, but it sounds like this:
A tool that's monitoring the VM says the memory used by your objects is not increasing, but other tools say the memory the VM has taken from the OS is increasing.
Is that the case? If not, nevermind--I've misunderstood.
If that is the case, then it's totally expected. The VM doesn't usually give memory back to the OS. If it hasn't used up the amount specified by -Xmx (or the default if you didn't specify -Xmx), it's free to just keep grabbing memory from the OS, rather than running a full GC to reclaim memory that it has used for objects but that is no longer reachable.

Safari 3 / Flash memory leak

I recently upgraded to Safari 3.0.4 and am noticing a huge memory leak problem if I leave a Flash-enabled page open for any length of time. I monitor the Virtual Memory usage of Safari using Activity Monitor. Usage goes from around 280MB to as high as 2.65GB before I have to shut down Safari for my 1GB machine to be usable.
See additional discussion here:
http://forums.macrumors.com/showthread.php?p=4610322
Does anyone know if this is a webkit issue, Apple/Safari issue, or a Flash issue?

Hi
Welcome to Apple Discussions
On my machines, Safari has had challenges with World Leaks since the beginning (right now it is using 750 mb of RAM with 38 tabs open on one window). A bit excessive, however, it's not a red flag given the amount of RAM and processor speed of the iMac. Nonetheless, it ought to be a lot more efficient with RAM usage. I would use the latest WebKit build, however, some of my Safari add-ons would be incompatible.
BTW, I too see jumps in usage, especially when accessing Flash content. The "only" way out is to quit/restart. Important to send feedback to Apple via the Safari Menu>Report Bugs to Apple.

Safari Flash Player Memory Leak?

I recently got a new macbook pro, 13" model (with the 2.2 GHz dual processor). Last night I noticed that it was running pretty slowly, something that I figured was weird considering the amount of power it has compared to my four year old desktop computer. I managed to isolate the problem: a memory leak with safari's flash player. I watch a lot of netflix and some TV episodes...and it turns out that the flash player accumulates up to 2 GB of RAM by itself. My pro has 4 GB of RAM and it never goes above 50% of that memory unless I watch videos. Only way to get around the problem is to force close the flash player application...but it's annoying to have to reload what I was watching. Any ideas on the fix for this?

Far as I know, Netflix doesn't use Flash, it uses Silverlight.
Your Flash likely got pwned.
So check here and update both
http://www.mozilla.org/en-US/plugincheck/
Then run ALL of OnyX's cleaning and maintainence aspects and reboot
http://www.titanium.free.fr/

Secd Process Memory Leak

Finding the secd process using 13GB of RAM was a bit of a shock. Watching its RAM consumption continue to increase, indicates a memory leak. Is this something anyone else has noticed? And any possible solutions?

Thanks - I think this helped, but will give it a day or two to see what happens.
My secd was over 32 GB the other day and the iMac wasn't quite its usual self. After restarting, secd's memory usage dropped away, but has been steadily creeping up over the last couple of days and was over 5GB this morning. So I tried dragging the Keychains folder to the trash and restarting.
The thing about dragging your keychain to the trash and restarting is, on logging back in you may be asked for a pile of passwords to all your mail accounts and your keychain will be empty!
I filled out all the requests for icloud passwords, but for the keychain to update properly, this took a while. I think what saved me from panicking about losing all my passwords, was going into System Preferences and signing into iCloud there. I was also requested to verify my iCloud login from another device (e.g., iPAD). I think this is what restored my keychain from the cloud.
Once the keychain had updated itself, I restarted the iMac again, and Mail returned to normal (no more requests for mail account passwords).
The only thing that wasn't restored after restarting was automatic keychain access to my time machine. I had to enter the password and save it to the keychain.

After 10.8.4....imagent process memory leak

I upgraded my MBA to 10.8.4. I started getting messages that my startup memory was full. I take a peak at Activity monitor and "imagent" is using 6GB of RAM and my HD has dropped in available space almost 100GB!!!
I force quit the process and reboot to recover the space soaked up by the leak, but it keeps coming back. As soon as I hear my fans going crazy I look at activity monitor and yep its back again.
Any one else with this issue after 10.8.4? I see in the release notes it was supposed to fix the reording of the messages in "imagent" but at this point I'll take the reorder problem over this problem.

Please read this whole message before doing anything.
This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
The purpose of the test is to determine whether the problem is caused by third-party software that loads automatically at startup or login, or by a peripheral device.
Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards. Boot in safe mode and log in to the account with the problem. Note: If FileVault is enabled, or if a firmware password is set, or if the boot volume is a software RAID, you can’t do this. Ask for further instructions.
Safe mode is much slower to boot and run than normal, and some things won’t work at all, including Wi-Fi on certain iMacs. The next normal boot may also be somewhat slow.
The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin. Test while in safe mode. Same problem? After testing, reboot as usual (i.e., not in safe mode) and verify that you still have the problem. Post the results of the test.

Imagent process memory leak

Hi all,
Since using a beta a couple of times I've noticed that imagent has gone nuts and started swapping insanely. I have about 30Gb free on my system drive, and it will chew through it all in a matter of minutes, then bring the whole computer to it's knees.
If I catch it in time and kill the process I loose that diskspace to vmswap files, but will get it back on reboot, and I can keep using the computer. If not, I have to hard reboot.
Using 10.7.3, and the Messages Beta. I have a yahoo, AIM, and iMessage accounts.
Also, since killing off the imagent process and it going nuts, even after a restart of the Messages app, I can't iMessage people.
Anyone else seen any odd behaviour?
Regards,
Alex

I also had Messages fail to deliver after killing imagent, and even after rebooting. Turns out in my case Messages had mysteriously switched to locating my contacts by email address rather than cell number. Switching contacts back to number made Message app resend failed messages successfully.

Memory leaks continuing in Safari and Web Kit

Will Apple ever fix the Safari memory leak?
As many of you know lots of reports over the years of Safari & Webkit having problems with memory leaks, and haven't seen a fix to it yet. This is a very important factor for usability of Safari.
A memory leak is when, after a period of time, your browser, which is the online field that's designed to function like a page and is used to access web pages and surf the World Wide Web, consumes more and more of your computer's memory until it reaches a point where it literally becomes impossible to use your computer. It's like your computer's stuck in cyber mud. You have to close any open software program or restart the entire computer.
Safari starts about 426.9 MB of real memory and 412.6 MB of virtual memormy and can go up to 1Gb of memory.
Has anyone come up with a fix to this problem ? If anyone has a workaround for this, please share it.
Meanwhile, Apple really should eliminate this problem once and for all.
FYI, I'm using Safari version 5.0.3 and the latest WebKit r72487 which was built on 21 November 2010.

My experience is that the same thing happens with Firefox and Chrome. The only difference with Chrome is that since the tabs are separate threads, they consume memory separately. The nice thing about that is that once the tab is closed memory is instantly freed. However, the helper thread always gets larger. Whether this is a memory leak or a consequence of having an application open over a long period of time is -I believe- open to discussion. I have experienced similar results with Eclipse (a memory intensive application). Daily shutdown/reboot and a few "Quit"s per a few hours fixes this issue. I don't know whether you would like to do this, though.
Using Safari 5.0.2.

Killing "Safari Web Content"

Hi,
I recently upgraded to Safari 6.0.
In the previous version of Safari (whatever the latest 5.x was), when the process "Safari Web Content" got too large (memory-wise) I could force-kill it using Activity Monitor. The behavior when that happened was that most (if not all) of the Safari Web Content memory would be freed, and all of the open tabs on Safari would be reloaded. This was very good behavior, IMO, because it allowed me to retrieve some memory without losing any content (other that now being unable to go back.)
In Safari 6.0, when Safari Web Content is killed, the entire Safari process is killed, and you have to start from scratch.
Was this an accidental feature (aka a bug) in Safari 5.x, or was this change intentional? Is there any way to free up memory in Safari 6.0 without killing the whole thing? Safari 6.0 seems to continue the trend of Safari being a real memory hog (apparently much worse than Google Chrome), and the behavior of 5.x was very useful in that regard.
Thanks,
Geoff

Clear the history...
From the Safari menu bar click Safari > Reset Safari
Select Clear History
Deselect the other boxes then click Reset.
Quit then relaunch Safari to test.

Safari Web Content taking 3/4 my RAM?

I have a single Safari tab open, and a subprocess called Safari Web Content is taking 1.5GB of ram.
I don't think there is any flash or anything on the page: http://explosm.net/comics/1949/
Why does Safari need so much memory? My Macbook only has 2GB in total, so everything is crawling. Is this a bug, or by design? I really like Safari and I don't want to have to switch to Chromium, but if Safari doesn't work well on 2GB machines, I guess I have no choice
Version 5.1 (7534.48.3) on Lion

dsa.me wrote:
This is not a memory leak. Running the browser in 32-bit mode solves the problems: http://mytech.dsa.me/en/2011/08/27/safari-5-1-memory-leak-solve/
You will be magically brought in the old good days when the grass was greener.
I don't understand why many people keep posting that link. If one looks at the Activity Monitor picture the memory usage is not that good. 1GB total for running Safari out of 3.75GB RAM isn't really a a great deal. Sure, it depends on how many tabs the guy had opened during the day.
Anyway, running Safari in 32 bit mode doesn't change much. Safari is simply not releasing the memory for the old pages. As it has been said it is not a proper memory leak because Safari seems to be aware it's retaining that memory, but it is still annoying nonetheless.

Web Process + Safari now hogging 50-75% more memory than Safari 5.0.5 did

Now that Apple has split Safari into two processes — Web Process (handles page loads and other traffic) and Safari (handles interface, bookmarks, history, etc) — these two processes together are using 50% to 75% more memory than Safari did before the upgrade to 5.1.
Three days ago, the most RAM I'd ever seen Safari hog (after several hours of surfing multiple tabs) was 1.1GB (still way more than it needed, once back down to 3 or 4 tabs).
Today, after surfing only an hour:
WebProcess 1.3GB
Safari 552MB
Anyone else seeing this? And anyone have ideas about limiting this memory hogging?

Well, to add a little more frustraton to this thread, a few weeks ago, when I first saw all the bugginess with this "update", I called Apple, was handed up to a higher-level tech person. He told me they were aware of all these problems, and promised me a fix would be released "ASAP". Well, a few weeks later, & of course, no fix. About a week ago, I called again, & was handed to a different higher-level guy, but this time he gave the same tired, "you should disable all your extensions & plug-ins" blah, blah, blah... And worse, he told me that he's heard nothing from users about issues with Safari!!!
Well, I then asked him if the problem really was one or some of the add-ons, why couldn't Apple just give us a list of at least some of the more popular ones that don't work. Why should ever single user have to go thru a one by one, trial & error, add one, then restart, then another, etc, since Apple could just do it, & let us know. Of course, that's never happened, so everyone has been trying anything they can, &/or resorting to using other browsers, & posting here & other places. I sure hope Apple quits stonewalling everyone, you would think they would address this, either by fixing it quickly, or at least letting everyone know they are aware of it, and that a fix will be coming, but pretending they no see, no hear nothing, and it's all in our heads, well, ...... it shucks.

Memory leak issues persist in Safari 6.0.5 (it's about time that Apple actually fixed this)

Safari has been notorious for its memory leaks for years, as I'm sure many of you know. I stopped using Safari as my main browser in 2010 or so, and I instead began to use Chrome. However, I recently had to use Safari to access some webpages, and I neglected to quit out of it. A few hours later, my computer slowed to a complete crawl. I was confused, because my computer never slows down to such a crawl, so I went into Activity Monitor to find the 'Safari Web Content' process using all of my available RAM, which was nearly 6 GB. Needless to say, Safari was force quit after that. I've heard that some plugins will cause this, but Flash was my only active plugin. Flash is, indeed, a heaping pile of crap that will readily eat resources as it sees fit- but this never happens to me in Chrome, and I use Flash all of the time n Chrome. This was after it had been sitting idle for quite some time, and I imagine that it would have used more RAM if it could.

Using 6.0.5 here without any of those issues ...
Regardless of whether Flash is being used, from your Safari menu bar click Help > Installed Plug-ins.
Try troubleshooting extensions and third party plug-ins.
From your Safari menu bar click Safari > Preferences then select the Extensions tab. Turn that off if there are any installed. Quit and relaunch Safari to test. If that helped, turn extensions back on then uninstall one a time to test.
If it's not an extensions issue, try troubleshooting third party plug-ins.
Back to Safari > Preferences. This time select the Security tab. Deselect: Allow all other plug-ins. Quit and relaunch Safari to test.
If that made a difference, instructions for troubleshooting plugins here.
my computer slowed to a complete crawl.
Checked to see exactly how much space is available ??
Click your Apple menu icon top left in your screen. From the drop down menu click About This Mac > More Info > Storage
Make sure there's at least 15% free disk space.
Checked the startup disk lately?
Launch Disk Utility located in HD > Applications > Utilities
Select the startup disk on the left then select the First Aid tab.
Click: Verify Disk (not Verify Disk Permissions)
If the disk needs repairing, restart your Mac while holding down the Command + R keys. From there you can access the built in utilities in OS X Recovery to repair the startup disk.
message edited by: cs

Detecting a memory leak in a process running on Solaris 5.7

Hi,
Iam running my application on solaris 5.7 platform.
I can see clear memory leak in that process.
Is there any tool or in-built functionality on solaris 5.7 to detect/fix that leak.
Thanks in advance,
Avvaru

Thanks for the reply. I already turned it off in both Safari and Spotlight preferences. However the problem persists. The process still runs, and from time to time it decides to leak all the memory as well. I really can't understand what the reason might be.
To be clear, in Safari-->Preferences-->Search-->Smart search field-->"Include Spotlight Suggestions" is un-checked. In Spotlight preferences all three "Spotlight Suggestions", "Bookmarks & History" and "Bing Web Searches" are un-checked. Process still runs under Spotlight as can be seen here:
After the last post I let it run for a while when it happened again, and below is just before i terminated it. Look at the memory usage!

Marshelling Web Service Response Memory Leak

I believe I have found a memory leak when using the configuration below.
The memory leak occurs when calling a web service. When the web service function is marshelling the response of the function call, an "500 Internal Server Error ... java.lang.OutOfMemoryError" is returned from OC4J. This error may be seen via the TCP Packet Monitor in JDeveloper.
Unfortunately no exception dump is outputted to the OC4J log.
Configuration:
Windows 2000 with 1 gig ram
JDeveloper 9.0.5.2 with JAX/RPC extension installed
OC4J 10.0.3
Sun JVM version 1.4.2_03-b02
To demonstrate the error I created a simple web service and client. See below the client and web service function that demonstrates it.
The web service is made up of a single function called "queryTestOutput".
It returns an object of class "TestOutputQueryResult" which contains an int and an array.
The function call accepts a one int input parameter which is used to vary the size of array in the returned object.
For small int (less than 100). Web service function returns successfully.
For larger int and depending on the size of memory configuration when OC4J is launched,
the OutOfMemoryError is returned.
The package "ws_issue.service" contains the web service.
I used the Generate JAX-RPC proxy to build the client (found in package "ws_issue.client"). Package "types" was
also created by Generate JAX-RPC proxy.
To test the web service call execute the class runClient. Vary the int "atestValue" until error is returned.
I have tried this with all three encodings: RPC/Encoded, RPC/Literal, Document/Literal. They have the
same issue.
The OutOfMemory Error is raised fairly consistently using the java settings -Xms386m -Xmx386m for OC4J when 750 is specified for the input parameter.
I also noticed that when 600 is specified, the client seems to hang. According to the TCP Packet Monitor,
the response is returned. But, the client seems unable to unmarshal the message.
** file runClient.java
// -- this client is using Document/Literal
package ws_issue.client;
public class runClient
public runClient()
* @param args
* Test out the web service
* Play with the atestValue variable to until exception
public static void main(String[] args)
//runClient runClient = new runClient();
long startTime;
int atestValue = 1;
atestValue = 2;
//atestValue = 105; // last one to work with default memory settings in oc4j
//atestValue = 106; // out of memory error as seen in TCP Packet Monitor
// fails with default memory settings in oc4j
//atestValue = 600; // hangs client (TCP Packet Monitor shows response)
// when oc4j memory sessions are -Xms386m -Xmx386m
atestValue = 750; // out of memory error as seen in TCP Packet Monitor
// when oc4j memory sessions are -Xms386m -Xmx386m
try
startTime = System.currentTimeMillis();
Ws_issueInterface ws = (Ws_issueInterface) (new Ws_issue_Impl().getWs_issueInterfacePort());
System.out.println("Time to obtain port: " + (System.currentTimeMillis() - startTime) );
// call the web service function
startTime = System.currentTimeMillis();
types.QueryTestOutputResponse qr = ws.queryTestOutput(new types.QueryTestOutput(atestValue));
System.out.println("Time to call queryTestOutput: " + (System.currentTimeMillis() - startTime) );
startTime = System.currentTimeMillis();
types.TestOutputQueryResult r = qr.getResult();
System.out.println("Time to call getresult: " + (System.currentTimeMillis() - startTime) );
System.out.println("records returned: " + r.getRecordsReturned());
for (int i = 0; i<atestValue; i++)
types.TestOutput t = r.getTestOutputResults();
System.out.println(t.getTestGroup() + ", " + t.getUnitNumber());
catch (Exception e)
e.printStackTrace();
** file wsmain.java
package ws_issue.service;
import java.rmi.RemoteException;
import javax.xml.rpc.ServiceException;
import javax.xml.rpc.server.ServiceLifecycle;
public class wsmain implements ServiceLifecycle, ws_issueInterface
public wsmain()
public void init (Object p0) throws ServiceException
public void destroy ()
System.out.println("inside ws destroy");
* create an element of the array with some hardcoded values
private TestOutput createTestOutput(int cnt)
TestOutput t = new TestOutput();
t.setComments("here are some comments");
t.setConfigRevisionNo("1");
t.setItemNumber("123123123");
t.setItemRevision("arev" + cnt);
t.setTestGroup(cnt);
t.setTestedItemNumber("123123123");
t.setTestedItemRevision("arev" + cnt);
t.setTestResult("testResult");
t.setSoftwareVersion("version");
t.setTestConditions("conditions");
t.setStageName("world's a stage");
t.setTestMode("Test");
t.setTestName("test name");
t.setUnitNumber("UnitNumber"+cnt);
return t;
* Web service function that is called
* Create recCnt number of "records" to be returned
public TestOutputQueryResult queryTestOutput (int recCnt) throws java.rmi.RemoteException
System.out.println("Inside web service function queryTestOutput");
TestOutputQueryResult r = new TestOutputQueryResult();
TestOutput TOArray[] = new TestOutput[recCnt];
for (int i = 0; i< recCnt; i++)
TOArray = createTestOutput(i);
r.setRecordsReturned(recCnt);
r.setTestOutputResults(TOArray);
System.out.println("End of web service function call");
return r;
* @param args
public static void main(String[] args)
wsmain wsmain = new wsmain();
int aval = 5;
try
TestOutputQueryResult r = wsmain.queryTestOutput(aval);
for (int i = 0; i<aval; i++)
TestOutput t = r.getTestOutputResults();
System.out.println(t.getTestGroup() + ", " + t.getUnitNumber());
catch (Exception e)
e.printStackTrace();
** file ws_issueInterface.java
package ws_issue.service;
import java.rmi.Remote;
import java.rmi.RemoteException;
public interface ws_issueInterface extends java.rmi.Remote
public TestOutputQueryResult queryTestOutput (int recCnt) throws java.rmi.RemoteException;
** file TestOutputQueryResult.java
package ws_issue.service;
public class TestOutputQueryResult
private long recordsReturned;
private TestOutput[] testOutputResults;
public TestOutputQueryResult()
public long getRecordsReturned()
return recordsReturned;
public void setRecordsReturned(long recordsReturned)
this.recordsReturned = recordsReturned;
public TestOutput[] getTestOutputResults()
return testOutputResults;
public void setTestOutputResults(TestOutput[] testOutputResults)
this.testOutputResults = testOutputResults;
** file TestOutput.java
package ws_issue.service;
public class TestOutput
private String itemNumber;
private String itemRevision;
private String configRevisionNo;
private String testName;
private String testConditions;
private String stageName;
private String testedItemNumber;
private String testedItemRevision;
private String unitNumber;
private String testStation;
private String testResult;
private String softwareVersion;
private String operatorID;
private String testDate; // to be datetime
private String comments;
private int testGroup;
private String testMode;
public TestOutput()
public String getComments()
return comments;
public void setComments(String comments)
this.comments = comments;
public String getConfigRevisionNo()
return configRevisionNo;
public void setConfigRevisionNo(String configRevisionNo)
this.configRevisionNo = configRevisionNo;
public String getItemNumber()
return itemNumber;
public void setItemNumber(String itemNumber)
this.itemNumber = itemNumber;
public String getItemRevision()
return itemRevision;
public void setItemRevision(String itemRevision)
this.itemRevision = itemRevision;
public String getOperatorID()
return operatorID;
public void setOperatorID(String operatorID)
this.operatorID = operatorID;
public String getSoftwareVersion()
return softwareVersion;
public void setSoftwareVersion(String softwareVersion)
this.softwareVersion = softwareVersion;
public String getStageName()
return stageName;
public void setStageName(String stageName)
this.stageName = stageName;
public String getTestConditions()
return testConditions;
public void setTestConditions(String testConditions)
this.testConditions = testConditions;
public String getTestDate()
return testDate;
public void setTestDate(String testDate)
this.testDate = testDate;
public String getTestName()
return testName;
public void setTestName(String testName)
this.testName = testName;
public String getTestResult()
return testResult;
public void setTestResult(String testResult)
this.testResult = testResult;
public String getTestStation()
return testStation;
public void setTestStation(String testStation)
this.testStation = testStation;
public String getTestedItemNumber()
return testedItemNumber;
public void setTestedItemNumber(String testedItemNumber)
this.testedItemNumber = testedItemNumber;
public String getTestedItemRevision()
return testedItemRevision;
public void setTestedItemRevision(String testedItemRevision)
this.testedItemRevision = testedItemRevision;
public String getUnitNumber()
return unitNumber;
public void setUnitNumber(String unitNumber)
this.unitNumber = unitNumber;
public int getTestGroup()
return testGroup;
public void setTestGroup(int testGroup)
this.testGroup = testGroup;
public String getTestMode()
return testMode;
public void setTestMode(String testMode)
this.testMode = testMode;

Many thanks for your help. This solved the issue for our .NET code, however the leak is still present in the report designer. I was also wondering if you could help further: because of the limits on the java memory process is there a way to ensure that a separate java process is started for each report that is loaded in my report viewers collection? Essentially the desktop application that i have created uses a tab control to display each type report, so each tab goes through the following code when displaying a report and closing a tab:
Is there a way to ensure that a different Java process is kicked off each time that I display a different report? My current code in c# always uses the same Java process so the memory ramps up. The code to load the report and then dispose of the report through closing the tab (and now the Java process) looks like this:
    private void LoadCrystalReport(string FullReportName)
      ReportDocument reportDoc = new ReportDocument();
      reportDoc.Load(FullReportName, OpenReportMethod.OpenReportByTempCopy);
      this.crystalReportViewer1.ReportSource = reportDoc;
    private void DisposeCrystalReportObject()
      if (crystalReportViewer1.ReportSource != null)
        ReportDocument report = (ReportDocument)crystalReportViewer1.ReportSource;
        foreach (Table table in report.Database.Tables)
          table.Dispose();
        report.Database.Dispose();
        report.Close();
        report.Dispose();
        GC.Collect();
Thanks

Safari web process - memory leak?

Similar Messages

Maybe you are looking for