LabVIEW memory management changes in 2009-2011?

I'm upgrading a project that was running in LV8.6. As part of this, I need to import a custoemr database and fix it. The DB has no relationships in it, and the new software does, so I import the old DB and create the relationships, fixing any broken ones, and writ eot the new DB.
I started getting memeory crashes on the program, so started looking at Task manager. The LabVIEW 8.6 code on my machine will peak at 630MB of memory when the databse is fully loaded. in LabVIEW 2011, it varies. The lowest I have gotten it is 1.2GB, but it will go up to 1.5GB and crash. I tried LV 2010 and LV 2009 and see the same behavior.
I thought it may be the DB toolkit, as it looks like it had some changes made to it after 8.6, but that wasn't it (I copied the LV8.6 version into 2011 and saw the same problems). I'm pretty sure it is now a difference in how LabVIEW is handling memory in these subVIs. I modified the code to still do the DB SELECTS, but do nothing with the data, and there is still a huge difference in memory usage.
I have started dropping memory deallocation VIs into the subVIs and that is helping, but I still cannot get back to the LV 8.6 numbers. The biggest savings was by dropping one in the DB toolkit's fetch subVI.
What changed in LabVIEW 2009 to cause this change in memory handling? Is there a way to address it?

I created a couple of VIs which will demonstrate the issue.
For Memory Test 1, here's the memory (according to Task Manager):
Pre-run
Run 1
Run 2
Run 3
LabVIEW 8.6
55504
246060
248900
248900
LabVIEW 2011
93120
705408
1101260
1101260
This gives me the relative memory increase of:
Delta Run 1
Delta Run 2
Delta Run 3
LabVIEW 8.6
190556
193396
193396
LabVIEW 2011
612288
1008140
1008140
For Memory Test 2, it's the same except drop the array of variants:
Pre-run
Run 1
Run 2
Run 3
LabVIEW 8.6
57244
89864
92060
92060
LabVIEW 2011
90432
612348
617872
621852
This gives us delats of:
Delta Run 1
Delta Run 2
Delta Run 3
LabVIEW 8.6
32620
34816
34816
LabVIEW 2011
521916
527440
531420
What I found interesting in Memory Test #1 was that LabVIEW used more memory for the second run in LV2011 before it stopped. I started with Test 1 because it more resembled what the DB toolkit was doing since it passes out variants that I then convert. I htought maybe LabVIEW didn't store variants internally the same any more. I dropped the indicator thinking it would make a huge difference in Memory Test 2, and it didn't make a huge difference.
So what is happening? I see similar behaviore in LV2009 and LV2010. LV2009 was the worst (significantly), LV2010 was slightly better than 2011, but still siginificantly worse than 8.6.
Pre-run
Run 1
Run 2
Run 3
LabVIEW 8.6
55504
246060
248900
248900
LabVIEW 2011
93120
705408
1101260
1101260
Attachments:
Memory Test.vi ‏8 KB
Memory Test2.vi ‏8 KB

Similar Messages

Memory Management in LabView / DLL

Hi all,
I have a problem concerning the memory management of LabView. If my data is bigger than 1 GB, LabView crashes with an error message "Out of Memory" (As LabView passes Data only by value and not by reference, 1 GB can be easily achieved). My idee is to divide the data structure into smaller structures and stream them from Hard Disk as they are needed. To do so, i have to get access to a DLL which reads this data from disk. As a hard disk is very slow in comparison to RAM, the LabView program gets very slow.
Another approach was to allocate memory in the DLL and pass the pointer back to LabView...like creating a Ramdisk and reading the data from this disk. But memory is allocated in the context of Labview...so LabView crashes because the memory was corrupted by C++. Allocating memory with LabView-h-Files included doesnt help because memory is still allocated in the LabView context. So does anybody know if it's possible to allocate memory in a C++-DLL outside the LabView context, so that i can read my Data with a DLL by passing the pointer to this DLL by LabView? It should work the following way:
-Start LabView program--> allocate an amount of memory for the data, get pointer back to labview
-Work with the program and the data. If some data is needed, a DLL reads from the memory space the pointer is pointing at
-Stop LabView program-->Memory is freed
Remember: The data structure should be used like a global variable in a DLL or like a ramdisk!
Hope you can understand my problem
Thanks in advance
Christian
THINK G!! ;-)
Using LabView 2010 and 2011 on Mac and Win
Programming in Microsoft Visual C++ (Win), XCode (Mac)

