Reminder to VZW - Memory Leak in VZ Access Mgr Software

Hello, Just in case you missed it. Verizon Access Manager software (windows 7/xp) steadily increases it's memory use after startup - after several hours it can grab up to 1 GB of memory according to the Windows Task Manager. I have heard of no updates to fix this issue. The workaround is to restart the program at least three times a day. A bit inconvenient.

jstring resposta =
(jstring)env->GetObjectArrayElement(respostaArray, indiceVariavel);You need to call DeleteLocalRef() on 'reposta' after you're finished with it in each loop iteration.

Similar Messages

Memory leak using repeater tag

Hi,
I am trying to show a report that has 33113 rows using a repeater tag, but i get the following error: "An error has occurred: java.lang.OutOfMemoryError".
I am using the pageFlow to bind a ArrayList that already contains the rows.
Any ideas?
Thanks a lot.

Link to Microsoft Connect issue
https://connect.microsoft.com/VisualStudio/feedback/details/1045459/memory-leak-using-windows-accessibility-tools-microsoft-narrator-windows-speech-recognition-with-net-applications
Link to Microsoft Community post
http://answers.microsoft.com/en-us/windows/forum/windows_7-performance/memory-leak-using-windows-accessibility-tools/8b32a81c-f828-415c-aec8-34e3106f9cb0?tm=1420469245606

Memory Leak Issue for Adobe Access iOS API

Hi,
We are trying to develop an iOS app (with ARC enabled) using Adobe Acces API 4.0 and we have identified that the function [drmManager createDRMSession] has memory leak.
DRMSESSION = [drmManager createDRMSession:METADATA playlist:PLAYLIST error:nil complete:^() {}];
We are using:
DRMSESSION -> weak
METADATA ->strong (as need to share within object)
PLAYLIST ->strong (as need to share within object)
After calling this function, the object is unable to dealloc and most of the leaking object related to networking (such as CFNetwork...)
Is this a known issue for the Adobe Access iOS API or we are missing some key steps.
Any suggestions is appreciated. Thanks in advance.

ans0600, sorry about that, I read Hiroshi's forward too quickly. I've done a little digging and have come up with two work-arounds:
Create a file with ARC disabled to translate the returned object to be an autorelease
declare the returned DRMSession as __unsafe_unretained and use CFRelease, as noted on stackexchange
In the future we may change this method to return an autoreleased object to avoid this issue. Let us know if you have any further questions!

I am getting a memory leak that sometimes leads to an unresponsive Firefox, but does not crash per se.

Hello, For the last couple of months, I am having issues with one of my tabs or the program itself causing a memory leak. I was hoping that subsequent releases would fix the problem, but when I downloaded V.11 it did not help.
I use tab mix plus and at any time, usually have about 25 tabs open. Everything functioned okay for 8 or so months up until recently.
I am wondering if there is a way to try to track down what is causing the leak. If it is one of my open pages, i will get rid of it. I tried opening one page at a time from scratch, but could not find the issue. .
I always have flash block enabled to cut down on the website junk.
using OSX firefox v11.

Now, I'm not going to say it's an Add-On problem because from the research I've been doing on this problem for the last half hour shows that everyone has DIFFERENT add-ons, but everyone's having the SAME problem....
So I went through my add-ons and disabled them one by one, and the single add-on that has been giving me grief is the latest WOT add-on. So, I have Firefox 11 (so does my wife) and we both have the WOT add-on. But that's where the similarity ends... I have Windows 7 x64, she has Windows XP x86.... but she doesn't have the memory leak problem.
What I see is a sawtooth pattern over time. Memory goes up a little over 30+ seconds, then drops down. But over half an hour, the peaks of the sawtooth are larger, and it doesn't drop back down to the same level again - always a little more than before. And before you know it, FF is peaking at 1.5+GB, dropping down to 1.2GB... and FF is running very, very slowly.... excessive disk accesses (paging probably, though I apparently I still have 1.5 to 2.0 GB of free RAM). Killing FF frees it all up, and if I open FF again, it's back to using 250MB of RAM.
So, it's not the add-ons per se, but how they're interacting with FF (or the other way round).... most likely, it's this plug-in container they created to stop add-ons from taking FF with them when they crashed. Seems to have created more problems than it has solved..... would be great if you could choose not to use it....

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.

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

How Do I identify a Memory Leak?

I know this is not enought information but...
My application used 3 hashtables in a Data object to store application data. I retrive this data from an XML file. I also download XML and merge it into andother XML file. Some of these hashtables contain object that contain more hashtables.
I am trying to use JProbe Profiler to find the leak. I notice the memory increases when I load the data into objects and put them into hash tables. I also notice an increase when I am merging newly downloaded XML into the current XML data. I am useing Nodelists and NOdes to get the data.
Does anyone have any tips or suggestion on how to find a memory leak?
Thank you,
Al

