Execution stay in memory after exit

Hello everyone,
I've the program to do the following at the end of execution:
using the developer's suite I have no problem by exit, the program exit perfectly without staying in memory list.
After I build an exe and do the same to exit the exe program disappears from the task bar, however stays in the list of task management (Ctrl+Alt+Del).
In my program there's Network Streaming, CAN bus, and RS232.
How to exit the program completely without letting it stay in the memory?
Wilbur
Solved!
Go to Solution.

Hi,
here is a dummy code from the whole project. I've constructed the as many different subVIs and at the end the error handle part.
And the "Dummy.vi" is in the same position of my main.vi, which is the caller of the "Simple error saver.vi".
I've tested that the code run till the "Simple error saver.vi" but it doesn't exit from memory.
By the way, I've used the dynamic call VI to catch the .net event in my program!
Wilbur
Attachments:
Dummy.zip ‏29 KB

Similar Messages

Firefox process is left running in memory after exit

The firefox *32 process is left running in memory after exiting Firefox. You cannot restart firefox without either killing the process (ctrl-alt-del ...) or restarting the computer.
I am running Windows 7 pro 64bit and Firefox 6.0.2 swedish version.
I haven't had this kind of a problem with prior versions of Firefox.

Firefox is already running but is not responding
* https://support.mozilla.com/en-US/kb/Firefox%20is%20already%20running%20but%20is%20not%20responding
Profile in use
* http://kb.mozillazine.org/Profile_in_use
Check and tell if its working.

Menu "Application" Stays open even after "Exit"

Open the menu, click Exit (bottom right) - it will take you back to the Home Screen. Do a Show Open Applications. The Menu is still running.
Open the menu, click Options (bottom left) and then Exit - it will take you back to the Home Screen. Do a Show Open Applications. The Menu is not shown as running.
So the Exit command from the Options menu is not same as the direct Exit. Is this a Bug!

yeah, I noticed this too..also noticed that when you exit e-mails wiht the right exit button it returns you to home screen but the application still runs in backround, but when you exit throught the options than it really exits

LabVIEW as a Service - process stays in memory despite finishing execution