If you have multiple subvis grabbing 200MB each you might try using the "Request Deallocation" function so that once a vi is done processing it releases the memory.
LabVIEW Help: "When a top-level VI calls a subVI, LabVIEW allocates a data space
of memory in which that subVI runs. When the subVI finishes running, LabVIEW
usually does not deallocate the data space until the top-level VI finishes
running or until the entire application stops, which can result in out-of-memory
conditions and degradation of performance. Use this function to deallocate the
data space immediately after the VI completes execution."
Programming >> Application Control >> Memory Control >> Request Deallocation
I think it first appeared in LabVIEW 7.1.
Message Edited by Troy K on 07-14-2008 09:36 AM
Troy
CLDEach snowflake in an avalanche pleads not guilty. - Stanislaw J. Lec
I haven't failed, I've found 10,000 ways that don't work - Thomas Edison
Beware of the man who won't be bothered with details. - William Feather
The greatest of faults is to be conscious of none. - Thomas Carlyle

Resizing an array of struct inside a DLL using the memory manager

Hi all,
I dug deep inside the boards, but wasn't able to find a solution for my problem.
I'm building a dll, which does some imageprocessing and should return an array of structs to labview, with one struct for every element in the image.
As I don't know the number of elements beforehand and the limit of the number is numbers of magnitude larger then the expected one, I don't want to allocate such a huge chunk of memory prior to the dll call in labview.
In a former version I used a 2d array for the elements, where each row holds the values of every element. Here I used the NumericArrayResize-function, which worked quite well. But I have to add more sub-processes and using structs (or clusters in labview) appears to be more usefull and cleaner for me, in addition I had to cast some of the elements back and foreward a few times.
So one element-struct should hold 2 singles and 1 uint32. My question is now, how can I resize this array of struct with memory manager functions as the NumericArrayResize-functions does not suit this purpose?
(Accessing a given array of structs inside the DLL and after that reading the changed values in Labview is surprisingly easy )
Thanks in advance
Solved!
Go to Solution.

Well, I was able to solve it myself. I found this thread, where the first post of rolfk made me thinking. It appeared to me, that the numericarrayresize-function behaves very similar to the realloc-function of c. So I used the type unsigned int 8 (which is just one byte) and multiplied it by the number of bytes used by one struct, in my case 12 bytes (4+4+4) and then multiplied it by the number of structs (elements in the image) i have. Luckily it worked and the memory block was resized exactly as I wanted it to be. Important to note: do not forget to adjust the size element of the handle, otherwise Labview does not know about the changed size.

Memory manager.cppについて

いつもお世話になっております。
下記問題について、どなたかご存知でしたら教えて頂けないでしょうか。
VI編集中に致命的な内部エラーとして、「memory manager.cpp　ライン566」のダイアログが表示されます。
ブロックダイアグラム上で編集作業時、ショートカットキーの「Ctrl」+「Z」もしくは「Ctrl」+「S」を押した際に本エラーが頻発します。
その他の操作では出たことがありません。
ダイアログの内容からメモリに関するエラーなのだと察することはできますが、具体的な解決法がわかりません。
どなたかご存知でしょうか。
ちなみに、Windows7 HomePremium（64bit）にてLabVIEW2010を使用しております。
解決済！
解決策の投稿を見る。
添付:
ライン566.jpg ‏36 KB

haljion 様
平素より弊社製品をご利用頂きまして、誠にありがとうございます。
ご報告いただいた症状は、不特定の状況で生じるLabVIEW 2010の既知の不具合となっております。
積極的な解決策ではございませんが、この不具合の発生後、LabVIEWの再インストールをすることで改善された例が報告されています。
なお、この不具合は、LabVIEW 2011以降では修復がなされております。
この不具合ですが、不特定の状況で生じるものであるため、こちらで再現することが困難な次第です。
そこでお教えいただきたいのですが、この不具合はどのようなタイミングから発生するようになったのでしょうか。
また、特定のVIの編集を行っている際のみ発生するもの、もしくは、編集するVIに依らず発生するもののいずれでしょうか。
日本NI 早田

Fatal Internal Error: "Memory Manager.cpp", line 547