7 MB of XML file, loaded into a DOM? You realize, of
course, that DOMs are data structures that take up
memory, too, right?Yes I do. I load it into DOM then go through the Document and put the XML data into a custom file format (seialized objects). The data is sent from the server in the form of XML.
There's your problem. If you load X MB into memory
and keep it around as long as your application is
running, that's not necessarily a "leak". Yeah I realized this but it seems that if I load 7MB of my objects into hashtables my memory usage shouldn't increase by 30MB. I just assumed it would stay around 10MB.
The real issue is trading memory for CPU. If keeping
them in memory is crashing your app with OOM errors,
by all means just keep those objects in memory for as
long as you need them and then let the GC clean them
up. Don't put them in a Map, just let them have a
narrow method scope. Recreate them every time you
need them. Yes I'm beginning to see the light.
I'm sure you're thinking, "But recreating them will
cost CPU and slow down my app!" Yes, that's why it's
a tradeoff between memory and CPU.
Do you really need the whole document in memory at
once? If you're just cherry picking a few values out
of it, maybe you can use a SAX parser instead of a
DOM.
No I don't need all that data at once.
>
Either you're screwed or you need to rethink this.
You'd better hope that it's really not needed at
every moment for every client.After rethinking, I'm going to keep the serialized data in the file until I need it. Rather than searching through a hashtable for the object I want I will search the file.
What are your JVM settings for -Xms and -Xmx? Maybe
increasing those will do the trick.I did increase them and it helped a little, but I can still get a OutOfMemoryError if I try.
Are you sure these are the culprits? Have you
profiled the app to see if there are other sources of
leaks?Yes I have been profiling the application. It seems that there is a memory leek. I am just having trouble identifing it. I know the memory increases at 2 points. When I load the XML data into the DOM and when I load the DOM into my Custom object and then into the Hashtables.
Last resort? Buy more physical memory. It's cheap.I think I am going to keep unused data out of memory and access it form a file. After I make this change I think my memory usage will drop alot. I will profile again after I have this change made to see if there is a memory leak.
Thanks for you help,
Al

Address Book Sync Memory Leak

Address Book Sync Memory Leak , Using 5.6GB of Real Memory
Has anyone had issues with this? I have to force quit the process from Activity Monitor every 30 minutes.
Sampling process 3337 for 3 seconds with 1 millisecond of run time between samples
Sampling completed, processing symbols...
Analysis of sampling AddressBookSync (pid 3337) every 1 millisecond
Process:         AddressBookSync [3337]
Path:            /System/Library/Frameworks/AddressBook.framework/Versions/A/Resources/AddressBo okSync.app/Contents/MacOS/AddressBookSync
Load Address:    0x100000000
Identifier:      AddressBookSync
Version:         ??? (???)
Code Type:       X86-64 (Native)
Parent Process: SyncServer [3314]
Date/Time:       2011-05-30 10:09:28.670 -0400
OS Version:      Mac OS X 10.6.7 (10J869)
Report Version: 7

Unfortunately not. No groups and any Mobile Me account here not even many contacts (436) and any duplicates except in Ical after having restored my iphone 4 times. Something strange too, 2 weeks ago, Isync was running while I'm not registered on MM nor Icloud (turned off on my iphone) . Maybe a conflict between Outlook, Addressbook, Itunes and Isync on SL....I'm going crasy with this issue It reminds me of Windows ! Thx anyway, I'm gooing to contact apple in the following days.

Memory leak issue on Blackberry Torch 9860

I own a Blackberry Torch 9860 Os 7.0 Bundle 1465 for the last 5 months
Previously I had Blackberry Curve 9300 which I had upgraded to OS 6.0. It had memory leak issues wherein my application memory would gradually dropdown to merely KBs within a few days and I had to reboot it to restore the same.
When I purchased Torch 9860, I migrated my device settings from Curve to Torch using the Desktop Manager. I face the same memory leak issues in this new device as well. I have 3 email accounts configured on my device and some social networking applications which include facebook, twitter, and some messengers. I usually delete my emails and keep only a few useful mails for reference. Still I am facing this issue wherein I have to reboot my device to restore the application memory. It starts from 152 Mb and usually dropsdown to merely Kilobytes of memory. The phone freezes for around 1-2 minutes sometimes when I am on call, or accessing my contacts.
Also to let you know that I have a 8GB memory card on my phone which has around 1.6 GB free space. I have disabled Compression on my memory card as well.
Please advise as I am having a hard time using this time this way.
Regards,
Abhinav Sharma
Thanks and regards,
Abhinav Sharma