I have a fairly interesting/unique problem with trying to run a LabVIEW built executable as a service using srvstart (http://www.nick.rozanski.org.uk/services). Srvstart allows you run any application as a service (similar to srvany or firedaemon) but it has the advantage that when you shutdown the service, you can set it to send a WM_CLOSE message which can be picked up in LabVIEW using the Application Instance Close? filter event and shutdown the service gracefully without killing it (as is the case with srvany).
To debug this, I put a simple file write into the Application Instance Close? and Panel Close? events, my 'Exit' case and in a sequence structure at the very end of my application. If the application shuts down gracefully, a file will be created for at least the 'Exit' case and the the final file write.
When I run the application in the LabVIEW development environment or as a normal executable (by double clicking on the EXE), it shuts down gracefully (by queueing up an 'Exit' command and executing the 'Exit' case) when I close the front panel (which is just an empty front panel - no controls/indicators as it runs without a UI as a service) - it creates the files and the application closes (and the process in task manager disappears).
When I run the application and try to shut it down by using 'End Task' or run the application as a service. This should fire the Application Instance Close? filter event, which is then discarded (with silent shutdown) which will should queue up an 'Exit' command and shut down the software gracefully.
What actually happens is that If I'm running the EXE normally and I 'End Task', the front panel closes but the application process stays in the system (i.e. in task manager). None of the files are written so the application hasn't gracefully shutdown. I then have to kill the process in task manager.
When I'm running as a service and 'Stop' the service, the files for Application Instance Close?, my 'Exit' case and the last call get created, the memory usage goes from 30to 80mb and the process stays in memory (in task manager) - the service doesn't respond and I have to shut it down via task manager. I call 'Quit LabVIEW' right at the end of my VI, just after the last call file is created, if I disable this, the same thing happens but the memory usage doesn't go up. In both cases though, the service/application doesn't respond.
I have to be a little careful about what I post in terms of VIs/screenshots for IP reasons but I'll try to illustrate my setup:
In terms of other considerations, the VI does some asynchronous calls for handling TCP connections but these will finish execution when the main event queue is destroyed and the problem still occurs even if no TCP connections occur (and hence no calls are made to the asynchronous VI). I'm running LabVIEW 2011 SP1 on a Windows 7 64-bit.
I tried to use the Desktop Trace Execution toolkit to help debug the issue but it seems that the VI Server shuts down and doesn't show me any trace information after I tell the service to Stop.
The things I don't understand are:
- If I 'End Task' on the EXE, shouldn't that fire the Application Instance Close? filter event in LabVIEW? I understand that Windows would give a 'This application is not responding...' message if it then didn't shutdown or if I didn't discard the event but I don't understand why that event isn't being captured/discarded on my EXE.
- Why doesn't the process end when the VI has finished executing - even though I call the 'Quit LabVIEW' VI as the last call in my application?
- Finally, why does the memory usage go from 30mb to 83mb depending on whether or not I call the 'Quit LabVIEW' VI (but the process still stays in Task Manager)?
The key one is the second one - as this is the one that stops me from being able to stop/restart the service from 'Services'. I'd like to be able to use my 'Exit' case to try and send a last ditch 'Hey I'm shutting down now' message before the PC switches off by gracefully shutting down my service (and you know - because it's better to shutdown things in a controlled manner - hence the reason for using srvstart in the first place!)
If anyone can help shed some light on this I'd really appreciate it as I've been trying to debug this for a lot longer than I'd like and despite asking around a few people not been able to come to any sort of solution.
Certified LabVIEW Architect, Certified TestStand Developer
NI Days (and A&DF): 2010, 2011, 2013, 2014
NI Week: 2012, 2014
Knowledgeable in all things Giant Tetris and WebSockets

Since about LabVIEW 8.5 it is a very bad idea to add the Application Close? filter event and expect LabVIEW Quit to still do anything! It simply behaves as No Operation when this filter event is registered in any event structure.
The proper way to handle this is to make the LabVIEW code terminate gracefully (terminate every loop in there) and as last operation close the Front Panel explicitedly with the VI Server method.
LabVIEW Quit is btw. anyhow only a emergency bandaid. It is really analogous to crashing your car in a wall to make it stop. Pretty effective but also dangerous for various reasons. The proper way to terminate a LabVIEW built application is and has always been to make sure every loop has terminated and then close every and any front panel of your application as last measure. An open front panel (even when hidden) will keep your executable alive forever.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Process in memory after System.exit(0)

I still see the process in memory after I exit the app. Do you think it is a JWS side effect?
Platform: W2K
Cheers,
Ivan

Ivan,
when you enable the 'java console' in Java Web Start->Preferences->Advanced->Show Java Console, you'll notice that you run into a java.security.accessControlException.
To avoid that, sign your jar file(s) and add the following to your jnlp file :
<security>
<all-permissions>
</security>
and it will work as expected!
Regards,
Patrick

IFWEB90.EXE stays in memory

When I exit web page from wich Forms9i application has been started
IFWEB90.EXE stays in memory (memory isn't free). In Forms6i application
(Oracle9iAS v1.0.2.2.2a) that isn't case (IFWEB60.EXE disappears from
the memory).
How to solve that memorial problem for Forms9i applications?

FORMS90_TIMEOUT is an environment variable that you'd set in the server. Put it in the .ENV file for your application, or default.env file if you haven't created your own .ENV file.
If you go to the Forms area on OTN, you can go to the Documentation section. From, go to the Forms Online Help, in HTML format. Click on Reference, then Environment Variables. It's under there.
There are no real disadvantages of lowering the timeout until you approach the heartbeat. The heartbeat is a message from the client to the server to let the server know it is still alive. By default, the heartbeat is every two minutes.
So if your user goes to lunch, there is no activity on the client. But the heartbeat sends a message every two minutes so that server doesn't terminate. If the server doesn't hear anything in 15 minutes, then it terminates. But since there is a heartbeat every 2 minutes, this won't happen unless something goes wrong.
For instance, if someone yanks the power cord out of the client PC, then no close message is sent from the client. After 15 minutes, the server will not have heard anything, so it terminates.
If the timeout is close to the heartbeat, or less than the heartbeat, funky things can happen.
Suppose the timeout is 1 minute, and the heartbeat is the default 2 minutes. While the user is active, things are okay, the server knows the client is there and stays alive. If the user goes to lunch, the server won't get the heartbeat until 1 minutes. But the timeout is 1 minute, so it will terminate before it ever gets the hearbeat.
You might want to do this in case people don't logout, or you have sensitive information. Set the timeout for 15 minutes and the heartbeat for 16 minutes, and Forms will terminate if the user is inactive for 15 minutes.
If the timeout is greater than the heartbeat, but not by much, theoretically it should be the same as having the timeout 15 minutes and the heartbeat 2 minutes. But in reality it isn't always so.
Suppose the timeout is 3 minutes and the hearbeat is 2 minutes. If there is a glitch in the network just when a heartbeat is sent, the server won't get it. The client doesn't know this and will send another heartbeat in two minutes. But for the server, that's 4 minutes without a heartbeat, so it terminates after the 3 minute timeout period.
Similarly, if if the client retries, but each retry takes 40 seconds, which can sometimes happen, the timeout period might expire before the server gets a message.
So assuming you leave the heartbeat at it's default 2 minutes, setting the timeout to 10 minutes, or even 5 minutes shouldn't have too much affect, especially if your network isn't prone to dropping out for short periods of time. You can experiment. If you start to lose sessions, set the timeout a bit higher.
I hope this helps.
Regards,
Robin Zimmermann
Forms Product Management

Reader 9.3 causing IE to stay in processes after closing

After installing the latest Reader (9.3) for a client, their Internet Explorer remains in memory after closing it completely (iexplore.exe processes stay in task manager). This wouldn't be a problem because IE still starts back up just fine, but it causes another program they use to hang when they are trying to perform some tasks in it. When it hangs, I can close out the processes, but there's a 50/50 chance it stops hanging and continues or stays hung up. After uninstalling Reader, IE closes out fine and immediately, and their other program works fine. The other program is a little older, most likely a Windows 3.1 16-bit program. I was not yet been able to disable the Link Helper add-on for IE to see if that was the cause. Any other ideas?

Try this:
Right click on the IE8 icon in the taskbar. A menu pops ups up. Right click again on "Internet Explorer". Then left click on "Run as administrator". I had a different problem with Reader and this solved the problem. The problem I had was I could not save pdf files in IE8. This solved that problem.

Keep weblogic admin server and managed server running after exiting PUTTY

How do i keep my managed servers and admin servers running on SOLARIS (unix) boxes even after exiting putty and starting them? Do i need to create like a cron job or something?

*(after running nohup ./startWebLogic.sh i get Sending output to nohup.out and hangs there)*
out put from nohup.out =>
JAVA Memory arguments: -Xms256m -Xmx512m -XX:MaxPermSize=256m
WLS Start Mode=Production
CLASSPATH=/usr/Oracle/Middleware/patch_wls1034/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/usr/Oracle/Middleware/patch_ocp360/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/d/ct0/home/shahs06/JAVA/jdk1.6.0_25/lib/tools.jar:/usr/Oracle/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/usr/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar:/usr/Oracle/Middleware/modules/features/weblogic.server.modules_10.3.4.0.jar:/usr/Oracle/Middleware/wlserver_10.3/server/lib/webservices.jar:/usr/Oracle/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/usr/Oracle/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar:/usr/Oracle/Middleware/wlserver_10.3/common/derby/lib/derbyclient.jar:/usr/Oracle/Middleware/wlserver_10.3/server/lib/xqrl.jar
PATH=/usr/Oracle/Middleware/wlserver_10.3/server/bin:/usr/Oracle/Middleware/modules/org.apache.ant_1.7.1/bin:/d/ct0/home/shahs06/JAVA/jdk1.6.0_25/jre/bin:/d/ct0/home/shahs06/JAVA/jdk1.6.0_25/bin:/usr/sbin:/usr/bin:/usr/local/bin:/d/ct0/home/shahs06/JAVA/jdk1.6.0_25/bin
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http://hostname:port/console *
starting weblogic with Java version:
java version "1.6.0_25"
Java(TM) SE Runtime Environment (build 1.6.0_25-b06)
Java HotSpot(TM) 64-Bit Server VM (build 20.0-b11, mixed mode)
Starting WLS with line:
/d/ct0/home/shahs06/JAVA/jdk1.6.0_25/bin/java -server -d64 -Xms256m -Xmx512m -XX:MaxPermSize=256m -Dweblogic.Name=AdminServer -Djava.security.policy=/usr/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.policy -Dweblogic.ProductionModeEnabled=true -da -Dplatform.home=/usr/Oracle/Middleware/wlserver_10.3 -Dwls.home=/usr/Oracle/Middleware/wlserver_10.3/server -Dweblogic.home=/usr/Oracle/Middleware/wlserver_10.3/server -Dweblogic.management.discover=true -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=false -Dweblogic.ext.dirs=/usr/Oracle/Middleware/patch_wls1034/profiles/default/sysext_manifest_classpath:/usr/Oracle/Middleware/patch_ocp360/profiles/default/sysext_manifest_classpath weblogic.Server
<9-May-2011 1:33:56 o'clock PM PDT> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
<9-May-2011 1:33:57 o'clock PM PDT> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
<9-May-2011 1:33:59 o'clock PM PDT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) 64-Bit Server VM Version 20.0-b11 from Sun Microsystems Inc.>
<9-May-2011 1:34:04 o'clock PM PDT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.4.0 Fri Dec 17 20:47:33 PST 2010 1384255 >
<9-May-2011 1:34:12 o'clock PM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<9-May-2011 1:34:12 o'clock PM PDT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<9-May-2011 1:34:12 o'clock PM PDT> <Notice> <Log Management> <BEA-170019> <The server log file /usr/Oracle/Middleware/user_projects/domains/base_domain/servers/AdminServer/logs/AdminServer.log is opened. All server side log events will be written to this file.>
<9-May-2011 1:34:27 o'clock PM PDT> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<9-May-2011 1:34:45 o'clock PM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
<9-May-2011 1:34:45 o'clock PM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
9-May-2011 1:34:58 PM com.sun.faces.config.ConfigureListener contextInitialized
INFO: Initializing Sun's JavaServer Faces implementation (1.2_03-b04-FCS) for context '/console'
9-May-2011 1:34:58 PM com.sun.faces.config.ConfigureListener contextInitialized
INFO: Completed initializing Sun's JavaServer Faces implementation (1.2_03-b04-FCS) for context '/console'
<9-May-2011 1:35:04 o'clock PM PDT> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
<9-May-2011 1:35:04 o'clock PM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<9-May-2011 1:35:04 o'clock PM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
<9-May-2011 1:35:06 o'clock PM PDT> <Notice> <Security> <BEA-090171> <Loading the identity certificate and private key stored under the alias DemoIdentity from the jks keystore file /usr/Oracle/Middleware/wlserver_10.3/server/lib/DemoIdentity.jks.>
<9-May-2011 1:35:06 o'clock PM PDT> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /usr/Oracle/Middleware/wlserver_10.3/server/lib/DemoTrust.jks.>
<9-May-2011 1:35:06 o'clock PM PDT> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /d/ct0/home/shahs06/JAVA/jdk1.6.0_25/jre/lib/security/cacerts.>
<9-May-2011 1:35:06 o'clock PM PDT> <Alert> <Security> <BEA-090152> <Demo trusted CA certificate is being used in production mode: [
Version: V3
Subject: CN=CACERT, OU=FOR TESTING ONLY, O=MyOrganization, L=MyTown, ST=MyState, C=US
Signature Algorithm: MD5withRSA, OID = 1.2.840.113549.1.1.4
Key: SunPKCS11-Solaris RSA public key, 512 bits (id 4371458208, session object)
modulus: 9550192877869244258838480703390456015046425375252278279190673063544122510925482179963329236052146047356415957587628011282484772458983977898996276815440753
public exponent: 65537
Validity: [From: Thu Mar 21 12:12:27 PST 2002,
To: Tue Mar 22 13:12:27 PDT 2022]
Issuer: CN=CACERT, OU=FOR TESTING ONLY, O=MyOrganization, L=MyTown, ST=MyState, C=US
SerialNumber: [ 33f10648 fcde0deb 4199921f d64537f4]
Certificate Extensions: 1
[1]: ObjectId: 2.5.29.15 Criticality=true
KeyUsage [
Key_CertSign
]

Firefox mobile won't shut down after exit

Android RAZR v2.3.6
After exiting Firefox, the app stays running in the background and eats my battery. Killed it yesterday in just 4 hours. My phone runs hot while firefox is running and after exiting Firefox.
Doing a complete power off and back on doesn't work, Firefox starts back up and it is in my running apps again. It won't accept a force shut down either.
Yesterday I couldn't get Firefox to shut down until I plugged the phone back into the charger. Then it finally went away on the running apps list.

Not exiting when it goes to the background is normal and expected behavior for an Android application, but using all your CPU and ending up eating your battery sounds like a potential bug.
We released a significantly updated version of Firefox for Android today, so the first thing to try is probably updating to that. If the problem persist, please report a bug in Bugzilla. We'll really need to know at least the version you're using, though.

Excel remains in memory after using by DOI.

Hi.
I'm trying to use DOI but
Excel instance remains in memory after I have run macro and leave program. If I don't run any macro - everything is Ok.
I run macro by this way:
    CALL METHOD document->execute_macro
      EXPORTING
        macro_string = 'MyMacro'
        param_count = 0
      IMPORTING
        error      = error.
Before leaving the program I release DOI objects as in demo
    IF NOT documentproxy IS INITIAL.
      CALL METHOD documentproxy->close_document.
      CALL METHOD c_oi_errors=>show_message
        EXPORTING
          type = 'E'.
      FREE documentproxy.
    ENDIF.
    IF NOT olecontrol IS INITIAL.
      CALL METHOD olecontrol->destroy_control.
      FREE olecontrol.
    ENDIF.
Thanks for your help.
Mike Menkov.

Hello, long time no see,
but anyway, executing a macro prevents excel then to be closed over ole, as i've tried many ways to get it done, here is a work-around.
it's frustating that I cannot use excel as Inplace there, because users could then easily USE or even UPLOAD their own excel-spreadsheets over the custom control with the use of ALV-Grid firstly, wich is really nice. Because of this 'bug', (i think it definitely is one, but don't know on wich side, MS or SAP) excel-spreadsheet functionality over ALV-Grid imho simply cannot be used fine with spreadsheets containing 'bigger' macros which where executed over ole - in eo_start_macro.
For closing this issue, I just wanted to add how I could 'overcome' the sympthoms of this still remaining temp-files (+excel holding them open) when using excel + ole automation over SAPGUI:
You could just NOT use excel "Inplace" on a custom control of a dynpro, but outside SAP, still OLE-driven.
Start it in foreground guarantees you can close the temp-file with or without saving at a time and not surprisingly at the end on shutdown, because the controls of excel (and excel as a whole) are visible anytime - ole automation works also fine this way.
This is the order of preparing excel and setting data into it i've done it, therefore i've created a single include for all the excel-ole stuff:
(complete source could be looked up at http://pastebin.com/zmr6xdZm)
1.eo_get_templ_uri
2.eo_build_spreadsheet_interface - goes ahead with parameter inplace_enabled = SPACE
3.eo_build_named_area
4.eo_set_data_into_sheet
5.eo_start_macro
after the data is sent to excel (+ the macro on the spreadsheet has done it's job), excel is holding the filled temp file (spreadsheet) in foreground, so users can directly close it with- or without saving.
*** using inplace_enabled = SPACE here, on Initializing the control
CALL METHOD cl_control->init_control
   EXPORTING
     inplace_enabled          = ' '
     no_flush                 = 'X'
     INPLACE_SHOW_TOOLBARS    = insert_toolbar
     r3_application_name      = sy-cprog
     parent                   = cl_container
   IMPORTING
     error                    = error
   EXCEPTIONS
*          javabeannotsupported     = 1 " ex. nicht im Minisap
     OTHERS                   = 2.
*** and on Load document from BOR
     CALL METHOD cl_document->open_document
     EXPORTING
       "startup_macro    = 'DieseArbeitsmappe.start' "funkt nicht
       document_title = sy-cprog
       document_url   = doc_url
       no_flush       = 'X'
       open_inplace   = ' '
     IMPORTING
       retcode          = soiret
       error          = error.
     APPEND error TO t_errors.
   ENDIF.
Cheers,
David

How can i restore memory after deleting all photos on my iPad 8.1.2

iPad 4
8.1.2
Photos; not iPhoto app
Under GENERAL I cannot restore my capacity memory after deleting all my photos from the iPad.
I do not store photos in the Cloud. I do not use Photo Stream
I have reset my iPad as well as checked in Image Capture for possible photos still there.
I have also deleted last 30 days of photos.

In iOS 8.1.2 photos that are deleted from the Camera Roll are moved to the Recently Deleted album. They remain there for 30 days unless you delete them again from that album. The Recently Deleted album was created because so many people complained that they deleted photos and wanted them back. The Recently Deleted album gives people 30 days to change their mind about deleting photos. For the rest of us, it's kind of a pan to have to delete the photos twice to free up the storage space.
Oh, and there is no longer an iPhoto that works on iOS devices running iOS 8.1.2.

Mac mini not booting up with 8GB memory after 10.7.2 update

My mac mini is not booting up with 8GB of memory after the 10.7.2 update. It just keeps on beeping and flashing the led.
If I take out the upper DIMM (Bank 1) It boots just fine, and it does so with either one of the 4GB DIMMs in Bank 0, so the DIMMs are fine. It also boots up fine with two 1GB DIMMs installed simultaneously, so the Bank 1 seems to be somehow working as well.
This trouble started right after the Lion recovery update, meaning the mini has never booted with the full 8GB installed after the update.
It worked just fine before that, with the full 8GB of memory installed.
Anyone else having similar problems?
Cheers, Otto.

I have upgraded my 2011 Macbook Pro and my 2011 Mini Server
to 8 gig with Corsair RAM and have had no issues
(CMSA8GX3M2A1333C9). What brand RAM was used?
There have been issues in the past with some RAM
brands.
Something to try is a PRAM reset with the 8 gig installed.
http://docs.info.apple.com/article.html?path=Mac/10.7/en/mh26871.html
Also, make sure the Minis are booting into 64 bit mode.
Open Applications->Utilities->System Information
On the left side click the software heading. There should be a line
64-bit Kernel and Extensions: Yes
This should be the default for 2010 and 2011, but something could
have got hosed.

Front Panel objects do not stay in place after saving, closing, and reopening the VI.

I have been working with a couple of versions of a main VI. The original VI was given to me so that I could add additional functionalities to it. I had been designing the front panel of the latest version of the VI on a Dell laptop running Windows 7 and LabView 2011 SP1 using a monitor with a resolution of 1920x1080. My booleans, numerics, and plots on the front panel had always stayed in place after saving, closing, and reopening the VI. Once in the field, I connected my laptop to a cRIO9073 and used my laptop screen with a resolution of 1366x768 to operate the VI. I made some changes to the VI, saved it, and reopened it. This time I noticed that the front panel objects had become overlapped, resized, and generally rearranged. I tried fixing the objects but I noticed that they reverted back to the incorrect positions after saving and reopening the VI. I was successful in keeping the objects in position a couple of times, but when I would open the VI at a later time, the objects were again rearranged. This is happening on both my monitor and laptop screen. The original version of the VI, however, does not behave this way and I have opened it on both my monitor and laptop screen. In this version, the front panel objects always stay in place. Both VI's have the same window size properties. Could I have corrupted the latest version of my VI somehow? Below are screenshots of the front panels of both VI's.
Attachments:
Blender Controller Original.PNG ‏140 KB
Blender Controller.PNG ‏203 KB

Hi Miguel,
It is possible to programmatically set or change the position of front panel objects. (for example: http://digital.ni.com/public.nsf/allkb/4D0DA06B43195B3F862572F3000AF2D3?OpenDocument) However, if you haven’t intentionally done that, it seems unlikely that it is the problem.
Have you tried copying the entire block diagram in to a new VI to see if the problem persists? While it is unlikely, you are right that it is possible for VIs to become corrupted. I’ve never heard of a situation like this except in the situation where the settings Tom had you check have been changed. Here is some information about those settings:
http://digital.ni.com/public.nsf/allkb/7567EF257B9CFDF986256F630073228F?OpenDocument
Since there was no rearrangement when you copied the front panel to a new VI, you might try copying the block diagram a little bit at a time to see if there is some particular part of it that creates the problem somehow.
K. Johnson

Pocket slow down after exit application

Hi,
I have an application that runs normally in a Pocket PC, Windows Mobile 2003, 64 MB RAM. But when i exit application, the Pocket almost freezes ! Sometimes I need to inicialize Pocket again.
I exit my application this way:
            ConnectDB.disconnect();
            try{
                Config.getClientSocket().getSocket().close(); //Finish Socket connection with server application
            }catch(IOException e){
                MsgDialog msg = new MsgDialog(this, true, "Falha ao encerrar conex�o ", MsgDialog.MSG_WARNING);
                msg.dispose();
            new Thread(){
                public void run(){
                    try{
                        sleep(400);
                    }catch(InterruptedException e){
            }.start();
            System.exit(0);           I have two threads I've created running at this moment. Could it be a problem for Pocket performance after exit application ?
Thanks !

Hi,
I have an application that runs normally in a Pocket PC, Windows Mobile 2003, 64 MB RAM. But when i exit application, the Pocket almost freezes ! Sometimes I need to inicialize Pocket again.
I exit my application this way:
            ConnectDB.disconnect();
            try{
                Config.getClientSocket().getSocket().close(); //Finish Socket connection with server application
            }catch(IOException e){
                MsgDialog msg = new MsgDialog(this, true, "Falha ao encerrar conex�o ", MsgDialog.MSG_WARNING);
                msg.dispose();
            new Thread(){
                public void run(){
                    try{
                        sleep(400);
                    }catch(InterruptedException e){
            }.start();
            System.exit(0);           I have two threads I've created running at this moment. Could it be a problem for Pocket performance after exit application ?
Thanks !

Why does the print cue window stay open even after job is done?

In Tiger, and every other version of OSX I have any recollection of using, the printer window opens to display what's in the cue when you select to print something. Once printing is done, this cue closes. Since installing Leopard, everytime we print from our iMac, MacBook or MBP, the print cue window stays open indefinitely after the job is done, requiring a manual closing of the window. I can't for the life of me fathom what benefit this brings or who would want this. Is this part of Leopard or a problem with our install? Something I can turn off?

If you control-click (or right click) on the open printer queue in the Dock you can choose to have it auto close once the spool file is sent.
As to why this is necessary in Leopard, well I haven't seen a good enough answer to date...
PaHu

Execution stay in memory after exit

Similar Messages

Maybe you are looking for