Hello,
I am using LV 2009 and I am also getting an error as follows:
=======================================================
Fatal Internal Error: "Memory Manager.cpp", line 547
LabVIEW version 9.0.1
You will lose any unsaved work. For assistance in resolving this problem, please relaunch LabVIEW, or contact National Instruments.
=======================================================
I get this error when I start executing steps on TS 4.2.1 as well as when I do "Unload All Modules" in TS. Please find the attched logs. Further, I could not run anything in TS and need to restart the PC to re-run the sequence after everytime this error occurs.
We have transited through LV 8.0, 8.2, 8.5 and now 2009 over past 4 years for our project and this is the first time I could see this error.
Please help.
Thanks.
Attachments:
lvlog2010-06-09-10-06-07.txt ‏2 KB
lvlog2010-06-09-18-52-36.txt ‏1 KB
lvlog2010-06-09-19-16-20.txt ‏2 KB

Adding on to Pritam's post:
For the earlier "Fatal Internal Error: "Memory Manager.cpp", line 547" , we found that a couple of our dll's which were developed in LV 8.5.1 had not been recompiled in LV2009. After recompiling each of them in LV2009, and then running the same sequences in TestStand,this error vanished.
But now again we're seeing this error, and that too only on 3 PCs systems out of 5 PCs!
The same installer has been installed on all 5 sytems (after removing the earlier installers and running MSI Blast.exe them).
The error now appears again, only when we try to exit TestExec.exe and another tool built in LabVIEW.
So everything works fine and tasks are performed,etc, but when we close the window or try the exit that program, the "Fatal Internal Error: "Memory Manager.cpp", line 547" pops up.
If we say "OK" to it, the window closes, but the Task is seen still running in the Task Manager and has to be manually terminated (End Task).
Does anyone know what could be going wrong?

How does object memory management works?

Hi all,
I'm having a lot of problems with memory which seems not to be released when using objects (on Oracle 9i 9.0.1.1.1). I've prepared the following test:
create type t_test as object (
id number,
member function FunctTest(TBL IN CHAR, expand IN CHAR) return varchar2
) not final;
create or replace type body t_test as
MEMBER FUNCTION FunctTest(TBL IN CHAR, expand IN CHAR) RETURN varchar2 IS
BEGIN
return NULL;
END FunctTest;
end;
create or replace function FunctTest2(TBL IN CHAR, expand IN CHAR) RETURN varchar2 IS
BEGIN
return NULL;
END FunctTest2;
create table tab_test of t_test;
insert into tab_test values(1);
commit;
As you can see, I create a simple type with a member function, and a schema function who does the same (nothing, in this case). Then I call the two functions with the following PL/SQL blocks:
declare i integer;
t varchar2(4000);
ob t_test;
begin
select value(a) into ob from tab_test a where a.id=1;
for i in 1..5000 loop
select ob.FunctTest('A','S') into t from dual;
end loop;
end;
declare i integer;
t varchar2(4000);
begin
for i in 1..5000 loop
select FunctTest2('A','S') into t from dual;
end loop;
end;
If you run these blocks with Task Manager opened (I use W2000) on server console, you can see how memory usage grows very fast with the first block, and how it doesn't change with the second one.
The memory isn't released till the session is alive.
I'm trying to develop an object application, but these memory leaks are making me crazy.
Geoff, does release 2 solve some of these problems?
In particular, please, do I need to free by myself temporary objects (these ones referenced in PL/SQL blocks)? In which way? I haven't found anything about object memory management in documentation...
As always,
Thanks for any support to everybody.
Andrea Arilotta
[email protected]