I have the almost same problem when i run the phone gap app on the 9800 torch OS 6 than this build of 1.2 MB takes the memory of 40 MB at run time and the device gives the low memory message and close the app forcefully.
In my app phone gap is using 3-4 html pages and java script .
And when i navigate on these pages it gives this message of memory low.
Please help me to out of this .
And please suggest if any professional help in this
Thanks\\\
Vipin Tomer

Memory leak in external interface SetReturnValue?

I'm having trouble with a memory leak in my application. I'm
hoping someone out there can help me find a fix or workaround, or
tell me what I'm doing wrong.
The leak seems to be coming from the flash external
interface; specifically, IShockwaveFlash.SetReturnValue(String). My
application is written in Visual Basic 2008, connecting to Flash
9.0.124.0 (activex version).
I've written a fairly simple flash/VB program pair to
illustrate the problem.
The SWF contains a button, 2 dynamic text fields, and the
ActionScript 2 code below.
The VB project contains a Form with a AxShockwaveFlash object
and the VB code below.
When this program is run, and the button is clicked a lot
(10's of thousands of times), the application's memory creeps up
and never seems to fall back down. If the string passed to
SetReturnValue is longer, memory is consumed faster. But if the
call to SetReturnValue is commented-out, the application's memory
usage remains stable.
If anyone has any suggestions on how to proceed, I'd be
grateful.
(By the way: I'm using a freeware program called DoItAgain to
automate the button pressing.)

I have developed two simple Java and corresponding
C++ classes. Use code tags when you post your code.
You are missing a lot of error checking. JNI calls, every single one, will usually be followed by some sort of error checking. Any that access classes, methods, fields or allocate object must be followed by checks for java exceptions.
You will need to reduce your code to a smaller sample. Otherwise it is unlikely anyone will look at it.
You also need to specify how you know that a memory leak is occurring.

Memory Leak in my JDBC application.

Hi
I am experiencing a memory leak in a test application using the JDBC-ODBC bridge to access an MS Access DB.
I close the result set, statement and connection objects after each query. Even then the memory allocated to the process increases by about 20K after each query.
Is there anything else I should do apart from closing these objects??
Thanks a lot for your time.
Fred.

I am having the same problem using JDBC-ODBC bridge with the MS SQL server DB. Even after closing all of the objects as specified.
Sorry couldn't be of much help but check the following link
http://www.allaire.com/Handlers/index.cfm?ID=12409&Method=Full
But I do not have a work around for this may be I am not looking at the right response.
Can some one please help.

Memory Leak in 8.1.6.0.1 JDBC/OCI for Solaris

Hello,
there is a memory leak in the 8.1.6.0.1 JDBC-OCI driver for solaris.
The leak causes your jvm to eat up all memory
if you reuse callable statements
(calling one statement multiple times with
different values).
The thin driver has no such problem. Is
there any fix available ?

Ok. The code spans multiple classes and
most of it comes from a customized version
of the Enhydra Java Application server.
I have a class called "StandardDBConnection"
which caches CallableStatements and is a
wrapperclass for java.sql.DBConnection. The
interesting method here is "prepareCall":
* Get a callable statement given an SQL string. If the statement is
* cached, return that statement, otherwise prepare and save in the
* cache.
* @param sql The SQL statement to be called.
* @return a new CallableStatement object containing the
* pre-compiled SQL statement.
* @exception java.sql.SQLException If a database access error occurs
* statement.
public synchronized CallableStatement prepareCall(String sql)
throws SQLException {
PreparedStatement preparedStmt;
logDebug ("Prepare call: " + sql);
validate();
preparedStmt = (PreparedStatement)preparedStmtCache.get(sql);
// Check if the object returned by the cache really is a
// callable statement. if it is not, someone did call first
// prepareStatement() and now prepareCall() with the same
// sql. Silently replace the existing cache entry by a
// callable statement in this case.
if (preparedStmt instanceof CallableStatement) {
preparedStmt.clearParameters();
else {
// Need to close the old PreparedStatement in case we have to
// replace it with a CallableStatement
if (preparedStmt != null) {
preparedStmt.close();
else if (preparedStmtCache.size() >= maxPreparedStmts) {
String key = (String)preparedStmtCache.keys().nextElement();
((PreparedStatement) preparedStmtCache.remove(key)).close();
preparedStmt = connection.prepareCall(sql);
preparedStmtCache.put(sql, preparedStmt);
return (CallableStatement)preparedStmt;
The statements get closed when I close the
connection:
boolean closeStmts = true;
// Close the prepared statements.
Enumeration e = preparedStmtCache.keys();
while (e.hasMoreElements() && closeStmts) {
String key = (String)e.nextElement();
try {
((PreparedStatement)
preparedStmtCache.remove(key)).close();
} catch (SQLException except) {
// Ignore errors, we maybe handling one.
closeStmts = false;
log.write(Logger.NOTICE,
"DBConnection[" + id + "]: " + url +
"\nUnable to close statements. Continuing....\n");
In my classes using database queries I just
use the prepareCall method of DBConnection
and do not have to care about anything.
Works perfectly with the thin driver, but
as soon as I switch to oci... :-|
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by JDBC Dev Team:
Soda, Rupper,
Do you mind posting some code that shows us what your code was doing when you notice this leak?
Thanks.<HR></BLOCKQUOTE>
null

Memory leak using Oracle thin driver on wls6.1...

Hi, I've been attempting to find a memory leak in an application that
runs on WLS 6.1 SP2, on Solaris 8 and accessing an Oracle 9i db. We
are using the Type 4 (Thin) driver and JProbe reports that hundreds of
oracle.jdbc.* objects are left on the heap after my test case
completes. Specifically oracle.jdbc.ttc7.TTCItem is the most common
loiterer on the heap. I have verified that after each database access
the resources are release correctly (i.e. ResultSet, Connection,
PreparedStatement, etc.)
Has anyone encountered similar problems? or does anyone know how to
fix this?
Thanks,
Tim Watson

Hi Tim!
We have seen problem using oracle 817 client that has been resolved using
901 client for type2(oci) driver, But i am not aware of thin driver
problem. You should check with oracle if they have find any customer's
with this problem.
Thanks,
Mitesh
Tim Watson wrote:
Hi, I've been attempting to find a memory leak in an application that
runs on WLS 6.1 SP2, on Solaris 8 and accessing an Oracle 9i db. We
are using the Type 4 (Thin) driver and JProbe reports that hundreds of
oracle.jdbc.* objects are left on the heap after my test case
completes. Specifically oracle.jdbc.ttc7.TTCItem is the most common
loiterer on the heap. I have verified that after each database access
the resources are release correctly (i.e. ResultSet, Connection,
PreparedStatement, etc.)
Has anyone encountered similar problems? or does anyone know how to
fix this?
Thanks,
Tim Watson

Memory leak in ODBC Driver version 8.1.7.8?

We have a web application connected to an 8.1.7 database on a MS Windows 2000 SP 2 server.
We recently upgraded ODBC driver from 8.1.7.7 to 8.1.7.8 and found that we ran out of virtual memory.
On further investigations, a simple refresh of our summary web page (going to the database to select a small recordset - even when there are only 2 records with 6 small VARCHAR2 fields) causes the virtual memory usage to increase by approximately 1Mb each refresh.
The same refresh using driver 8.1.7.7 occasionally increases the VM usage by 4Kb!
Is there a memory leak in ODBC driver version 8.1.7.8?

Hello Thomas,
thanks for your tips, but they did not help. Activating Connection Polling did not change anything. And opening another connection did not help, either. I did it the following way:
Sub memtest2()
Dim conODBC As New ADODB.Connection
conODBC.ConnectionString = "Data Source='xxxx';User ID='xxx';Password='xxx'"
conODBC.Open
Dim Rs1 As Recordset, Rs2 As Recordset, DB1 As Database
Set DB1 = CurrentDb
Set Rs1 = DB1.OpenRecordset("select id from artikel")
Do While Not Rs1.EOF
    Set Rs2 = DB1.OpenRecordset("select * from artikel where id=" & Rs1("id"))
    'do something
    Rs2.Close
    Set Rs2 = Nothing
    Rs1.MoveNext
Loop
Rs1.Close
Set Rs1 = Nothing
DB1.Close
Set DB1 = Nothing
conODBC.Close
End Sub
Perhaps one of you has another tip how this can be done.
@Lukasz:
using a seperate ADODB.Connection works fine, but that does not solve the problem itself. At first I would have to rewrite much code and the second much bigger thing is that the memory leak occurs even when working with bound forms in MS Access. For example: I have one large form with many subforms on it. If i go from record to record on this form the memory usage is increasing dramatically fast and there is no way to influence what kind of connection MS Access is using for bound forms.
Regards
Thorstem

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

Reminder to VZW - Memory Leak in VZ Access Mgr Software

Similar Messages

Maybe you are looking for