Telemetry + uploadFromBitmapData == Memory leak, crash
Hi all,
This bug/crash is a memory leak that only occurs when utilizing texture upload and -advanced-telemetry at the same time.
Testcase at: http://onetacoshort.com/temp/telemetry_leak.zip
Testcase README file is as follows:
Using Scout to debug an app compiled with -advanced-telemetry using the new ASC2.0 compiler, uploading textures via:
flash.display3D.textures.Texture.uploadFromBitmapData(bd);
causes a memory leak and eventual crash. Observed when using AIR 3.6 - 3.8 on both iOS and Android.
Memory usage in the "Other" category rises infinityly in steps until the app crashes (see scout_screenshot_telemetry.jpg).
If compiled without -advanced-telemetry, the app runs properly (see scout_screenshot_without.jpg)
Note that if the Testcase app is not connected to a Scout instance (i.e. Adobe Scout app not installed, or not enabled), it does not crash.
So it's probably not critical, but it's a testing irritation.
Best,
-Jeff
Hi Jeff,
Thanks for the heads up. Would you mind copy/pasting this report over to bugbase.adobe.com as a new bug report? Once added please shoot me the bug number and I'll follow up internally.
Thanks,
Chris
Similar Messages
-
I have a memory leak problem using the CWGraph control.
I have an SDI application (MFC using Measurement Studio) and I generate dynamicaly a dialog containing a 2D Graph, and I use the OnTimer() of the dialog to generate data and to update the graph, with a timer of 50ms. In OnTimer() function I have a loop to generate
and to update two plots on the graph. When I call a method of the graph (for example for changing the color of the plot or for updating a plot (using PlotXvsY)), I have a periodic increasing of memory with a fixed amount of memory (4k). In the same OnTimer() function I update also some CWSlide controls without memory leaks.
If I comment the line that call a method of graph
(ex. m_Graph.Plots.Item(1)....), the code works wi
thout memory leaks.
I'll apreciate any suggestion about this problem.I had the same memory leak problem with my program as well. I do not think it is because of using CWGraph. Memory leaks occur when you allocate memory and did not free them. The problem will accumulate and crashed randomly (sometime it crashed when you just move mouse around). Try this: if the program does not crash (memory leak crash) on the first time it compiles and runs, it is probable has nothing to do with the CWGraph. On the second and third run, if you did not free variable, the program will usually crashed. If your program crashed on the first time it runs, the problem might be something else.
-
How to deal with Memory Leaks, that are caused by Binding
Hi, I recently noticed (huge?) memory leaks in my application and suspect bindings to be the cause of all the evil.
I made a little test case, which confirms my suspicion:
import javafx.application.Application;
import javafx.beans.property.SimpleStringProperty;
import javafx.beans.property.StringProperty;
import javafx.scene.Scene;
import javafx.scene.control.Button;
import javafx.scene.layout.VBox;
import javafx.stage.Stage;
public class TestAppMemoryLeak extends Application {
public static void main(String[] args) {
launch(args);
@Override
public void start(Stage stage) throws Exception {
VBox root = new VBox();
Button button = null;
for (int i = 0; i < 100000; i++) {
button = new Button();
button.textProperty().bind(text);
button.textProperty().unbind(); // if you don't call this, you can notice the increased memory of the java process.
root.getChildren().add(button);
Scene scene = new Scene(root);
stage.setScene(scene);
stage.show();
private StringProperty text = new SimpleStringProperty("test");
}Now the problem is, HOW can I know, when a variable is no longer needed or overwritten by a new instance.
Just an example:
I have a ListView with a Cell Factory. In the updateItem method, I add a ContextMenu. The textProperty of each MenuItem is bound to a kind of global property, like in the example above. I have to do it in the updateItem method, since the ContextMenu differs depending on the item.
So every time the updateItem method is called a new ContextMenu is created, which binds some properties, but the old context menus remain in memory.
I guess there could be many more example.
How can I deal with it?I've dealt with this situation and created a Jira issue for it, but I also have a work-around that is a bit unwieldy but works. I'll share it with you.
The bug that deals with this (in part atleast): http://javafx-jira.kenai.com/browse/RT-20616
The solution is to use weak invalidation listeners, however they are a bit of a pain to use as you cannot do it with something simplistic as "bindWeakly"... and you need to keep a reference around to the wrapped listener otherwise it will just get garbage collected immediately (as it is only weakly referenced). Some very odd bugs can surface if weak listeners disappear randomly because you forgot to reference them :)
Anyway, see this code below, it shows you some code that is called from a TreeCell's updateItem method (I've wrapped it in some more layers in my program, but it is essentially the same as an updateItem method):
public class EpisodeCell extends DuoLineCell implements MediaNodeCell {
private final WeakBinder binder = new WeakBinder();
@Override
public void configureCell(MediaNode mediaNode) {
MediaItem item = mediaNode.getMediaItem();
StringBinding episodeRange = MapBindings.selectString(mediaNode.dataMapProperty(), Episode.class, "episodeRange");
binder.unbindAll();
binder.bind(titleProperty(), MapBindings.selectString(mediaNode.dataMapProperty(), Media.class, "title"));
binder.bind(ratingProperty(), MapBindings.selectDouble(mediaNode.dataMapProperty(), Media.class, "rating").divide(10));
binder.bind(extraInfoProperty(), Bindings.when(episodeRange.isNull()).then(new SimpleStringProperty("Special")).otherwise(episodeRange));
binder.bind(viewedProperty(), item.viewedProperty());
subtitleProperty().set("");
}This code makes use of a class called WeakBinder -- it is a helper class that can make Weak bindings and can keep track of them. When you call unbindAll() on it, all of the bindings it created before are released immediately (although they will also disappear when the Cell itself is garbage collected, which is possible because it only makes weak references).
I've tested this extensively and it solves the problem of Cells keeping references to objects with much longer life cycles (in my case, the MediaNode passed in has a longer lifecycle than the cells and so it is important to bind weakly to it). Before this would create huge memory leaks (crashing my program within a minute if you kept refreshing the Tree)... now it survives hours atleast and the Heap usage stays in a fixed range which means it is correctly able to collect all garbage).
The code for WeakBinder is below (you can consider it public domain, so use it as you see fit, or write your own):
package hs.mediasystem.util;
import java.util.ArrayList;
import java.util.HashMap;
import java.util.List;
import java.util.Map;
import javafx.beans.InvalidationListener;
import javafx.beans.Observable;
import javafx.beans.WeakInvalidationListener;
import javafx.beans.property.Property;
import javafx.beans.value.ObservableValue;
public class WeakBinder {
private final List<Object> hardRefs = new ArrayList<>();
private final Map<ObservableValue<?>, WeakInvalidationListener> listeners = new HashMap<>();
public void unbindAll() {
for(ObservableValue<?> observableValue : listeners.keySet()) {
observableValue.removeListener(listeners.get(observableValue));
hardRefs.clear();
listeners.clear();
public <T> void bind(final Property<T> property, final ObservableValue<? extends T> dest) {
InvalidationListener invalidationListener = new InvalidationListener() {
@Override
public void invalidated(Observable observable) {
property.setValue(dest.getValue());
WeakInvalidationListener weakInvalidationListener = new WeakInvalidationListener(invalidationListener);
listeners.put(dest, weakInvalidationListener);
dest.addListener(weakInvalidationListener);
property.setValue(dest.getValue());
hardRefs.add(dest);
hardRefs.add(invalidationListener);
}Let me know if this solves your problem. -
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.... -
I typically keep many windows with several tabs open. It is possible that this causes more crashes since the number of pages multiplies any effect most users with less pages/tabs would experience. I have been having problems with Firefox crashing Using the windows task manager I have looked into this issue monitoring lots of variables. Bottom line the crash is caused by increasing memory usage possibly caused by the flash add on which is doing many IO reads on at least one offending page/tab. Could some sites be using flash to read from my disk without permission and there is a memory leak in either flash of the code the sites uses? I have searched the web for a task manager like add-on for Firefox tabs that would allow me to determine the offending page/tab/add-on/extension. It seems like a great idea which has not been implemented. Since I am a developer I would be happy to implement, but would like some guidance since my knowledge of your product is only at the user level.
There is currently about:memory page which is being actively developed. A "task manager"of sorts is also in the works AFAIK. If you want to help out, your best bet is to find the applicable bug in Bugzilla. If you have the coding skills I can help get you in touch with a mentor - just let me know.
-
[LPX] Drummer/Drum Kit Designer memory leak causing crash
After working with LPX for a couple of days after release with almost no problems save for a few system overload errors that always seemed to sort themselves out, I loaded up a project I had been working on to find that it crashed every time I tried to play the track. Other, smaller projects, still played in varying degrees, some having to wait for a long time seemingly for samplers to load up etc.
I did some testing (painstaking, considering that I was having to force-quit the application for my computer to even run again; as an aside there were never any error reports for whatever reason) and found that it appears to be Drummer/Drum Kit Designer that's causing massive memory usage. Looking at the activity monitor when loading the project revealed that the memory usage would just go up and up until it maxed out my (rather modest) 4GB RAM, at which point there would be no free memory and the computer would slow almost to a standstill. Removing all instances of Drum Kit Designer and Drummer reduces the load to a point where it is once again manageable.
This seems like a fault in Drummer, I'm thinking possibly a memory leak. Has anyone else been experiencing this problem/anyone have any thoughts as to how it could be fixed?
Thanks in advance,
JasperThis is not a memory bug. It's simply the nature of the new Drummer.
Drummer uses a LOT of samples. It's a 13GB download for a reason. You will need more than 4GB to use drummer and not run into issues.
The nature of the modern Logic engine - which seems unchanged from v9 - makes it very bad at being able to tell when it's running out of memory. Logic will simply freeze or crash most of the time it runs out. The freeze would be down to it using literally every last MB on your RAM without overstepping the boundary, and the crash would be downt to it claiming to need more real RAM than you have spare.
Producer kits use 5.1 surround samples, and submixes them to stereo in a way that posistions them around the space. Whilst a doddle for a modern machine, you Mac is rather long in the tooth to be trying to do that whilst struggling to handle 1.2GB patches with 4GB of RAM total. -
2014.2 Crash by scrubbing - serious memory leak? (screenshot attached)
Hello. I've bought one year premiere pro cc plan. After upgrate from 2014.1 to 2014.2 I suffer with many crashes a day. I can't roll back, because I am in the middle of the feature film edit and new files are not opened by 2014.1
The most anoying crash is about memory use growth.
First - my system and sequence specs:
I have 48gb ram, intel i73930k processor, 4TB main drive and 3x250SSD drives for scratch disks. My Gpu is 2 x nvidia gtx 780 (3gb ram each). I work in 4k workspace and with uhd timeline 2.35 : 1 ratio. (3840x1628)
Second - how to crash.
I open the pproj file (about 8mbytes in size). It is a full feature film, i edit it in 3 parts for better performance. My main codec is cineform, both for HD previews and final 4K encoding.
Then I move playhead over any clip already rendered with preview (HD - mpeg or cineform).
Then I hold left mouse button and I start to scrub playhead left/right randomly along timeline, the problem unfolds: ram usage starts to go up, after some time of scrubbing it hits the ceiling and premiere crashes (along with eventual other apps opened as firefox).
It seems like premiere is registering every displayed frame in memory, even if it is already rendered as preview. And there is no limit set for doing this, so it overflows and crash.
As you see on the picture, in preferences there is 8GB reserved for other apps, and optimization for memory set.
Scrubbing over non-rendered clips makes ram eating even worse, crash occurs earlier.
I wonder - do you people have this similar problem? Could someone reproduce this inside any larger project (30 minutes of standard movie edit).
I would like to find solution, because I cant allow for so many crashes during serious production workflow.
nlI'm having the same problem too.
I've been posting my issues on another post entitled, "Just spent $7000. on new custom computer and PremiereProcc2014 crashing". (see my NEW profile computer specs as of two weeks ago)
I've been experiencing about 25 crashes in an 8 hour period. Some after 1/2 hour and others back to back crashes.
I didn't even think of why it was crashing until I called support, whereas they took over my computer and showed me that even when timeline is PAUSED, YES EVEN JUST PAUSED, we watched the RAM clime and clime to the ceiling until Premiere crashed.
It's so frigg'in frustrating that people here are complaining and there seem to be absolutely no talk about this issue. It's probably the cause of many Premiere issues, in my humble opinion.
Strangely enough, the tech fixed the problem (but this has been happening to me often and even with my older computer). Anyway he stopped several Adobe related running programs in the background, and took my timeline to a new project.
Basically, I'm not sure exactly what he did to solve the problem, and sadly I suspect it will return as it always has done so.
One strange note is that he reset all my preferences back to the defaults. I'm talking about maybe 15 presets that I have including a handful of changed key-strokes (to my liking), and simple things like "double-click opens in same folder" and "don't replay timeline after rendering" and "don't go to beginning of project after end of play-line" and changed around my user interphase to my liking.
These type of customization shouldn't cause Memory Leaks? I just don't get it. -
Can I locate "memory leaks" to keep apps from crashing?
Hello clever people,
Since the iPhone 4s is still on the market, I assume that my 2 year old 4s should be able to work fine. However, I am constantly plagued by apps crashing and, most frustratingly, apps often fail to remain running in the background, even with one or no other apps running.
I had a similar issue with my iPad2, just before it ran out of applecare, and the chap had me run through with sending anaylitcs to him, and his conclusion was that a few apps were causing 'memory leaks' - had me reset the iPad and reinstall everything. So I also did this on the iPhone, which did help, but it has not solved the issue. I have also removed most apps from the device, in a bid to locate the offending app.
Searching on Google for "memory leak" only brings up info for developers, and nothing for someone who is actually using their phone and having issues. My usual scenario is going for a bike ride and running Strava, which then cuts out when I stop to take a picture - with no other apps running.
Does anyone know how to solve the issue - return the phone to its 'as new' state, or locate the problem and remove it?
Cheers,
TobiasThere are differenty types of, "resets" ..
Have you tried the folloiwng ??
Reset the device:
Press and hold the Sleep/Wake button and the Home button together for at least ten seconds, until the Apple logo appears.
If that doesn't help, tap Settings > General > Reset > Reset All Settings
No data is lost due to a reset.
Use iTunes to restore your iOS device to factory settings -
Version 7.3 memory leaks Windows 8 then crashes
Hello, There are already some threads about this, but they mention Windows 7. I can confirm the memory leak (it gets up to 1.5 gb then crashes) is happening on windows 8 and windows 8.1. This issue wasn't present for skype 7.2.0.103 , it is present for 7.3 and also for 7.4.0.102 . It leaks for about 0.6MB per second , it constantly writes to disk 0.3 MB/S and uses ~12% CPU. This behavior happens only after I'm logged in. No calls, no messages, just staying logged in is sufficient. Furhtermore, the memory leaked by Skype is not returning to the system, so I end up having 75% memory used on a 16 GB machine after restarting skype several times (because it crashes and I need skype to communicate with my contacts constantly). Please provide me with a link to download 7.2 (since it works). I had this issue with Skype 7.3 and in 7.4 nothing got solved, so please give me a link to something that works rather that something that's shiny but broken. Thank you
The memory leak is still occuring in 7.6.0+.
Downgraded to 7.2.0.103 and it still does not prevent memory leak. Eventually it crashes around 1100MB of RAM usage on my system. Validated everything is working like directx, etc. I think this is a Microsoft Windows 8.1 bug, and not just a Skype memory leak issue, as I have seen one other application do the exact same thing (grow to 1100MB and crash). Time to go bug Microsoft for a solution... oh wait... Skype is a Microsoft product. -
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 2400Frank 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 -
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. -
Help needed: Memory leak causing system crashing...
Hello guys,
As helped and suggested by Ben and Guenter, I am opening a new post in order to get help from more people here. A little background first...
We are doing LabView DAQ using a cDAQ9714 module (with AI card 9203 and AO card 9265) at a customer site. We run the excutable on a NI PC (PPC-2115) and had a couples of times (3 so far) that the PC just gone freeze (which is back to normal after a rebooting). After monitor the code running on my own PC for 2 days, I noticed there is a memory leak (memory usage increased 6% after one day run). Now the question is, where the leak is???
As a newbee in LabView, I tried to figure it out by myself, but not very sucessful so far. So I think it's probably better to post my code here so you experts can help me with some suggestions. (Ben, I also attached the block diagram in PDF for you) Please forgive me that my code is not written in good manner - I'm not really a trained programmer but more like a self-educated user. I put all the sequence structures in flat as I think this might be easier to read, which makes it quite wide, really wide.
This is the only VI for my program. Basically what I am doing is the following:
1. Initialization of all parameters
2. Read seven 4-20mA current inputs from the 9203 card
3. Process the raw data and calculate the "corrected" values (I used a few formula nodes)
4. Output 7 4-20mA current via 9265 card (then to customer's DCS)
5. Data collection/calculation/outputing are done in a big while loop. I set wait time as 5 secs to save cpu some jucie
6. There is a configuration file I read/save every cycle in case system reboot. Also I do data logging to a file (every 10min by default).
7. Some other small things like local display and stuff.
Again I know my code probably in a mess and hard to read to you guys, but I truely appreciate any comments you provide! Thanks in advance!
Rgds,
Harry
Attachments:
Debug-Harry_0921.vi 379 KB
Debug-Harry_0921 BD.pdf 842 KBWell, I'll at least give you points for neatness. However, that is about it.
I didn't really look through all of your logic but I would highly recommend that you check out the examples for implementing state machines. Your application suffers greatly in that once you start you basically jumped off the cliff. There is no way to alter your flow. Once in the sequence structure you MUST execute every frame. If you use a state machine architecture you can take advantage of shift registers and eliminate most of your local variables. You will also be able to stop execution if necessary such as a user abort or an error. Definitely look at using subVIs. Try to avoid implementing most of your program in formula nodes. You have basically written most of your processing there. While formula nodes are easier for very complex equations most of what you have can easily be done in native LabVIEW code. Also if you create subVIs you can iterate over the data sets. You don't need to duplicate the code for every data set.
I tell this to new folks all the time. Take some time to get comfortable with data flow programming. It is a different paradigm than sequential text based languages but once you learn it it is extremely powerful. All your data flow to control execution rather than relying on the sequence frame structure. A state machine will also help quite a bit.
Mark Yedinak
"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot -
MacBook crashing every so often with a some sort of memory leak? Need help to pinpoint cause.
I've only owned this Macbook for about 4 months now and it has started giving me this save memory leak issue every so often. I am not 100% sure if this is the proper place to post this kind of stuff, but I've tried to uninstall some things that I've added in the last month (which is when it started). No luck.
Can anyone tell what it might be just by looking?
Error Report
Anonymous UUID: 69F44AA1-027D-B2A4-9036-9DF6EBE5D770
Thu Jan 1 22:53:52 2015
*** Panic Report ***
panic(cpu 2 caller 0xffffff8022b79085): "zalloc: zone map exhausted while allocating from zone kalloc.8192, likely due to memory leak in zone kalloc.64 (1112477184 total bytes, 17382449 elements allocated)"@/SourceCache/xnu/xnu-2782.1.97/osfmk/kern/zalloc.c:2521
Backtrace (CPU 2), Frame : Return Address
0xffffff80bbd7bc00 : 0xffffff8022b3a811
0xffffff80bbd7bc80 : 0xffffff8022b79085
0xffffff80bbd7bdb0 : 0xffffff8022b42ef1
0xffffff80bbd7bde0 : 0xffffff8022b22a90
0xffffff80bbd7be10 : 0xffffff8022b3e8b7
0xffffff80bbd7be40 : 0xffffff8022b235a3
0xffffff80bbd7be90 : 0xffffff8022b33e8d
0xffffff80bbd7bf10 : 0xffffff8022c0a142
0xffffff80bbd7bfb0 : 0xffffff8022c3ac66
BSD process name corresponding to current thread: WindowServer
Mac OS version:
14B25
Kernel version:
Darwin Kernel Version 14.0.0: Fri Sep 19 00:26:44 PDT 2014; root:xnu-2782.1.97~2/RELEASE_X86_64
Kernel UUID: 89E10306-BC78-3A3B-955C-7C4922577E61
Kernel slide: 0x0000000022800000
Kernel text base: 0xffffff8022a00000
__HIB text base: 0xffffff8022900000
System model name: MacBookPro9,2 (Mac-6F01561E16C75D06)
System uptime in nanoseconds: 182760011229369
vm objects:24524880
vm object hash entri:3801640
VM map entries:5061280
pv_list:19697664
vm pages:64337216
kalloc.16:91921984
kalloc.32:130084416
kalloc.64:1112477184
kalloc.128:9461760
kalloc.256:7639040
kalloc.512:49831936
kalloc.1024:4407296
kalloc.2048:3215360
kalloc.4096:10162176
kalloc.8192:6324224
mem_obj_control:1522048
ipc ports:3965600
threads:1624696
vnodes:15977280
namecache:5540640
HFS node:21820528
HFS fork:7712768
cluster_write:2037072
decmpfs_cnode:1866816
buf.8192:10346496
ubc_info zone:5286864
vnode pager structur:2395720
compressor_pager:2375680
compressor_segment:4024080
Kernel Stacks:3604480
PageTables:155758592
Kalloc.Large:19787177
Backtrace suspected of leaking: (outstanding bytes: 21440)
0xffffff8022b79486
0xffffff8022b42ef1
0xffffff802305e513
0xffffff802307ada1
0xffffff80230b665e
0xffffff802305d01e
0xffffff802305d1e7
0xffffff80230b05c5
0xffffff80230b6dd0
0xffffff7fa35a3cc4
0xffffff7fa359eb0c
Kernel Extensions in backtrace:
com.razer.common.razerhid(10.57)[91AF82D9-68E7-3D2F-9D29-31113DBA21EE]@0xffffff 7fa3599000->0xffffff7fa35b1fff
dependency: com.apple.iokit.IOUSBFamily(705.4.14)[E15E9DC8-410F-3612-8371-E5FECD939E0D]@0xf fffff7fa3316000
dependency: com.apple.iokit.IOHIDFamily(2.0.0)[917971EF-5947-3DF5-BB9F-D353D05C0484]@0xffff ff7fa3431000
dependency: com.apple.iokit.IOUSBHIDDriver(705.4.0)[2CB055E6-0535-39A2-A393-F8FECDA6863B]@0 xffffff7fa34bb000
dependency: com.apple.driver.IOBluetoothHIDDriver(4.3.1f2)[12CE576E-DC6B-3F99-A180-909E93DA F5C3]@0xffffff7fa3585000
last loaded kext at 168541610122784: com.apple.driver.AppleUSBCDC 4.2.2b5 (addr 0xffffff7fa53cd000, size 20480)
last unloaded kext at 168658428597842: com.apple.driver.AppleUSBCDC 4.2.2b5 (addr 0xffffff7fa53cd000, size 16384)
loaded kexts:
org.virtualbox.kext.VBoxNetAdp 4.3.18
org.virtualbox.kext.VBoxNetFlt 4.3.18
org.virtualbox.kext.VBoxUSB 4.3.18
org.virtualbox.kext.VBoxDrv 4.3.18
com.razer.common.razerhid 10.57
com.apple.filesystems.smbfs 3.0.0
com.apple.driver.AudioAUUC 1.70
com.apple.filesystems.autofs 3.0
com.apple.iokit.IOBluetoothSerialManager 4.3.1f2
com.apple.driver.AGPM 100.14.37
com.apple.driver.X86PlatformShim 1.0.0
com.apple.driver.AppleOSXWatchdog 1
com.apple.driver.AppleMikeyHIDDriver 124
com.apple.driver.AppleHDA 267.0
com.apple.driver.AppleMikeyDriver 267.0
com.apple.iokit.IOUserEthernet 1.0.1
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.driver.AppleSMCPDRC 1.0.0
com.apple.driver.AppleSMCLMU 2.0.4d1
com.apple.driver.AppleHWAccess 1
com.apple.driver.AppleHV 1
com.apple.driver.AppleUpstreamUserClient 3.6.1
com.apple.driver.AppleThunderboltIP 2.0.2
com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport 4.3.1f2
com.apple.driver.AppleBacklight 170.4.12
com.apple.driver.AppleMCCSControl 1.2.10
com.apple.driver.AppleLPC 1.7.3
com.apple.driver.AppleIntelHD4000Graphics 10.0.0
com.apple.driver.AppleIntelFramebufferCapri 10.0.0
com.apple.driver.SMCMotionSensor 3.0.4d1
com.apple.driver.AppleUSBTCButtons 240.2
com.apple.driver.AppleUSBTCKeyboard 240.2
com.apple.driver.AppleIRController 327.5
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
com.apple.BootCache 35
com.apple.iokit.SCSITaskUserClient 3.7.0
com.apple.driver.XsanFilter 404
com.apple.iokit.IOAHCIBlockStorage 2.6.5
com.apple.driver.AirPort.Brcm4360 901.19.10
com.apple.driver.AppleUSBHub 705.4.1
com.apple.driver.AppleSDXC 1.6.5
com.apple.iokit.AppleBCM5701Ethernet 10.1.2b3
com.apple.driver.AppleFWOHCI 5.5.2
com.apple.driver.AppleAHCIPort 3.0.7
com.apple.driver.AppleUSBXHCI 705.4.14
com.apple.driver.AppleUSBEHCI 705.4.14
com.apple.driver.AppleSmartBatteryManager 161.0.0
com.apple.driver.AppleACPIButtons 3.1
com.apple.driver.AppleRTC 2.0
com.apple.driver.AppleHPET 1.8
com.apple.driver.AppleSMBIOS 2.1
com.apple.driver.AppleACPIEC 3.1
com.apple.driver.AppleAPIC 1.7
com.apple.driver.AppleIntelCPUPowerManagementClient 218.0.0
com.apple.nke.applicationfirewall 161
com.apple.security.quarantine 3
com.apple.security.TMSafetyNet 8
com.apple.driver.AppleIntelCPUPowerManagement 218.0.0
com.apple.kext.triggers 1.0
com.apple.iokit.IOSerialFamily 11
com.apple.driver.DspFuncLib 267.0
com.apple.kext.OSvKernDSPLib 1.15
com.apple.iokit.IOAudioFamily 200.6
com.apple.vecLib.kext 1.2.0
com.apple.driver.AppleSMBusPCI 1.0.12d1
com.apple.iokit.IOFireWireIP 2.2.6
com.apple.driver.X86PlatformPlugin 1.0.0
com.apple.driver.AppleHDAController 267.0
com.apple.iokit.IOHDAFamily 267.0
com.apple.iokit.IOBluetoothHostControllerUSBTransport 4.3.1f2
com.apple.driver.AppleBacklightExpert 1.1.0
com.apple.driver.AppleSMBusController 1.0.13d1
com.apple.iokit.IOUSBUserClient 705.4.0
com.apple.driver.IOPlatformPluginFamily 5.8.0d49
com.apple.iokit.IOSurface 97
com.apple.iokit.IONDRVSupport 2.4.1
com.apple.iokit.IOAcceleratorFamily2 156.4
com.apple.AppleGraphicsDeviceControl 3.7.21
com.apple.iokit.IOGraphicsFamily 2.4.1
com.apple.driver.AppleSMC 3.1.9
com.apple.driver.IOBluetoothHIDDriver 4.3.1f2
com.apple.iokit.IOBluetoothFamily 4.3.1f2
com.apple.driver.AppleUSBMultitouch 245.2
com.apple.iokit.IOUSBHIDDriver 705.4.0
com.apple.driver.AppleUSBMergeNub 705.4.0
com.apple.driver.AppleUSBComposite 705.4.9
com.apple.driver.CoreStorage 471
com.apple.iokit.IOSCSIMultimediaCommandsDevice 3.7.0
com.apple.iokit.IOBDStorageFamily 1.7
com.apple.iokit.IODVDStorageFamily 1.7.1
com.apple.iokit.IOCDStorageFamily 1.7.1
com.apple.driver.AppleThunderboltDPInAdapter 4.0.6
com.apple.driver.AppleThunderboltDPAdapterFamily 4.0.6
com.apple.driver.AppleThunderboltPCIDownAdapter 2.0.2
com.apple.iokit.IOAHCISerialATAPI 2.6.1
com.apple.iokit.IOSCSIArchitectureModelFamily 3.7.0
com.apple.driver.AppleThunderboltNHI 3.1.7
com.apple.iokit.IOThunderboltFamily 4.2.1
com.apple.iokit.IO80211Family 700.52
com.apple.iokit.IOEthernetAVBController 1.0.3b3
com.apple.driver.mDNSOffloadUserClient 1.0.1b8
com.apple.iokit.IONetworkingFamily 3.2
com.apple.iokit.IOFireWireFamily 4.5.6
com.apple.iokit.IOAHCIFamily 2.7.0
com.apple.iokit.IOUSBFamily 705.4.14
com.apple.driver.AppleEFINVRAM 2.0
com.apple.driver.AppleEFIRuntime 2.0
com.apple.iokit.IOHIDFamily 2.0.0
com.apple.iokit.IOSMBusFamily 1.1
com.apple.security.sandbox 300.0
com.apple.kext.AppleMatch 1.0.0d1
com.apple.driver.AppleKeyStore 2
com.apple.driver.AppleMobileFileIntegrity 1.0.5
com.apple.driver.AppleCredentialManager 1.0
com.apple.driver.DiskImages 389.1
com.apple.iokit.IOStorageFamily 2.0
com.apple.iokit.IOReportFamily 31
com.apple.driver.AppleFDEKeyStore 28.30
com.apple.driver.AppleACPIPlatform 3.1
com.apple.iokit.IOPCIFamily 2.9
com.apple.iokit.IOACPIFamily 1.4
com.apple.kec.Libm 1
com.apple.kec.pthread 1
com.apple.kec.corecrypto 1.0
Model: MacBookPro9,2, BootROM MBP91.00D3.B09, 2 processors, Intel Core i5, 2.5 GHz, 4 GB, SMC 2.2f44
Graphics: Intel HD Graphics 4000, Intel HD Graphics 4000, Built-In
Memory Module: BANK 0/DIMM0, 2 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54343235533641465236412D50422020
Memory Module: BANK 1/DIMM0, 2 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54343235533641465236412D50422020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xF5), Broadcom BCM43xx 1.0 (7.15.124.12.10)
Bluetooth: Version 4.3.1f2 15015, 3 services, 19 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en1
Serial ATA Device: Samsung SSD 840 EVO 250GB, 250.06 GB
Serial ATA Device: HL-DT-ST DVDRW GS41N
USB Device: Hub
USB Device: Hub
USB Device: Razer DeathStalker
USB Device: Razer DeathAdder
USB Device: Hub
USB Device: Apple Internal Keyboard / Trackpad
USB Device: BRCM20702 Hub
USB Device: Bluetooth USB Host Controller
USB Device: IR Receiver
USB Device: Hub
USB Device: FaceTime HD Camera (Built-in)
Thunderbolt Bus: MacBook Pro, Apple Inc., 25.1I'm sorry to have conveyed that impression. I do very much like EtreCheck, but it is completely misused by too many people who seem to think it's the answer to all problems. If is excellent for what it does. I helped beta test it for the developer. But it's a tool best used when a helper specifically asks for it when it is needed. That isn't for kernel panics. It may well be that some software can cause the panic, but the panic itself is generally in hardware. You can see that in the first few lines of the report. I urge you to learn more about them:
Mac OS X- How to log a kernel panic
OS X- About kernel panics
Technical Note TN2063- Understanding and Debugging Kernel Panics
Tutorial - Avoiding and eliminating Kernel panic
What's a "kernel panic"? (Mac OS X)
OSXFAQ - Troubleshooting Kernel Panics
Visit The XLab FAQs and read the FAQ on diagnosing kernel panics.
You will find a wealth of information about panics in the above references. There are many panic reports that simply don't give us any clues as to their root cause. They can be frustrating to deal with. But when someone is having a kernel panic EtreCheck is simply not the tool you whip out first or even second.
Good luck learning and a Happy New Year. -
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 (<, &qt;, >). 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. -
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,
Al7 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
Maybe you are looking for
-
A suggestion for the next upgrade.
When I want to separate my iPod I of course select the "eject" on the screen. However there are times when I just want to eject and keep the iPod connected (recharging, seeing what's on the iPod since the new upgrade took that away, listen to my tune
-
Report Painter Library: troubles with new field in the additional structure
Hi, ALL! I'm creating a new field in the Report Painter table GLFUNCT. Do do it I created my field in the additional structure GLDBZ for GLFUNCT and create an row in the T804C table for new field. Who has expirience in customizing using T804* tabl
-
Can't find DAQmx Create Task.vi and lots of other VI's
Hello, I have the problem that appears in the subject. I have the LabView2012 version on my computer, and I also downloaded and installed the NI-DAQmx9.4 but I can't run the project correctly because of those missing VI's. Please, any help is much a
-
Webdynpro application automatic start after j2ee startup
Hi , Is there a way to automatically start any specific webdynpro applications after j2ee startup Oren
-
2 Switches - 2 Routers - 2 ISP , I need to configure auto failover
Hello, I need a help please. I have 2 switches connected to 2 Routers and then 2 different ISPs. SW -----> Router(1) -----> ISP (Main) || || SW -----> Router -----> ISP (secondary) on R1 I did this: interface GigabitEthernet0/2