Andrea,
Do you have an Oracle Support customer ID? If you can log a TAR on http://metalink.oracle.com with your customer id, someone can take a closer look at this problem.
Regards,
Geoff
Hi all,
I'm having a lot of problems with memory which seems not to be released when using objects (on Oracle 9i 9.0.1.1.1). I've prepared the following test:
create type t_test as object (
id number,
member function FunctTest(TBL IN CHAR, expand IN CHAR) return varchar2
) not final;
create or replace type body t_test as
MEMBER FUNCTION FunctTest(TBL IN CHAR, expand IN CHAR) RETURN varchar2 IS
BEGIN
return NULL;
END FunctTest;
end;
create or replace function FunctTest2(TBL IN CHAR, expand IN CHAR) RETURN varchar2 IS
BEGIN
return NULL;
END FunctTest2;
create table tab_test of t_test;
insert into tab_test values(1);
commit;
As you can see, I create a simple type with a member function, and a schema function who does the same (nothing, in this case). Then I call the two functions with the following PL/SQL blocks:
declare i integer;
t varchar2(4000);
ob t_test;
begin
select value(a) into ob from tab_test a where a.id=1;
for i in 1..5000 loop
select ob.FunctTest('A','S') into t from dual;
end loop;
end;
declare i integer;
t varchar2(4000);
begin
for i in 1..5000 loop
select FunctTest2('A','S') into t from dual;
end loop;
end;
If you run these blocks with Task Manager opened (I use W2000) on server console, you can see how memory usage grows very fast with the first block, and how it doesn't change with the second one.
The memory isn't released till the session is alive.
I'm trying to develop an object application, but these memory leaks are making me crazy.
Geoff, does release 2 solve some of these problems?
In particular, please, do I need to free by myself temporary objects (these ones referenced in PL/SQL blocks)? In which way? I haven't found anything about object memory management in documentation...
As always,
Thanks for any support to everybody.
Andrea Arilotta
[email protected]

Oracle 9i Automatic PGA Memory Management

