Memory leak due to MediaProvider

Hello,
I am using jmc to create my own media player. I found that, when creating a new JMediaPane instance for opening and playing a new medium, the old instance is not deleted by the garbage collection, although it is not used and referenced anymore. The reason for this seems to be a still running thread in the class MediaProvider.
This behavior also occurs when using javafx and changing the media of a mediaplayer.
Has anyone any idea on how to solve this problem and how to build a (jmc-based) media player which reliably allows to open and play new media?
Thanks in advance!

Hello,
I am using jmc to create my own media player. I found that, when creating a new JMediaPane instance for opening and playing a new medium, the old instance is not deleted by the garbage collection, although it is not used and referenced anymore. The reason for this seems to be a still running thread in the class MediaProvider.
This behavior also occurs when using javafx and changing the media of a mediaplayer.
Has anyone any idea on how to solve this problem and how to build a (jmc-based) media player which reliably allows to open and play new media?
Thanks in advance!

Similar Messages

  • Memory leak due high database operations

    Our application is a network monitoring application , where we get lot of data from network every 2 minutes.
    When we try process large amount data in our application we start seeing memory leak. But if we control data inflow rate , then our application works fine with no leak.
    I am not able to profile our application with tools like Jprobe, as the profiler itself is running outofmemory even before I could reproduce the issue.
    Mostly likely DB is not able to handle the data at the rate we would like it to handle. We are using MySql with C3P0.
    I am not sure which objects are not getting garbage collected which is causing our application to run outofmemory since i am not able to profile the application.
    Will appreciate if anyone can share their experiences in debugging such problems

    We have added throttling mechanism to temporarily fix the problem. As I said before we get data every 2 mins from network. We have a data structure which is populated when we receive the data. So we count the numbers of rows in the data structure and once we reach the throttle we drop rest of the data. Throttle gets reset so that when data comes in next cycle we can again process it.
    The problem is we are not able handle data at a higher rate. Most of the times data received from the network is within our throttle limit , so there are no issues. We were seeing issues only when receive burst of data. So if we fixed the issue temporarily by adding throttling.
    I hope this clarifies your question

  • Memory leak due to http-basic-authn ?

    I reproduced the problem with the example/servlets/SessionServlet class. The http client (non-UI) creates session on every request and also passes in userid-password for http-basic authentication.
    Please note that we do NOT configure any authentication in weblogic deployment descriptors.
    With memory profiler OptimizeIt, I see the leak in the hashtable authUsers. The entry in the hashtable was created with:
    weblogic.servlet.internal.HttpServer.setAuthUser().
    The AuthenticatedUser object was created with:
    weblogic.security.acl.ClusterRealm.certify().
    It seems to me that Weblogic is trying to do the authentication by just see'ing userid-password in the Http headers. Even though when we want to do the authentication inside our application.
    I have the profiler snapshot but I do not know how to send the attachment in this posting. Let me know if I can email it to some address.
    Thanks
    -Rakesh

    I reproduced the problem with the example/servlets/SessionServlet class. The http client (non-UI) creates session on every request and also passes in userid-password for http-basic authentication.
    Please note that we do NOT configure any authentication in weblogic deployment descriptors.
    With memory profiler OptimizeIt, I see the leak in the hashtable authUsers. The entry in the hashtable was created with:
    weblogic.servlet.internal.HttpServer.setAuthUser().
    The AuthenticatedUser object was created with:
    weblogic.security.acl.ClusterRealm.certify().
    It seems to me that Weblogic is trying to do the authentication by just see'ing userid-password in the Http headers. Even though when we want to do the authentication inside our application.
    I have the profiler snapshot but I do not know how to send the attachment in this posting. Let me know if I can email it to some address.
    Thanks
    -Rakesh

  • Libclntsh - Memory leak

    Hi every body,
    I have a big problem with my c++ program, after 3 hours of execution, my program explose, no enouth memory and the cause is that i have a lot of memory leak due at the use of the oracle librairie libclntsh, my oracle version is 9.2.0.7
    There is any patch for this librairie ?
    Please i need help
    Thanks in advance

    On http://metalink.oracle.com
    Go in the "Patches & Updates" tab
    Click on Simple search
    Choose search by "Product or Family" and enter "RDBMS Server" in the following field.
    Choose the version you are looking for (9.2.0.8)
    Choose your plateform
    Click on the Go button.
    Nicolas.

  • My iMac keeps crashing due to a memory leak....  Any thoughts on what this means?

    I'll be using my iMac (27" late 2009) and it will suddenly cut to black.  Then after a second or two, a grey screen will appear and tell me an issue occured and to push any key to restart.  Once the computer restarts, the issue report pops up and it says I have a memory leak.  I don't know what that means, or how to fix it.  Any thoughts on the cause of why it's doing this, or the impending doom it may be heralding?  I've posted the issue report below incase anyone can glean anything from it.  Thanks for your help.
    Fri Feb 14 14:19:08 2014
    panic(cpu 4 caller 0xffffff801185211d): "zalloc: zone map exhausted while allocating from zone kalloc.64, likely due to memory leak in zone kalloc.64 (2370900672 total bytes, 37045323 elements allocated)"@/SourceCache/xnu/xnu-2422.1.72/osfmk/kern/zalloc.c:2494
    Backtrace (CPU 4), Frame : Return Address
    0xffffff8104ed3a30 : 0xffffff8011822f69
    0xffffff8104ed3ab0 : 0xffffff801185211d
    0xffffff8104ed3bb0 : 0xffffff801182aa2f
    0xffffff8104ed3be0 : 0xffffff8011c4bb5d
    0xffffff8104ed3c10 : 0xffffff8011c4c0b7
    0xffffff8104ed3c40 : 0xffffff8011c61b3a
    0xffffff8104ed3c60 : 0xffffff8011c61b91
    0xffffff8104ed3ca0 : 0xffffff8011c61d12
    0xffffff8104ed3ce0 : 0xffffff8011c93663
    0xffffff8104ed3d20 : 0xffffff8011c4abde
    0xffffff8104ed3eb0 : 0xffffff8011c4ada7
    0xffffff8104ed3ee0 : 0xffffff8011c8e4c3
    0xffffff8104ed3f50 : 0xffffff8011c93cc4
    0xffffff8104ed3f70 : 0xffffff7f923edbfb
    0xffffff8104ed3fa0 : 0xffffff7f923edc6e
    0xffffff8104ed3fb0 : 0xffffff80118d6aa7
          Kernel Extensions in backtrace:
             com.razer.common.razerhid(4.43)[1B7FEBF6-6668-A183-C80E-505105E80B16]@0xffffff7 f923e8000->0xffffff7f923fdfff
                dependency: com.apple.iokit.IOUSBFamily(650.4.4)[972D3024-AF9C-3E09-A9EC-D9AB2A559B38]@0xff ffff7f921cb000
                dependency: com.apple.iokit.IOHIDFamily(2.0.0)[1185D338-98A5-345E-84F8-E59DF819A61B]@0xffff ff7f92288000
                dependency: com.apple.iokit.IOUSBHIDDriver(650.4.4)[B79A7E01-DD3F-3C1A-840A-879D262C69DE]@0 xffffff7f9230d000
                dependency: com.apple.driver.IOBluetoothHIDDriver(4.2.0f6)[BDBCA485-A5D3-3EE0-A782-60D83447 BAEB]@0xffffff7f923d4000
    BSD process name corresponding to current thread: kernel_task
    Boot args: mbasd=1
    Mac OS version:
    13B42
    Kernel version:
    Darwin Kernel Version 13.0.0: Thu Sep 19 22:22:27 PDT 2013; root:xnu-2422.1.72~6/RELEASE_X86_64
    Kernel UUID: 1D9369E3-D0A5-31B6-8D16-BFFBBB390393
    Kernel slide:     0x0000000011600000
    Kernel text base: 0xffffff8011800000
    System model name: iMac11,1 (Mac-F2268DAE)
    System uptime in nanoseconds: 6500042405956
    vm objects:14896672
    vm object hash entri:1422080
    VM map entries:3665920
    pv_list:14364672
    vm pages:148044672
    kalloc.16:296143584
    kalloc.32:296364096
    kalloc.64:2370900672
    kalloc.128:8413184
    kalloc.256:2584576
    kalloc.512:2330624
    kalloc.1024:5713920
    kalloc.2048:1327104
    kalloc.4096:1859584
    kalloc.8192:6995968
    ipc ports:3312960
    threads:3060288
    uthreads:1891008
    vnodes:27132000
    namecache:10648800
    HFS node:36340432
    HFS fork:4812800
    buf.4096:2613248
    buf.8192:34643968
    ubc_info zone:2554704
    vnode pager structur:1418040
    Kernel Stacks:25870336
    PageTables:75939840
    Kalloc.Large:37970463
    Backtrace suspected of leaking: (outstanding bytes: 60608)
    0xffffff8011851c23
    0xffffff801182aa2f
    0xffffff8011c4bb5d
    0xffffff8011c4d667
    0xffffff8011c8e5e7
    0xffffff8011c93cc4
    0xffffff7f923edbfb
    0xffffff7f923edc6e
          Kernel Extensions in backtrace:
             com.razer.common.razerhid(4.43)[1B7FEBF6-6668-A183-C80E-505105E80B16]@0xffffff7 f923e8000->0xffffff7f923fdfff
                dependency: com.apple.iokit.IOUSBFamily(650.4.4)[972D3024-AF9C-3E09-A9EC-D9AB2A559B38]@0xff ffff7f921cb000
                dependency: com.apple.iokit.IOHIDFamily(2.0.0)[1185D338-98A5-345E-84F8-E59DF819A61B]@0xffff ff7f92288000
                dependency: com.apple.iokit.IOUSBHIDDriver(650.4.4)[B79A7E01-DD3F-3C1A-840A-879D262C69DE]@0 xffffff7f9230d000
                dependency: com.apple.driver.IOBluetoothHIDDriver(4.2.0f6)[BDBCA485-A5D3-3EE0-A782-60D83447 BAEB]@0xffffff7f923d4000
    last loaded kext at 280540738124: com.apple.filesystems.msdosfs          1.9 (addr 0xffffff7f92483000, size 65536)
    loaded kexts:
    com.taoeffect.ispy.kext          2.0.2
    com.quark.driver.Tether64          1.1.0d3
    com.logmein.driver.LogMeInSoundDriver          1.0.0
    com.squirrels.airparrot.framebuffer          3
    com.squirrels.driver.AirParrotSpeakers          1.7
    com.razer.common.razerhid          4.43
    at.obdev.nke.LittleSnitch          4052
    com.apple.filesystems.msdosfs          1.9
    com.apple.filesystems.ntfs          3.11
    com.apple.driver.AppleTyMCEDriver          1.0.2d2
    com.apple.driver.AGPM          100.14.11
    com.apple.driver.AppleHWSensor          1.9.5d0
    com.apple.driver.AudioAUUC          1.60
    com.apple.filesystems.autofs          3.0
    com.apple.iokit.IOBluetoothSerialManager          4.2.0f6
    com.apple.driver.AppleMikeyHIDDriver          124
    com.apple.driver.AppleUpstreamUserClient          3.5.13
    com.apple.iokit.IOUserEthernet          1.0.0d1
    com.apple.driver.AppleHDAHardwareConfigDriver          2.5.3fc1
    com.apple.kext.AMDFramebuffer          1.1.4
    com.apple.driver.AppleHDA          2.5.3fc1
    com.apple.Dont_Steal_Mac_OS_X          7.0.0
    com.apple.ATIRadeonX2000          8.1.8
    com.apple.driver.AppleHWAccess          1
    com.apple.driver.AppleMuxControl          3.4.12
    com.apple.driver.AppleBacklight          170.3.5
    com.apple.driver.AppleMikeyDriver          2.5.3fc1
    com.apple.iokit.IOBluetoothUSBDFU          4.2.0f6
    com.apple.kext.AMD4800Controller          1.1.4
    com.apple.driver.AppleMCCSControl          1.1.12
    com.apple.driver.AppleLPC          1.7.0
    com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport          4.2.0f6
    com.apple.driver.ACPI_SMC_PlatformPlugin          1.0.0
    com.apple.driver.AppleUSBCardReader          3.3.5
    com.apple.driver.AppleIRController          325.7
    com.apple.driver.AppleFileSystemDriver          3.0.1
    com.apple.AppleFSCompression.AppleFSCompressionTypeDataless          1.0.0d1
    com.apple.AppleFSCompression.AppleFSCompressionTypeZlib          1.0.0d1
    com.apple.BootCache          35
    com.apple.iokit.SCSITaskUserClient          3.6.0
    com.apple.driver.XsanFilter          404
    com.apple.iokit.IOAHCIBlockStorage          2.4.0
    com.apple.driver.AppleUSBHub          650.4.4
    com.apple.driver.AppleFWOHCI          4.9.9
    com.apple.iokit.AppleBCM5701Ethernet          3.6.9b9
    com.apple.driver.AirPort.Atheros40          700.74.5
    com.apple.driver.AppleAHCIPort          2.9.5
    com.apple.driver.AppleUSBEHCI          650.4.1
    com.apple.driver.AppleUSBUHCI          650.4.0
    com.apple.driver.AppleACPIButtons          2.0
    com.apple.driver.AppleRTC          2.0
    com.apple.driver.AppleHPET          1.8
    com.apple.driver.AppleSMBIOS          2.0
    com.apple.driver.AppleACPIEC          2.0
    com.apple.driver.AppleAPIC          1.7
    com.apple.driver.AppleIntelCPUPowerManagementClient          216.0.0
    com.apple.nke.applicationfirewall          153
    com.apple.security.quarantine          3
    com.apple.driver.AppleIntelCPUPowerManagement          216.0.0
    com.apple.kext.triggers          1.0
    com.apple.iokit.IOSerialFamily          10.0.7
    com.apple.iokit.IOSurface          91
    com.apple.driver.DspFuncLib          2.5.3fc1
    com.apple.vecLib.kext          1.0.0
    com.apple.driver.AppleGraphicsControl          3.4.12
    com.apple.iokit.IOFireWireIP          2.2.5
    com.apple.driver.AppleBacklightExpert          1.0.4
    com.apple.iokit.IONDRVSupport          2.3.6
    com.apple.kext.AMDSupport          1.1.4
    com.apple.AppleGraphicsDeviceControl          3.4.12
    com.apple.iokit.IOAudioFamily          1.9.4fc11
    com.apple.kext.OSvKernDSPLib          1.14
    com.apple.driver.AppleSMBusController          1.0.11d1
    com.apple.driver.AppleSMBusPCI          1.0.12d1
    com.apple.driver.AppleHDAController          2.5.3fc1
    com.apple.iokit.IOGraphicsFamily          2.3.6
    com.apple.iokit.IOHDAFamily          2.5.3fc1
    com.apple.iokit.IOBluetoothHostControllerUSBTransport          4.2.0f6
    com.apple.driver.AppleSMC          3.1.6d1
    com.apple.driver.IOPlatformPluginLegacy          1.0.0
    com.apple.driver.IOPlatformPluginFamily          5.5.1d27
    com.apple.driver.IOBluetoothHIDDriver          4.2.0f6
    com.apple.iokit.IOBluetoothFamily          4.2.0f6
    com.apple.driver.AppleUSBHIDKeyboard          170.15
    com.apple.driver.AppleHIDKeyboard          170.15
    com.apple.iokit.IOSCSIBlockCommandsDevice          3.6.0
    com.apple.iokit.IOUSBMassStorageClass          3.6.0
    com.apple.iokit.IOUSBHIDDriver          650.4.4
    com.apple.driver.AppleUSBMergeNub          650.4.0
    com.apple.driver.AppleUSBComposite          650.4.0
    com.apple.iokit.IOSCSIMultimediaCommandsDevice          3.6.0
    com.apple.iokit.IOBDStorageFamily          1.7
    com.apple.iokit.IODVDStorageFamily          1.7.1
    com.apple.iokit.IOCDStorageFamily          1.7.1
    com.apple.iokit.IOAHCISerialATAPI          2.6.0
    com.apple.iokit.IOSCSIArchitectureModelFamily          3.6.0
    com.apple.iokit.IOUSBUserClient          650.4.4
    com.apple.iokit.IOFireWireFamily          4.5.5
    com.apple.iokit.IOEthernetAVBController          1.0.3b3
    com.apple.driver.mDNSOffloadUserClient          1.0.1b4
    com.apple.iokit.IO80211Family          600.34
    com.apple.iokit.IONetworkingFamily          3.2
    com.apple.iokit.IOAHCIFamily          2.6.0
    com.apple.iokit.IOUSBFamily          650.4.4
    com.apple.driver.AppleEFINVRAM          2.0
    com.apple.iokit.IOHIDFamily          2.0.0
    com.apple.driver.AppleEFIRuntime          2.0
    com.apple.iokit.IOSMBusFamily          1.1
    com.apple.security.sandbox          278.10
    com.apple.kext.AppleMatch          1.0.0d1
    com.apple.security.TMSafetyNet          7
    com.apple.driver.AppleKeyStore          2
    com.apple.driver.DiskImages          371.1
    com.apple.iokit.IOStorageFamily          1.9
    com.apple.iokit.IOReportFamily          21
    com.apple.driver.AppleFDEKeyStore          28.30
    com.apple.driver.AppleACPIPlatform          2.0
    com.apple.iokit.IOPCIFamily          2.8
    com.apple.iokit.IOACPIFamily          1.4
    com.apple.kec.pthread          1
    com.apple.kec.corecrypto          1.0
    Model: iMac11,1, BootROM IM111.0034.B02, 4 processors, Intel Core i7, 2.8 GHz, 8 GB, SMC 1.54f36
    Graphics: ATI Radeon HD 4850, ATI Radeon HD 4850, PCIe, 512 MB
    Memory Module: BANK 0/DIMM0, 2 GB, DDR3, 1067 MHz, 0x80AD, 0x484D54313235533642465238432D47372020
    Memory Module: BANK 1/DIMM0, 2 GB, DDR3, 1067 MHz, 0x80AD, 0x484D54313235533642465238432D47372020
    Memory Module: BANK 0/DIMM1, 2 GB, DDR3, 1067 MHz, 0x80AD, 0x484D54313235533642465238432D47372020
    Memory Module: BANK 1/DIMM1, 2 GB, DDR3, 1067 MHz, 0x80AD, 0x484D54313235533642465238432D47372020
    AirPort: spairport_wireless_card_type_airport_extreme (0x168C, 0x8F), Atheros 9280: 4.0.74.0-P2P
    Bluetooth: Version 4.2.0f6 12982, 3 services, 23 devices, 1 incoming serial ports
    Network Service: Ethernet, Ethernet, en0
    Serial ATA Device: ST31000528ASQ, 1 TB
    Serial ATA Device: HL-DT-ST DVDRW  GA11N
    USB Device: Hub
    USB Device: Internal Memory Card Reader
    USB Device: BRCM2046 Hub
    USB Device: Bluetooth USB Host Controller
    USB Device: Hub
    USB Device: Keyboard Hub
    USB Device: Razer DeathAdder
    USB Device: Apple Keyboard
    USB Device: IR Receiver
    USB Device: Built-in iSight
    Thunderbolt Bus:

    Boot into safe mode (restart holding down SHIFT key). If no KP, then uninstall and reinstall those 3rd-party items that Roger pointed out, one at a time, and restart. Continue until you determine which ones are causing the problem. If KP while in safe mode, then most likely hardware related. Run the Apple Hardware Test suite, extended tests at least twice, followed by Rember.  See
    OS X About kernel panics,
    Technical Note TN2063: Understanding and Debugging Kernel Panics,
    Mac OS X Kernel Panic FAQ,
    Resolving Kernel Panics,
    How to troubleshoot a kernel panic, and
    Tutorial: Avoiding and eliminating Kernel panics for more details.

  • Kernel Panic due to memory leak?

    Hello All
    I have recently been noticing an issue where while playing music through iTunes my computer freezes and the music begins to skip forcing me to power down by holding in the power button. I have read most topics on this, however none address a memory leak in the 'iChat Agent.'
    My machine has 4GB of memory (dual 1.8GHz G5, PPC) and have never had this issue before. I am not sure if it is caused by iTunes or if it is just happens to be when listening to music. I have begun to look around and I have noticed that my memory shoots up after 1-2 days of the computer being on. This is due to the iChat Agent... it takes up about 2GB of RAM. Is this normal?
    It has happened 3 times now in the past 2 weeks. Any suggestions?

    well... the first time i got the kernel panic. it was text overlay on my screensaver that was running. The second time the computer just froze. I wonder though if the kernel panic would have eventually happened.
    i keep noticing now that this iChat Agent slowly creeps up during the day to about 2GB Real Memory and 2.4 Virtual Memory. is this normal or causing the freeze??

  • Cropping Crashes Aperture 3 due to Video Card Memory Leak?

    Recently after updating from 3.1.1 to 3.1.2 I have been experiencing crashing issues whenever I perform the cropping action.  I see the death of wheel following hitting the return key.  There was one time when the master version itself vaporized into thin air.  I also noticed from the iStat Menus that the issue only occurs when the ATI Radeon HD 2400 memory usage has reach its full capcity.  I quite firefox to release some of the memory then Aperture functions normally until the memory runs out again.  I would then see the death of wheel once again when I crop.
    Is Aperture crashing because I need a more powerful video card or is it a memory leak issue with the application?
    Thanks!
    iMac (Early 2008)
    2.4 GHz Intel Core  Duo
    4 GB 800 MHz DDR2 SDRAM
    ATI Radeon HD 2400

    Frank Caggiano wrote:
    Lets see if we understand this correctly.
    You had a system on which Aperture was crashing when you used the crop tool. You then got a brand new system and the crop tool still causes  Aperture to crash. Am I correct so far?
    What are the common factors between the old and new systems as far as Aperture goes? Not knowing how you migrated from the old to the new the only  thing we can say for certain is that the library is identical.
    So have you run the basic library first aid steps? Another thing to try is to create a new empty library, put an image into it and try cropping it and see what happens.
    Let us know what happens after those steps,
    regards
    Frank Caggiano wrote: Lets see if we understand this correctly. You had a system on which Aperture was crashing when you used the crop tool. You then got a brand new system and the crop tool still causes  Aperture to crash. Am I correct so far? What are the common factors between the old and new systems as far as Aperture goes? Not knowing how you migrated from the old to the new the only  thing we can say for certain is that the library is identical. So have you run the basic library first aid steps? Another thing to try is to create a new empty library, put an image into it and try cropping it and see what happens. Let us know what happens after those steps, regards
    I migrated everything from the old computer to the new.  I also tried creating a new library and the issue persists.  I've also tried the First Aid options all of 'Repair Permission, Repair Database, and Rebuild Database' none of which worked.  I've also tried reinstalling Aperture and it crashes on the first crop.
    I will need to be editing many photos in a few weeks and now I'm stuck with this issue.. HELP!!!!!!!
    It seems like others have run into the same issue also but no solutions!!
    Why is aperture 3.1 crashing after cropping images, any one else?
    http://www.google.com.hk/url?sa=t&source=web&cd=1&ved=0CBsQFjAA&url=https%3A%2F% 2Fdiscussions.apple.com%2Fthread%2F2642858%3Fstart%3D15%26tstart%3D0&ei=axUETrC0 DM3ciAL23ZXZDQ&usg=AFQjCNE9Kv1N--m8mCyaRkyWi3E9d-0aXg&sig2=qzgEONrK7vLfWetcPT69y A

  • 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.

  • Memory leak using xslprocessor.valueof in 11.1.0.6.0 - 64bit ??

    My company has made the decision to do all of our internal inter-system communication using XML. Often we may need to transfer thousands of records from one system to another and due to this (and the 32K limit in prior versions) we're implementing it in 11g. Currently we have Oracle 11g Enterprise Edition Release 11.1.0.6.0 on 64 bit Linux.
    This is a completely network/memory setup - the XML data comes in using UTL_HTTP and is stored in a CLOB in memory and then converted to a DOMDocument variable and finally the relevant data is extracted using xslprocessor.valueof calls.
    While this is working fine for smaller datasets, I've discovered that repeated calls with very large documents cause the xslprocessor to run out of memory with the following message:
    ERROR at line 1:
    ORA-04030: out of process memory when trying to allocate 21256 bytes
    (qmxdContextEnc,)
    ORA-06512: at "XDB.DBMS_XSLPROCESSOR", line 1010
    ORA-06512: at "XDB.DBMS_XSLPROCESSOR", line 1036
    ORA-06512: at "XDB.DBMS_XSLPROCESSOR", line 1044
    ORA-06512: at "SCOTT.UTL_INTERFACE_PKG", line 206
    ORA-06512: at line 28
    Elapsed: 00:03:32.45
    SQL>
    From further testing, it appears that the failure occurs after approximately 161,500 calls to xslprocessor.valueof however I'm sure this is dependent on the amount of server memory available (6 GB in my case).
    I expect that we will try and log a TAR on this, but my DBA is on vacation right now. Has anyone else tried calling the xslprocessor 200,000 times in a single session?
    I've tried to make my test code as simple as possible in order to track down the problem. This first block simply iterates through all of our offices asking for all of the employees at that office (there are 140 offices in the table).
    DECLARE
    CURSOR c_offices IS
    SELECT office_id
    FROM offices
    ORDER BY office_id;
    r_offices C_OFFICES%ROWTYPE;
    BEGIN
    OPEN c_offices;
    LOOP
    FETCH c_offices INTO r_offices;
    EXIT WHEN c_offices%NOTFOUND;
    utl_interface_pkg.get_employees(r_offices.office_id);
    END LOOP;
    CLOSE c_offices;
    END;
    Normally I'd be returning a collection of result data from this procedure, however I'm trying to make things as simple as possible and make sure I'm not causing the memory leak myself.
    Below is what makes the SOAP calls (using the widely circulated UTL_SOAP_API) to get our data and then extracts the relevant parts. Each office (call) should return between 200 and 1200 employee records.
    PROCEDURE get_employees (p_office_id IN VARCHAR2)
    l_request utl_soap_api.t_request;
    l_response utl_soap_api.t_response;
    l_data_clob CLOB;
    l_xml_namespace VARCHAR2(100) := 'xmlns="' || G_XMLNS_PREFIX || 'EMP.wsGetEmployees"';
    l_xml_doc xmldom.DOMDocument;
    l_node_list xmldom.DOMNodeList;
    l_node xmldom.DOMNode;
    parser xmlparser.Parser;
    l_emp_id NUMBER;
    l_emp_first_name VARCHAR2(100);
    l_emp_last_name VARCHAR2(100);
    BEGIN
    --Set our authentication information.
    utl_soap_api.set_proxy_authentication(p_username => G_AUTH_USER, p_password => G_AUTH_PASS);
    l_request := utl_soap_api.new_request(p_method => 'wsGetEmployees',
    p_namespace => l_xml_namespace);
    utl_soap_api.add_parameter(p_request => l_request,
    p_name => 'officeId',
    p_type => 'xsd:string',
    p_value => p_office_id);
    l_response := utl_soap_api.invoke(p_request => l_request,
    p_url => G_SOAP_URL,
    p_action => 'wsGetEmployees');
    dbms_lob.createtemporary(l_data_clob, cache=>FALSE);
    l_data_clob := utl_soap_api.get_return_clob_value(p_response => l_response,
    p_name => '*',
    p_namespace => l_xml_namespace);
    l_data_clob := DBMS_XMLGEN.CONVERT(l_data_clob, 1); --Storing in CLOB converted symbols (<">) into escaped values (&lt;, &qt;, &gt;).  We need to CONVERT them back.
    parser := xmlparser.newParser;
    xmlparser.parseClob(parser, l_data_clob);
    dbms_lob.freetemporary(l_data_clob);
    l_xml_doc := xmlparser.getDocument(parser);
    xmlparser.freeparser(parser);
    l_node_list := xslprocessor.selectNodes(xmldom.makeNode(l_xml_doc),'/employees/employee');
    FOR i_emp IN 0 .. (xmldom.getLength(l_node_list) - 1)
    LOOP
    l_node := xmldom.item(l_node_list, i_emp);
    l_emp_id := dbms_xslprocessor.valueOf(l_node, 'EMPLOYEEID');
    l_emp_first_name := dbms_xslprocessor.valueOf(l_node, 'FIRSTNAME');
    l_emp_last_name := dbms_xslprocessor.valueOf(l_node, 'LASTNAME');
    END LOOP;
    xmldom.freeDocument(l_xml_doc);
    END get_employees;
    All of this works just fine for smaller result sets, or fewer iterations (only the first two or three offices). Even up to the point of failure the data is being extracted correctly - it just eventually runs out of memory. Is there any way to free up the xslprocessor? I've even tried issuing DBMS_SESSION.FREE_UNUSED_USER_MEMORY but it makes no difference.

    Replying to both of you -
    Line 206 is the first call to xslprocessor.valueof:
    LINE TEXT
    206 l_emp_id := dbms_xslprocessor.valueOf(l_node, 'EMPLOYEEID');
    This is one function inside of a larger package (the UTL_INTERFACE_PKG). The package is just a grouping of these functions - one for each type of SOAP interface we're using. None of the others exhibited this problem, but then none of them return anywhere near this much data either.
    Here is the contents of V$TEMPORARY_LOBS immediately after the crash:
    SID CACHE_LOBS NOCACHE_LOBS ABSTRACT_LOBS
    132 0 0 0
    148 19 1 0
    SID 132 is a SYS session and SID 148 is mine.
    I've discovered with further testing that if I comment out all of the xslprocessor.valueof calls except for the first one the code will complete successfully. It executes the valueof call 99,463 times. If I then uncomment one of those additional calls, we double the number of executions to a theoretical 198,926 (which is greater than the 161,500 point where it usually crashes) and it runs out of memory again.

  • 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)

  • 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 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 in weblogic 6.0 sp2 oracle 8.1.7 thin driver

    Hi,
         I have a simple client that opens a database connection, selects from
    a table containing five rows of data (with four columns in each row)
    and then closes all connections. On running this in a loop, I get the
    following error after some time:
    <Nov 28, 2001 5:57:40 PM GMT+06:00> <Error> <Adapter>
    <OutOfMemoryError in
    Adapter
    java.lang.OutOfMemoryError
    <<no stack trace available>>
    >
    <Nov 28, 2001 5:57:40 PM GMT+06:00> <Error> <Kernel> <ExecuteRequest
    failed
    java.lang.OutOfMemoryError
    I am running with a heap size of 64 Mb. The java command that runs
    the client is:
    java -ms64m -mx64m -cp .:/opt/bea/wlserver6.0/lib/weblogic.jar
    -Djava.naming.f
    actory.initial=weblogic.jndi.WLInitialContextFactory
    -Djava.naming.provider.url=
    t3://garlic:7001 -verbose:gc Test
    The following is the client code that opens the db connection and does
    the select:
    import java.util.*;
    import java.sql.*;
    import javax.naming.*;
    import javax.sql.*;
    public class Test {
    private static final String strQuery = "SELECT * from tblPromotion";
    public static void main(String argv[])
    throws Exception
    String ctxFactory     = System.getProperty
    ("java.naming.factory.initial");
    String providerUrl     = System.getProperty
    ("java.naming.provider.url");
    Properties jndiEnv          = System.getProperties ();
    System.out.println ("ctxFactory : " + ctxFactory);
    System.out.println ("ProviderURL : " + providerUrl);
    Context ctx     = new InitialContext (jndiEnv);
    for (int i=0; i <1000000; i++)
    System.out.println("Running query for the "+i+" time");
    Connection con = null;
    Statement stmnt = null;
    ResultSet rs     = null;
    try
    DataSource ds     = (DataSource) ctx.lookup
    (System.getProperty("eaMDataStore", "jdbc/eaMarket"));
    con = ds.getConnection ();
    stmnt = con.createStatement();
    rs = stmnt.executeQuery(strQuery);
    while (rs.next ())
    //System.out.print(".");
    //System.out.println(".");
    ds = null;
    catch (java.sql.SQLException sqle)
    System.out.println("SQL Exception : "+sqle.getMessage());
    finally
    try {
    rs.close ();
    rs = null;
    //System.out.println("closed result set");
    } catch (Exception e) {
    System.out.println("Exception closing result set");
    try {
    stmnt.close ();
    stmnt = null;
    //System.out.println("closed statement");
    } catch (Exception e) {
    System.out.println("Exception closing result set");
    try {
    con.close();
    con = null;
    //System.out.println("closed connection");
    } catch (Exception e) {
    System.out.println("Exception closing connection");
    I am using the Oracle 8.1.7 thin driver. Please let me know if this
    memory leak is a known issue or if its something I am doing.
    thanks,
    rudy

    Repost in JDBC section ... very serious issue but it may be due to Oracle or
    to WL ... does it happen if you test inside WL itself?
    How many iterations does it take to blow? How long? Does changing to a
    different driver (maybe Cloudscape) have the same result?
    Peace,
    Cameron Purdy
    Tangosol Inc.
    << Tangosol Server: How Weblogic applications are customized >>
    << Download now from http://www.tangosol.com/download.jsp >>
    "R.C." <[email protected]> wrote in message
    news:[email protected]...
    Hi,
    I have a simple client that opens a database connection, selects from
    a table containing five rows of data (with four columns in each row)
    and then closes all connections. On running this in a loop, I get the
    following error after some time:
    <Nov 28, 2001 5:57:40 PM GMT+06:00> <Error> <Adapter>
    <OutOfMemoryError in
    Adapter
    java.lang.OutOfMemoryError
    <<no stack trace available>>
    >
    <Nov 28, 2001 5:57:40 PM GMT+06:00> <Error> <Kernel> <ExecuteRequest
    failed
    java.lang.OutOfMemoryError
    I am running with a heap size of 64 Mb. The java command that runs
    the client is:
    java -ms64m -mx64m -cp .:/opt/bea/wlserver6.0/lib/weblogic.jar
    -Djava.naming.f
    actory.initial=weblogic.jndi.WLInitialContextFactory
    -Djava.naming.provider.url=
    t3://garlic:7001 -verbose:gc Test
    The following is the client code that opens the db connection and does
    the select:
    import java.util.*;
    import java.sql.*;
    import javax.naming.*;
    import javax.sql.*;
    public class Test {
    private static final String strQuery = "SELECT * from tblPromotion";
    public static void main(String argv[])
    throws Exception
    String ctxFactory = System.getProperty
    ("java.naming.factory.initial");
    String providerUrl = System.getProperty
    ("java.naming.provider.url");
    Properties jndiEnv = System.getProperties ();
    System.out.println ("ctxFactory : " + ctxFactory);
    System.out.println ("ProviderURL : " + providerUrl);
    Context ctx = new InitialContext (jndiEnv);
    for (int i=0; i <1000000; i++)
    System.out.println("Running query for the "+i+" time");
    Connection con = null;
    Statement stmnt = null;
    ResultSet rs = null;
    try
    DataSource ds = (DataSource) ctx.lookup
    (System.getProperty("eaMDataStore", "jdbc/eaMarket"));
    con = ds.getConnection ();
    stmnt = con.createStatement();
    rs = stmnt.executeQuery(strQuery);
    while (rs.next ())
    //System.out.print(".");
    //System.out.println(".");
    ds = null;
    catch (java.sql.SQLException sqle)
    System.out.println("SQL Exception : "+sqle.getMessage());
    finally
    try {
    rs.close ();
    rs = null;
    //System.out.println("closed result set");
    } catch (Exception e) {
    System.out.println("Exception closing result set");
    try {
    stmnt.close ();
    stmnt = null;
    //System.out.println("closed statement");
    } catch (Exception e) {
    System.out.println("Exception closing result set");
    try {
    con.close();
    con = null;
    //System.out.println("closed connection");
    } catch (Exception e) {
    System.out.println("Exception closing connection");
    I am using the Oracle 8.1.7 thin driver. Please let me know if this
    memory leak is a known issue or if its something I am doing.
    thanks,
    rudy

  • Memory leak in Crystal Reports 2008

    We are running CR runtime 2008 version 12.3.4 and it looks like there is a memory leak. This is what we see happen (see chart#1). So just between these 4 report runs memory usage as gone up 64mb. We loose 20mb of memory with each report that we call. We actually see memory keep going up until the application fails due to out of memory issues around 1100mb of memory usage. This has been an issue ever since crystal 2008 was released we did not see this issue with Crystal Reports 11 or 10.
    chart#1:
    memory using in MB after opening and closing a small CR
    Start 123
    open rpt 225
    close rpt 204
    open rpt 245
    close rpt 226
    open rpt 266
    close rpt 247
    open rpt 287
    close rpt 268
    When is SAP going to address this issue?  Our work around for the last 2 years has been to close the CR application and reopen it multiple times a day to free up this lost memory and to revent "Out of memory" errors.  We will be forced to move to Reporting Services if this issue is not addressed soon.
    Josh

    Hi Josh,
    There are no memory leaks in CR 10, 11, 2008 or 2010 or 2011.
    Make sure you are closing and disposing all of your report objects, database connections, Data Sets etc. And then calling GC.Collect.
    And if you want to pursue this I suggest you give more details than just saying there is a leak and show a bunch of numbers that mean nothing without the code to verify those numbers.
    Thank you
    Don

  • Memory leak in MAX Preview resolved by build 411

    I was experiencing a memory leak while using the TLF that came as part of Flex 4 MAX Preview. Over the course of several hours, instances of a class called TextAccImpl would rapidly accumulate to the point where they accounted for over 50% of memory usage in my application, severely degrading performance.
    Upgrading to weekly build 411 resolved this issue - I didn't try with build 409 to see if it was also affected.
    Posting this as I wasn't sure if this entry in the change notes; "Fix a memory leak issue with the TextLayoutFormat cache" was related or not.

    If you modify the code just to call theCon=scp->getConnection(); and scp->releaseConnection(theCon); in an infinite loop, in as many threads as you like but initially in just one thread, does this program's memory usage stabilise or does it continue to use increasingly more and more memory until it crashes due to lack of memory?

Maybe you are looking for