Hello,
my team and me, we are facing difficulties to change the size of the PGA used by our server processes for HASH JOIN, SORT... operators,
here you can see the results of "select * from v$pgastat":
[pgastat dynamic view results|http://pastebin.com/m210314dc]
We have been increasing consecutively our pga_aggregate_target parameter from 1.7 Gb initially to 4Gb then at the end 6Gb, the value of "Global memory bound" and " aggregate pga auto target" on the link above are still equal to 0.
I have been reading threads on the forum and documentation see below, I understand how the global memory manager (CKPT) computest the sql memory target and then the global memory bound, as far as I understand I can only "play" on the pga_aggregate_target value in order to increase the size of our PGAs (I exclude to play with hidden parameters).
- Joze Senegacnik: Advanced Management of working areas in Oracle 9i/10g : http://tonguc.yilmaz.googlepages.com/JozeSenegacnik-PGAMemoryManagementvO.zip
- Dageville Benoit and Zait Mohamed: SQL memory management in oracle 9i
Here different information that could be usefull:
OS: solaris 10 (db running in a non global zone)
Arch: 64-bit sparcv9 kernel modules
Physical memory: 32 Gb (being shared between all non global zones)
Oracle version: 9.2.0.5 32bits
Values of init parameters and hidden parameters that could be relevant:
[init parameters|http://pastebin.com/m40340cf4]
[hidden parameters|http://pastebin.com/m50d74c53]
Maybe useful queries:
over work areas views, I use the following script:
[wa_analysis.sql|http://pastebin.com/d606ebd9b]
and the result of it:
[result of script wa_analysis.sql|http://pastebin.com/m5f49a2e5]

Joze Senegacnik wrote:
- either your sessions are using a lot of memory for storing variables like pl/sql arrays which is subtracted from automatic management: PGA_AGGREGATE_TARGET - (aggregated persistent area + a part of the run time area of all server processes)
- you are hitting a bug
- or maybe something elseI am really happy you come to this conclusion too, they are the same we made with my team and we have submitting to Oracle support via metalink SR 3-1216060641, we were asking if we hit the following bug (in note 1) or we leak about pl/sql or java... or else indeed,
note 1: PGA_AGGREGATE_TARGET Assigned Memory Is Left Unconsumed When Set High [ID 844542.1]
Joze Senegacnik wrote:
I would like to know:
1.) what were the values for global memory bound and autotarget immediately (or in short time) after the database restart or when you have increased them Just after the restart of the database and just after the change of P_A_T, we query v$pgastat immediately after and the value of global memory bound and auto target were equal to 0 byte,
2.) If you are able to change value of PGA_AGGREGATE_TARGET (P_A_T) to 10GB what happens with global memory bound and auto traget. They should be positive at least for a short time. As this is a dynamic parameter you can change it for a short time, run queries and set it back.We plan to do this tonight, we have an "heavy" ITIL change management procedures that allow us to make changes approved by change manager and only during night maintenance window on production system, I come back to you tomorrow. But we have been increasing from 1,7Gb to 4Gb to 6Gb, each time I have been querying v$sgastat in the next 2 mins and global memory bound and auto target were equal to 0 byte.
3.) Have you checked on the OS level how much memory are using server processes - do these numbers come along with what Oracle says. Not during problematic activities, meaning active work areas performing HASH-JOIN, SORT... operators,
unfortunately it is a production system, even if he performs poorly, we are not allowed to try or retry the poor queries, but if it comes again I'll do it,
during low activities, here the results paste with the scripts I used:
[pga processes info in oracle|http://pastebin.com/f2e540062]
I spooled the result rows of this previous script in /var/tmp/pga_processes.log then I loop over all processes pid and display pmap output anon info like this:
h5. cat /var/tmp/pga_processes.log | awk -F' ' '{print $5}' | xargs -n 1 -i pmap -x {}| grep -v 'Addres' |egrep 'Kb' 2>&1 > /var/tmp/pga_processes_os.log
then I merge line by line the two files with unix paste command, here the results:
[os and oracle pga informations|http://pastebin.com/f4135c8a6]
4.) How many server processes are running on you system in average/max and are you using just dedicated processes or also shared?in average 250, we are only using dedicated processes,
5.) At time of low activity is the global memory bound still 0 or becomes > 0. I have been querying every 15 min during more than 24 hours low activities, it still stay to 0,
5.) Are you experiencing paging/swapping on OS level?No, here orca figures for details:
[free memory|http://img509.imageshack.us/img509/5897/ohuron1asd2gauge1024xfr.png]
swap
[pagein pageout|http://img121.imageshack.us/img121/6946/ohuron1asd2gaugepginper.png]
[memory usage|http://img19.imageshack.us/img19/2213/ohuron1asd2gaugeppkerne.png]
6.) Please post the result of: select * from X$QESMMSGA ;during low activities, [results X$QESMMSGA|http://pastebin.com/f61df7093]
While you will be answering to my questions I'll try to figure out what we can do to properly diagnose the problem. As you are on 9i it is a little bit harder.I am really kind of your help, as we say in my country, "if you need tow arms one day to carry something, call me."
--Jeremy Baumont

Oracle 11g AMM (Automatic Memory Management)

Hi All,
I have a very powerful server 24 Processors with 6 cores each and 74 GB RAM for my production database. The server will host only one production database. I wanted to use AMM for this database and allocate maximum memory to Oracle by setting memory_target. By default /dev/shm is set 37 GB but I wanted to increase it least 55 GB. I know I can get this changed by my system admin but I wanted to know how much memory should leave for OS?
Please help me on sizing this.
Thanks,
Arun Singh

From MOS ID 169706.1
Automatic Memory Management
Starting with Oracle Database 11g, the Automatic Memory Management feature requires more shared memory (/dev/shm) and file descriptors. The shared memory should be sized to be at least the greater of MEMORY_MAX_TARGET and MEMORY_TARGET for each Oracle instance on the computer. To determine the amount of shared memory available, enter the following command: # df -k /dev/shm/
Note: MEMORY_MAX_TARGET and MEMORY_TARGET cannot be used when LOCK_SGA is enabled or with huge pages on Linux

Using Dynamic Memory Management

Hi All,
http://technet.microsoft.com/en-us/library/ms178145(v=sql.90).aspx
I have red the above article regarding Dynamic Memory Management and now I just want to check whether this option is enabled in my environment or not.
Is this by default enabled in the server or else Please suggest on how to achieve this
Regards,
Kalyan
Grateful to your time and support. Regards, Shiva

Is this by default enabled in the server or else Please suggest on how to achieve this
Regards,
Kalyan
Grateful to your time and support. Regards, Shiva
If you read the first line of the link you posted its clearly written SQL Server memory management is dynamic. You cannot change it . You can just restrict buffer pool usage by puttling limit on MAX Server memory. In that case as well SQL Server might cache
all Buffer pool memory.
Event though you cap max server memory still direct memory allocations for large pages will be done directly by windows API and that will also come under SQL Server memory utilization
In short SQL server memory allocation is always dynamic you cannot change it
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles

Memory management in plugins using Cocoa

Hello,
In Obj-C memory management guide stated: "If you spawn a secondary thread, you must create your own autorelease pool as soon as the thread begins executing; otherwise, you will leak objects."
I assume that it also applies to Acrobat Plugins? What are the guidelines of using NSAutoreleasePools in plugins and is there any specific things in plugins' memory manamgement?

If you have multiple subvis grabbing 200MB each you might try using the "Request Deallocation" function so that once a vi is done processing it releases the memory.
LabVIEW Help: "When a top-level VI calls a subVI, LabVIEW allocates a data space
of memory in which that subVI runs. When the subVI finishes running, LabVIEW
usually does not deallocate the data space until the top-level VI finishes
running or until the entire application stops, which can result in out-of-memory
conditions and degradation of performance. Use this function to deallocate the
data space immediately after the VI completes execution."
Programming >> Application Control >> Memory Control >> Request Deallocation
I think it first appeared in LabVIEW 7.1.
Message Edited by Troy K on 07-14-2008 09:36 AM
Troy
CLDEach snowflake in an avalanche pleads not guilty. - Stanislaw J. Lec
I haven't failed, I've found 10,000 ways that don't work - Thomas Edison
Beware of the man who won't be bothered with details. - William Feather
The greatest of faults is to be conscious of none. - Thomas Carlyle

Memory management problem

hi everyone.
I m trying to use OpenCV in After Effects. The problem is that OpenCV has its own management of memory.
The AE memory management is kind of bound to the lock/unlock system for multi thread processing and is kind of difficult to use from openCV...
So, as long as you dont use multi processing, I thought that using openCV would not be a problem.
But I was wrong. I got a random error:
After Effects error: Effects modules should only dispose worlds they have allocated.
My effect is allocating a lot of opencv layers, and one temporary AE layer. When I dispose the AE temporary layer, I have some errors when the rendering get slow and the user tries to interrupt it. the "After Effects error: Effects modules should only dispose worlds they have allocated."
When looking at the layer before disposing it, It s totally corrupted with random values for all the field, but data field is not NULL.
I did not get any error during the memory allocation of the layer though. Still it gets corrupted at some point.
I m wondering if it is openCV memory and AE memory that get into conflict or if it s my way of checking if layer has not been correctly allocated that is wrong.
I dont understand also why it would conflict, since system will allocate the memory on demand, and there is no reason the system would give conflicting memory regions....
I solved my problem by stopping using the AE temporary layer.
If anyone experienced and solved this kind of problem, please, let me know.
Regards

hey marc,
I think you are overcomplicating things a little,
1) add a local variable of type PF_LayerDef (or allocate on heap); no
need to initialise anything
2) WorldSuite1()->new_world()
3) use the layer. use PF_GET_PIXEL_DATA8() to get pixels
4) WorldSuite1()->dispose_world() (optionally free a heap variable)
Am 28.07.2011 05:06, schrieb salvati marc:
I m back to this problem...
As always, Shachar, it seems you are right. I deactivated OpenCV code, and... still crashing.
I investigate the problem more in depth and found my mistakes...
What I was doing was:
1) allocating my tmp layer
2) copying source to tmp
3) processing with opencv
4) copying back to output
5) cleaning tmp layer
I did few mistakes:
1) I was checking tmpLayer->data == NULL to see if the tmp layer was right or not (in step 5). BUT, I copyed my source to tmp (step 2) even if it was not correctly allocated... I guess that s why when I check NULL before dispose it was not consistent
2) I did not always set the tmpLayer->data to NULL before allocation! default value is not NULL. So my check after allocation was not consistent in some case
So multiple reason of not getting a NULL data although the data where not allocated...
Like you said, ill supervised creating/disposing of worlds...
Anyways, I realized in my algorithm that i did not nid the tmp layer, and I could just use the output layer for that purpose... But i m sure i ll get this problem again in the near future, so I had to investigate that.
Thanks again for your precious help.
Regards.
>

Memory management in jelly bean xperia tablet s and performance issues

Most used apps are always in memory.
while recent apps few remain in memory untill memory is full.
this is how memory management is supose to work.
pretty much same as windows 7
but if this true then why are games lagging ?
http://www.youtube.com/watch?v=S3TwBlW5ibk
When their not enough memory games i suspect lagging.
if their not enough memory recent apps getting killed to free up ram.
why does't this happen ?
And why are their apps in memory that i never use ?
tv sideview never use why its in memory ?
social life again never use again using memory
reader widget again using ram again never use at all
music unlimited again in memory never actualy use
Like i say'd most used apps are in memory all the time while rest is in cache.
But my most used apps are never in ram untill i start them
now if disabled lot apps my tablet become much faster respondsive.
Can sony plz plz plz plz fix memory management stop saying you did ?
You maybe reduced random shutdowns by like 90% or 95% perhaps even 99.99%
Before random shutdowns happend because of broken memory management, which obviously still broken as i see lag in games
sony apps use way to much ram, stop treating it like a computer with infinity amount of ram

I rooted my tablet, and when looking at the processor speed in SetCPU, Sony uses a governor for power management that makes the tablet run jagged... I changed the power governor to ondemand, and got MUCH better smoothness and performance, while not sacrificing my battery life. You should try it out, maybe that'll help with games and such.

Memory management getting worse

So I've been using the same machine, working in the same file sized roughly 3k by 5k, making concept art for 2 years now, not much has changed in terms of how I worked over the years. Photoshop always hogs any extra memory I have on my machine, it like a memory leak. When I start working and load a file it's fine, as I work on the same file after a few hours Photoshop just takes over more and more of the system memory until it's all used up. It used to not cause problems, but now, especially the last few months I've been having to close the program, then end the photoshop.exe file in the task manager daily to clear the memory. Now it's getting to the point where I have to do it 2 or 3 times a day to keep my system from halting. It doesn't seem to matter how I set the memory usage of the program it just eventually takes up the rest of the free memory (16gb of it) over time. It feels like a memory leak. It's getting frustrating, and slowing me down at work. I see on the forum that it's a common issue. From my experience over the years Photoshop always hogs up the memory over time, would be nice to get this fixed.

We check Photoshop pretty closely for leaks, and fix them.
Photoshop should only allocate memory up to the limit you set in Preferences.
But bugs in drivers, the OS, or third party plugins can leak memory.
No, leaks in Photoshop are not a common issue. Misunderstandings of memory management, or the aforementioned third party issues are common.

Parameter configuration of memory management

Hi all,
I receive from SAP a Analysis Check that suggest me to modify some value parameter of Memory management.
SAP suggest me:
ztta/roll_area: 3000329(current value) ->    6500000(Recommended value)
rdisp/PG_SHM: 8192(current value) ->    16384(Recommended value)
ztta/short_area: 3200000(current value) ->   4000000(Recommended value)
My request is: Can I modify these parameters with value suggest by SAP in my environment?
Is there any documentation which explain some info?
This is the information of the productive system:
machinfo
CPU info:
12 Intel(R) Itanium 2 9000 series processors (1.6 GHz, 24 MB)
          533 MT/s bus, CPU version C2
          18 logical processors
Memory: 65339 MB (63.81 GB)
Firmware info:
   Firmware revision: 7.44
   FP SWA driver revision: 1.18
   IPMI is supported on this system.
   Invalid combination of manageability firmware has been installed on this system.
   Unable to provide accurate version information about manageability firmware
Platform info:
   Model:                  "ia64 hp superdome server SD64B"
   Machine ID number:      xxxxxx
   Machine serial number: xxxxxx
OS info:
   Nodename: hostaddress
   Release:   HP-UX B.11.31
   Version:   U (unlimited-user license)
   Machine:   ia64
   ID Number: xxxx
   vmunix releaseversion:
@(#) $Revision: vmunix:    B.11.31_LR FLAVOR=perf

Hi,
I am sure that SAP must have recommanded these values after analysing your system. So you can anytime go for these values and what is good is....if you face any problem in future with these sets of values suggested by SAP, you can anytime escalaye back to SAP.
Please do not forget to take the backup of your Instance profile before making any change. Always adjust the values for pool 10 and pool 40 othwerwise your instance may not come up.
For more details about these parameters, please refer to below link.
http://help.sap.com/saphelp_nw04/helpdata/en/02/962acd538111d1891b0000e8322f96/frameset.htm
With Regards,
Saurabh

4.2 seems to have vastly improved memory management

This may not be something most uses will notice, but by using the 'MemoryFree' app I have noticed that the upgrade to 4.2 leaves much more software free memory on my iPhone4 than 4.1. I would guess that this would tend to boost performance as well, but I haven't noticed any perceptible change there.

sn4p2k wrote:
im not updating to 4.2 and i have no problems with performance on 4.1
I don't really think you read what I posted!
I didn't say I had issues with 4.1 and they went away after I upgraded to 4.2. I just pointed out that there were obviously major improvements made between 4.1 and 4.2 'under the hood', and that this was demonstrated in part by the clear improvement in the memory management. I stressed that i had not noticed any perceptible difference, but that the improvements were obviously there.

LabVIEW memory management changes in 2009-2011?

Similar Messages

Maybe you are looking for