VLC controls go MIA in fullscreen & Xorg 100% cpu

Hey guys,
I ran across a weird issue where randomly (although rather frequently) VLC's controls will visibly vanish but still be "usable." There's a semi-visible box where the controls should be and I can hover over and see tool-tips.
I'm not sure if this is a VLC issue or an Xorg issue since Xorg will peg my CPU while in fullscreen and continue doing so after VLC is done. I was wondering if anyone else has seen such a thing happen before and if anyone knows how to fix it (or at least have some leads).

I don't think screenshots are doing the issue justice here... Basically, the control box near the bottom of the fullscreen videos gets overlaid by the video so it's no longer visible (as it would normally when it's fullscreen) and when you hover over the control box, the box is "there" and usable but you can't see it. The video likes to lag a little where the box is supposed to be so you can make out the outline of the box by where the video starts to lag and tooltips are available. That's really all there is to it and I can't really manage to capture that on a screenshot. I'll keep try and see if I can finally get one that's lagging enough to be clearly visible.

Similar Messages

  • [radeon] Xorg 100% CPU, freezes, only way to resume is to reboot

    Hello, I have an ATI Radeon 9250 with the bleeding edge Arch. Occasionally, my graphics will randomly stop working, and the only thing that works is the mouse (although slowly)
    Rarely, the graphics cut out completely and the screen turns off, or I get an "Input Signal Out of Range" message from my monitor.
    The kernel doesn't crash however, I can SSH in (very slowly) and then killall -9 Xorg (but it makes no difference on the screen).
    If I run 'top' I see Xorg uses nearly 100% of CPU until it is killed by "KILL" signal. Even then, the process doesn't disappear, it just kills the processor usage.
    I will see if I can get an Xorg log and 'dmesg' from one of these crashes.
    /etc/X11/xorg.conf below:
    Section "ServerLayout"
    Identifier "X.org Configured"
    Screen 0 "Screen0" 0 0
    # Screen 1 "Screen1" RightOf "Screen0"
    InputDevice "Mouse0" "CorePointer"
    InputDevice "Keyboard0" "CoreKeyboard"
    EndSection
    Section "Files"
    ModulePath "/usr/lib/xorg/modules"
    FontPath "/usr/share/fonts/misc"
    FontPath "/usr/share/fonts/100dpi:unscaled"
    FontPath "/usr/share/fonts/75dpi:unscaled"
    FontPath "/usr/share/fonts/TTF"
    FontPath "/usr/share/fonts/Type1"
    EndSection
    Section "Module"
    Load "extmod"
    Load "glx"
    Load "dri"
    Load "record"
    Load "dbe"
    Load "dri2"
    EndSection
    Section "InputDevice"
    Identifier "Keyboard0"
    Driver "kbd"
    EndSection
    Section "InputDevice"
    Identifier "Mouse0"
    Driver "mouse"
    Option "Protocol" "auto"
    Option "Device" "/dev/input/mice"
    Option "ZAxisMapping" "4 5 6 7"
    EndSection
    Section "Monitor"
    #DisplaySize 300 220 # mm
    Identifier "Monitor0"
    VendorName "HWP"
    ModelName "HP vs15"
    HorizSync 30.0 - 63.0
    VertRefresh 50.0 - 76.0
    Option "DPMS"
    EndSection
    #Section "Monitor"
    # Identifier "Monitor1"
    # VendorName "Monitor Vendor"
    # ModelName "Monitor Model"
    #EndSection
    Section "Device"
    ### Available Driver options are:-
    ### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
    ### <string>: "String", <freq>: "<f> Hz/kHz/MHz"
    ### [arg]: arg optional
    #Option "NoAccel" # [<bool>]
    #Option "SWcursor" # [<bool>]
    #Option "Dac6Bit" # [<bool>]
    #Option "Dac8Bit" # [<bool>]
    #Option "BusType" # [<str>]
    #Option "CPPIOMode" # [<bool>]
    #Option "CPusecTimeout" # <i>
    #Option "AGPMode" # <i>
    #Option "AGPFastWrite" # [<bool>]
    #Option "AGPSize" # <i>
    #Option "GARTSize" # <i>
    #Option "RingSize" # <i>
    #Option "BufferSize" # <i>
    #Option "EnableDepthMoves" # [<bool>]
    Option "EnablePageFlip"
    #Option "NoBackBuffer" # [<bool>]
    #Option "DMAForXv" # [<bool>]
    #Option "FBTexPercent" # <i>
    #Option "DepthBits" # <i>
    #Option "PCIAPERSize" # <i>
    #Option "AccelDFS" # [<bool>]
    #Option "IgnoreEDID" # [<bool>]
    #Option "DisplayPriority" # [<str>]
    #Option "PanelSize" # [<str>]
    #Option "ForceMinDotClock" # <freq>
    #Option "ColorTiling" # [<bool>]
    #Option "VideoKey" # <i>
    #Option "RageTheatreCrystal" # <i>
    #Option "RageTheatreTunerPort" # <i>
    #Option "RageTheatreCompositePort" # <i>
    #Option "RageTheatreSVideoPort" # <i>
    #Option "TunerType" # <i>
    #Option "RageTheatreMicrocPath" # <str>
    #Option "RageTheatreMicrocType" # <str>
    #Option "ScalerWidth" # <i>
    Option "RenderAccel"
    #Option "SubPixelOrder" # [<str>]
    #Option "ShowCache" # [<bool>]
    #Option "DynamicClocks" # [<bool>]
    #Option "VGAAccess" # [<bool>]
    #Option "ReverseDDC" # [<bool>]
    #Option "LVDSProbePLL" # [<bool>]
    Option "AccelMethod" "EXA"
    #Option "DRI" # [<bool>]
    #Option "ConnectorTable" # <str>
    #Option "DefaultConnectorTable" # [<bool>]
    #Option "DefaultTMDSPLL" # [<bool>]
    #Option "TVDACLoadDetect" # [<bool>]
    #Option "ForceTVOut" # [<bool>]
    #Option "TVStandard" # <str>
    #Option "IgnoreLidStatus" # [<bool>]
    #Option "DefaultTVDACAdj" # [<bool>]
    #Option "Int10" # [<bool>]
    #Option "EXAVSync" # [<bool>]
    #Option "ATOMTVOut" # [<bool>]
    #Option "R4xxATOM" # [<bool>]
    Identifier "Card0"
    Driver "radeon"
    VendorName "ATI Technologies Inc"
    BoardName "RV280 [Radeon 9200 PRO]"
    BusID "PCI:0:8:0"
    EndSection
    #Section "Device"
    # ### Available Driver options are:-
    # ### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
    # ### <string>: "String", <freq>: "<f> Hz/kHz/MHz"
    # ### [arg]: arg optional
    # #Option "ShadowFB" # [<bool>]
    # #Option "DefaultRefresh" # [<bool>]
    # #Option "ModeSetClearScreen" # [<bool>]
    # Identifier "Card1"
    # Driver "vesa"
    # VendorName "Silicon Integrated Systems [SiS]"
    # BoardName "661/741/760 PCI/AGP or 662/761Gx PCIE VGA Display Adapter"
    # BusID "PCI:1:0:0"
    #EndSection
    Section "Screen"
    Identifier "Screen0"
    Device "Card0"
    Monitor "Monitor0"
    SubSection "Display"
    Viewport 0 0
    Depth 1
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 4
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 8
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 15
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 16
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 24
    EndSubSection
    EndSection
    #Section "Screen"
    # Identifier "Screen1"
    # Device "Card1"
    # Monitor "Monitor1"
    # SubSection "Display"
    # Viewport 0 0
    # Depth 1
    # EndSubSection
    # SubSection "Display"
    # Viewport 0 0
    # Depth 4
    # EndSubSection
    # SubSection "Display"
    # Viewport 0 0
    # Depth 8
    # EndSubSection
    # SubSection "Display"
    # Viewport 0 0
    # Depth 15
    # EndSubSection
    # SubSection "Display"
    # Viewport 0 0
    # Depth 16
    # EndSubSection
    # SubSection "Display"
    # Viewport 0 0
    # Depth 24
    # EndSubSection
    #EndSection
    I really hope someone can get to the bottom of this, it has been annoying me for quite some time. In fact, I think since the release of Xorg 7.0 if I remember.
    Its gotten worse, which is why I'm posting.

    I just set up the radeon driver for my HD 4200 graphics. I just installed Arch a couple of days ago so I am hopelessly noob.
    Anyway, after a ton of messing around I got one screen working with KMS off, a minimal xorg.conf and then changed to 2 screens with xrandr. I don't have 3d working yet, which is not a big deal for my uses. But I figure I get something working and then start adding features.  Oh yeah, I'm using Xorg 1.7.1
    my xorg:
    Section "Device"
    Identifier "HD4200"
    Driver "radeon"
    BusID "PCI:1:5:0"
    # Option "VGA-0" "Samsung"
    # Option "DVI-0" "Dell"
    EndSection
    Section "Screen"
    Identifier "HD4200"
    Device "HD4200"
    DefaultDepth 24
    Subsection "Display"
    Virtual 3200 1200
    EndSubsection
    EndSection
    Section "DRI"
    Group "video"
    Mode 0666
    EndSection
    The command that puts the screens where I want them:
    xrandr --output VGA-0 --auto --right-of DVI-0

  • Xorg 100% CPU after wake, black screen, no keyboard and mouse

    On my desktop PC after suspend/resume the keyboard is not working and the screen is black. I can only connect via ssh, but everything is slow.
    PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
    819 root 20 0 177m 68m 20m R 95,5 3,4 7:40.37 Xorg
    1670 il 20 0 318m 104m 22m R 25,2 5,2 2:49.04 skype
    1273 il 20 0 19492 8364 760 S 21,8 0,4 2:12.60 wineserver
    2222 root 20 0 15168 1724 1092 R 9,8 0,1 0:01.21 top
    'kill -KILL 819' has no effect.
    [root@il ~]# lspci
    01:00.0 VGA compatible controller: NVIDIA Corporation G94 [GeForce 9600 GT] (rev a1)
    [root@il ~]# pacman -Q linux xorg-server nvidia
    linux 3.4.4-2
    xorg-server 1.12.2-1
    nvidia 302.17-1

    It's nvidia.
    Downgrade to nvidia-295.53-2 helps.
    MadTux wrote:Did you look into the log file /var/log/pm-suspend.log, which provides more information than the usual log file.
    Nothing suspicious:
    Initial commandline parameters:
    Sun Jul 8 19:17:47 MSK 2012: Running hooks for suspend.
    Running hook /usr/lib/pm-utils/sleep.d/00logging suspend suspend:
    Linux il 3.4.2-2-ARCH #1 SMP PREEMPT Mon Jun 11 22:27:17 CEST 2012 x86_64 GNU/Linux
    Module Size Used by
    nls_cp437 5953 2
    nls_utf8 1352 1
    nls_cp866 5441 1
    vfat 10119 3
    fat 49739 1 vfat
    fuse 68768 6
    snd_hda_codec_analog 79856 1
    nvidia 10832296 30
    arc4 1410 2
    rtl8187 52527 0
    snd_hda_intel 24053 2
    snd_hda_codec 94273 2 snd_hda_intel,snd_hda_codec_analog
    snd_hwdep 6300 1 snd_hda_codec
    snd_pcm 74958 2 snd_hda_codec,snd_hda_intel
    eeprom_93cx6 2175 1 rtl8187
    mac80211 395232 1 rtl8187
    snd_page_alloc 7217 2 snd_pcm,snd_hda_intel
    snd_timer 18966 1 snd_pcm
    snd 58997 10 snd_hwdep,snd_timer,snd_pcm,snd_hda_codec,snd_hda_intel,snd_hda_codec_analog
    btusb 11764 0
    firewire_ohci 31677 0
    soundcore 5410 1 snd
    bluetooth 190551 2 btusb
    firewire_core 51552 1 firewire_ohci
    acpi_cpufreq 5933 0
    microcode 12185 0
    cfg80211 169978 2 mac80211,rtl8187
    intel_agp 10904 0
    iTCO_wdt 12813 0
    mperf 1267 1 acpi_cpufreq
    crc_itu_t 1363 1 firewire_core
    usb_storage 44728 4
    intel_gtt 14047 1 intel_agp
    iTCO_vendor_support 1929 1 iTCO_wdt
    i2c_i801 8180 0
    rfkill 15604 3 cfg80211,bluetooth
    sky2 49187 0
    coretemp 5654 0
    i2c_core 20369 2 i2c_i801,nvidia
    evdev 9754 4
    button 4502 0
    processor 26567 1 acpi_cpufreq
    pcspkr 1899 0
    asus_atk0110 9824 0
    uas 9285 0
    ext4 424175 3
    crc16 1359 2 ext4,bluetooth
    jbd2 73919 1 ext4
    mbcache 5977 1 ext4
    dm_mirror 13400 0
    dm_region_hash 7279 1 dm_mirror
    dm_log 8729 2 dm_region_hash,dm_mirror
    dm_mod 70918 22 dm_log,dm_mirror
    usbhid 36430 0
    sr_mod 14823 0
    cdrom 35648 1 sr_mod
    hid 85285 1 usbhid
    sd_mod 29239 7
    pata_jmicron 2480 0
    ahci 20549 2
    pata_acpi 3408 0
    ata_generic 3295 0
    libahci 20023 1 ahci
    libata 167515 5 ahci,pata_acpi,libahci,ata_generic,pata_jmicron
    uhci_hcd 23404 0
    scsi_mod 132942 5 uas,usb_storage,libata,sd_mod,sr_mod
    ehci_hcd 41154 0
    usbcore 147533 8 uas,btusb,uhci_hcd,rtl8187,usb_storage,ehci_hcd,usbhid
    usb_common 954 1 usbcore
    total used free shared buffers cached
    Mem: 2054720 378276 1676444 0 26004 129996
    -/+ buffers/cache: 222276 1832444
    Swap: 3903756 0 3903756
    /usr/lib/pm-utils/sleep.d/00logging suspend suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/00powersave suspend suspend:
    /usr/lib/pm-utils/sleep.d/00powersave suspend suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/01grub suspend suspend:
    /usr/lib/pm-utils/sleep.d/01grub suspend suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/49bluetooth suspend suspend:
    /usr/lib/pm-utils/sleep.d/49bluetooth suspend suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/75modules suspend suspend:
    /usr/lib/pm-utils/sleep.d/75modules suspend suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/90clock suspend suspend:
    /usr/lib/pm-utils/sleep.d/90clock suspend suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/94cpufreq suspend suspend:
    /usr/lib/pm-utils/sleep.d/94cpufreq suspend suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/95led suspend suspend:
    /usr/lib/pm-utils/sleep.d/95led suspend suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler suspend suspend:
    nVidia binary video drive detected, not using quirks.
    /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler suspend suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/99video suspend suspend:
    kernel.acpi_video_flags = 0
    /usr/lib/pm-utils/sleep.d/99video suspend suspend: success.
    Sun Jul 8 19:17:48 MSK 2012: performing suspend
    Sun Jul 8 19:18:02 MSK 2012: Awake.
    Sun Jul 8 19:18:02 MSK 2012: Running hooks for resume
    Running hook /usr/lib/pm-utils/sleep.d/99video resume suspend:
    /usr/lib/pm-utils/sleep.d/99video resume suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler resume suspend:
    /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler resume suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/95led resume suspend:
    /usr/lib/pm-utils/sleep.d/95led resume suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/94cpufreq resume suspend:
    /usr/lib/pm-utils/sleep.d/94cpufreq resume suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/90clock resume suspend:
    /usr/lib/pm-utils/sleep.d/90clock resume suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/75modules resume suspend:
    Reloaded unloaded modules.
    /usr/lib/pm-utils/sleep.d/75modules resume suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/49bluetooth resume suspend:
    /usr/lib/pm-utils/sleep.d/49bluetooth resume suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/01grub resume suspend:
    /usr/lib/pm-utils/sleep.d/01grub resume suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/00powersave resume suspend:
    /usr/lib/pm-utils/sleep.d/00powersave resume suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/00logging resume suspend:
    /usr/lib/pm-utils/sleep.d/00logging resume suspend: success.
    Sun Jul 8 19:18:02 MSK 2012: Finished.

  • How to control timing without 100% CPU usage

    I wanted fine control over timing (in windows XP), but ran into two problems.
    Problem 1: If you use the Swing timer, or Thread.sleep, the resolution is limited to 10 or 11 milliseconds. There is a Thread.sleep(millis, nanos) function, but I tested it and it still has 11ms resolution in WinXP.
    Problem 2: If you use jbanes's GAGE timer, CPU utilization will always be 100%.
    Solution: Use a hybrid technique. I would love to have nanosecond resolution AND low CPU utilization at any speed (and if you have any suggestions, please post them) but for now:
    class /*name*/ extends Thread{
    public void run(){
              setDelay(delaySettings[speed]); //Set "delay" to the desired delay in nanoseconds
              long nanos;
              while(true){
                   if(running){ //"running" is a boolean that can pause or unpause the game
                        nanos=System.nanoTime()+delay;
                        tick(); //Do the game logic and graphics for one frame
                        if(delay>11000000){ //If the system timer can handle it
                             try{sleep(delay/1000000);} //delay/1000000 gives millis
                             catch(Exception e){System.out.println("Caught sleep exception: "+e);}
                        }else{ //use a nanotimer (cpu-expensive)
                             while(System.nanoTime()<nanos){}
                   }else{ //it is paused, so wait a bit
                        try{sleep(50);}
                        catch(Exception e){System.out.println("Caught sleep exception: "+e);}
    //The rest of your code
    }If your desired delay is greater than the system timer resolution (here, I have it set at 11,000,000 nanoseconds, or 11ms) then you can use the Thread.sleep(milliseconds) call, which will have approximately 0% CPU utilization until the thread wakes up. Theoretically, you could use this time for another thread, but at the very minimum, your computer should use less power / generate less heat. If your desired resolution is smaller than 11,000,000 nanoseconds, it goes into a loop that checks nanoTime()... which gives you 100% CPU usage, but is very accurate. This works pretty well if you want to control the framerate dynamically (I use the "-"/"=" buttons to adjust speed) and it handles "pause" events, though I'm sure there are better ways to do that.
    Note: The timing granularity above 11ms for this technique is probably 11ms, though the code could be modified to provide nanosecond granularity at any speed.
    Note 2: I found this to run 3% faster than when I used the GAGE timer.
    -Cherry

    Pause the game when u alt-tab away ^_^
    Thats what most native fullscreen games do (the
    non-networked kind atleast)Good idea, but the crux of the issue is really the underlying scheduler which allows
    the thread to race.
    How to "Eliminate" 100% CPU usage.
    Tony's Law of the exec constant. <<<<"Any thread or process running on a non-preemptive operating system MUST NOT use blocking
    IO, and MUST preempt itself at leat 20MS per iteration."
    The reason it is called a constant is because it is the minimum time needed to ensure
    the underlying operating system gets enough CPU cycles to function correctly.
    Every milliseconds below this increases exponentially the chance of locking up or
    crashing despite the speed of your system.
    Most people who program do not realize the the implications of running under defective schedulers
    such as the one provided with MS windows where, for example, you can block on a socket, and
    hang your whole system.
    >>> Do NOT use Thread.sleep() <<< but instead use Object.wait();
    Do not use blockng IO. If you have to use java.io, use available() to make such you ONLY
    read the exact amount of bytes you need without blocking and make sure to prempt
    yourself at least 20MS per iteration.
    ie:
    InputStream inputStream;
    while(working)
    Object waitObject = new Object();
    int readCount = 0;
    int availableBytes = 0;
    int  totalBytes = 10;
       while(readCount < totalBytes)
          if((availableBytes = inputStream.available())!=0)
              read() (the # of Bytes available)
          else
              synchronized(waitObject)
                   waitObject.wait(200);        // 5X per second poll
                    waitObject.notifyAll();
    Using wait() removes the current thread from being scheduled; Thread.sleep()
    leaves the Thread on the schedule list. wait() releases all monitors allow other
    threads to have them; THread.sleep() does not.
    The 100% CPU issue is especially bad under NT BTW.
    If you do this not only will your CPU usage go to negligible, but you
    will never again lock your system because of it.
    Good Luck!
    (T)

  • 100% CPU Usage Overhead running EM DBConsole 11g on OEL-5.2

    After upgrading to OEL-5.2 and relinking all Oracle binaries, my old Oracle 11g installation, installed several months before on OEL-5.1, has been working well, including Enterprise Manager Database Console working nicely as always with respectful performance. Unfortunatelly, it lasted just several days.
    Yesterday I decided to uninstall the 11g completely and perform new clean installation (software and database) with the same configuration options and settings as before, including EM dbconsole, all configured using dbca. After completing the installation (EM was started automatically by dbca), oracle continued to suck 80-85% CPU time. In further few minutes CPU utilization raised up to 99% due to only one (always the same PID) client process - "oracleorcl (LOCAL=NO)". For first ten minutes I didn't care too much since I always enable Automatic Management in dbca. But after two hours, I started to worry. The process was still running, consuming sustained 99% of CPU power. No other system activity, no database activity, no disks activity at all!
    I was really puzzled since I installed and reinstalled the 11g at least 20 times on OEL-5.0 and 5.1, experimenting with ASM, raw devices, loopback devices and various combinations of installation options, but never experienced such a behaviour. It took me 3 minutes to log in to EM dbconsole as it was almost unusable performing too slow. After three hours CPU temperature was nearly 60 degrees celsius. I decided to shutdown EM and after that everything became quiet. Oracle was running normally. Started EM again, the problem was back again. Tracing enabled, it filled a 350 MB trace file in just 20 minutes. Reinstalling the software and database once again didn't help. Whenever EM is up, the CPU usage overhead of 99% persists.
    Here is a cca 23 minutes session summary report taken from EM dbconsole's Performance page. The trace file is too big to list it here, but it shows the same.
            Host CPU:  100%
    Active Sessions:  100%The details for the Selected 5 Minute Interval (the last 5 min interval) are shown as follow:
        TOP SESSIONS:  SYSMAN, Program: OMS
            Activity:  100%  
         TOP MODULES:  OEM.CacheModeWaitPool, Service: orcl
            Activity:  100%          
          TOP CLIENT:  Unnamed
            Activity:  99.1%
         TOP ACTIONS:  Unnamed (OEM.CacheModeWaitPool) (orcl)
            Activity:  100%
         TOP OBJECTS: SYSMAN.MGMT_JOB_EXEC_SUMMARY (Table)
            Activity:  100%
          TOP PL/SQL:  SYSMAN.MGMT_JOB_ENGINE.INSERT_EXECUTION
       PL/SQL Source:  SYSMAN.MGMT_JOB_ENGINE
         Line Number:  7135
            Activity:  100%
             TOP SQL:  SELECT EXECUTION_ID, STATUS, STATUS_DETAIL FROM MGMT_JOB_EXEC_SUMMARY
    WHERE JOB_ID = :B3 AND TARGET_LIST_INDEX = :B2 AND EXPECTED_START_TIME = :B1;
            Activity:  100%
                                  STATISTICS SUMMARY
                                cca 23 minutes session
                            with no other system activity
                                            Per 
                           Total      Execution         Per Row
    Executions           105,103                 1       10,510.30
    Elapsed Time (sec)  1,358.95              0.01        135.90
    CPU Time (sec)      1,070.42             0.01        107.04
    Buffer Gets       85,585,518 814.30 8,558,551.80
    Disk Reads                 2            <0.01          0.20
    Direct Writes              0              0.00          0.00
    Rows                      10            <0.01             1
    Fetches              105,103             1.00     10,510.30
                       ----------------------------------------Wow!!! Note: no disk, no database activity !
    Has anyone experienced this or similar behaviour after clean 11g installation on OEL-5.2? If not, anyone has a clue what the hell is going on?
    Thanks in advance.

    Hi Tommy,
    I didn't want to experiment further with already working OEL-5.2, oracle and dbconsole on this machine, specially not after googling the problem and finding out that I am not alone in this world. There are another two threads on OTN forums (Database General) showing the same problem even on 2GB machines:
    DBConsole easting a CPU
    11g stuck. 50-100% CPU after fresh install
    So, I took another, a smaller free machine I've got at home (1GB RAM, 2.2MHz Pentium4, three 80GB disks), on which I used to experiment with new releases of software (this is the machine on which I installed 11g for the first time when it was released on OEL-5.0, and I can recall that everything was OK with EM). This is what I did:
    1. I installed OEL-5.0 on the machine, adjusted linux and kernel parameters, and performed full 11g installation. Database and EM dbconsole worked nice with acceptable performance. Without activity in the database, %CPU = zero !!! The whole system was perfectly quiet.
    2. Since everything was OK, I shutdown EM and oracle, and performed the full upgrade to OEL-5.2. When the upgrade finished, restarted the system, relinked all oracle binaries, and started oracle and EM dbconsole. Both worked perfectly again, just as before the upgrade. I repeated restarting the database and dbconsole several times, always with the same result - it really rocks. Without database activity, %CPU = zero%.
    3. Using dbca, I dropped the database and created the new one with the same configuration options. Wow! I'm again in trouble. A half an hour after the creation of the database, %CPU raised up to 99%. That's it.
    The crucial question here is: what is that in OEL-5.2, not existing in the 5.0, that causes dbca/em scripts to be embarrassed at the time of EM agent configuration?
    Here are the outputs you required picked 30 minutes after starting the database and EM dbconsole (sustained 99% CPU utilization). Note that this is just a 1GB machine.
    Kernel command line: ro root=LABEL=/ elevator=deadline rhgb quiet
    [root@localhost ~]# cat /proc/meminfo
    MemTotal:      1034576 kB
    MemFree:         27356 kB
    Buffers:          8388 kB
    Cached:         609660 kB
    SwapCached:      18628 kB
    Active:         675376 kB
    Inactive:       287072 kB
    HighTotal:      130304 kB
    HighFree:          260 kB
    LowTotal:       904272 kB
    LowFree:         27096 kB
    SwapTotal:     3148700 kB
    SwapFree:      2940636 kB
    Dirty:              72 kB
    Writeback:           0 kB
    AnonPages:      328700 kB
    Mapped:         271316 kB
    Slab:            21136 kB
    PageTables:      14196 kB
    NFS_Unstable:        0 kB
    Bounce:              0 kB
    CommitLimit:   3665988 kB
    Committed_AS:  1187464 kB
    VmallocTotal:   114680 kB
    VmallocUsed:      5860 kB
    VmallocChunk:   108476 kB
    HugePages_Total:     0
    HugePages_Free:      0
    HugePages_Rsvd:      0
    Hugepagesize:     4096 kB
    [root@localhost ~]# cat /proc/slabinfo
    slabinfo - version: 2.1
    # name            <active_objs> <num_objs> <objsize> <objperslab> <pagesperslab> : tunables <limit> <batchcount> <sharedfactor> : slabdata <active_slabs> <num_slabs> <sharedavail>
    rpc_buffers            8      8   2048    2    1 : tunables   24   12    8 : slabdata      4      4      0
    rpc_tasks              8     15    256   15    1 : tunables  120   60    8 : slabdata      1      1      0
    rpc_inode_cache        6      7    512    7    1 : tunables   54   27    8 : slabdata      1      1      0
    ip_conntrack_expect    0      0     96   40    1 : tunables  120   60    8 : slabdata      0      0      0
    ip_conntrack          68     68    228   17    1 : tunables  120   60    8 : slabdata      4      4      0
    ip_fib_alias           7    113     32  113    1 : tunables  120   60    8 : slabdata      1      1      0
    ip_fib_hash            7    113     32  113    1 : tunables  120   60    8 : slabdata      1      1      0
    fib6_nodes            22    113     32  113    1 : tunables  120   60    8 : slabdata      1      1      0
    ip6_dst_cache         13     15    256   15    1 : tunables  120   60    8 : slabdata      1      1      0
    ndisc_cache            1     15    256   15    1 : tunables  120   60    8 : slabdata      1      1      0
    RAWv6                  4      5    768    5    1 : tunables   54   27    8 : slabdata      1      1      0
    UDPv6                  9     12    640    6    1 : tunables   54   27    8 : slabdata      2      2      0
    tw_sock_TCPv6          0      0    128   30    1 : tunables  120   60    8 : slabdata      0      0      0
    request_sock_TCPv6     0      0    128   30    1 : tunables  120   60    8 : slabdata      0      0      0
    TCPv6                  1      3   1280    3    1 : tunables   24   12    8 : slabdata      1      1      0
    jbd_1k                 0      0   1024    4    1 : tunables   54   27    8 : slabdata      0      0      0
    dm_mpath               0      0     28  127    1 : tunables  120   60    8 : slabdata      0      0      0
    dm_uevent              0      0   2460    3    2 : tunables   24   12    8 : slabdata      0      0      0
    dm_tio                 0      0     16  203    1 : tunables  120   60    8 : slabdata      0      0      0
    dm_io                  0      0     20  169    1 : tunables  120   60    8 : slabdata      0      0      0
    jbd_4k                 1      1   4096    1    1 : tunables   24   12    8 : slabdata      1      1      0
    scsi_cmd_cache        10     10    384   10    1 : tunables   54   27    8 : slabdata      1      1      0
    sgpool-128            36     36   2048    2    1 : tunables   24   12    8 : slabdata     18     18      0
    sgpool-64             33     36   1024    4    1 : tunables   54   27    8 : slabdata      9      9      0
    sgpool-32             34     40    512    8    1 : tunables   54   27    8 : slabdata      5      5      0
    sgpool-16             35     45    256   15    1 : tunables  120   60    8 : slabdata      3      3      0
    sgpool-8              60     60    128   30    1 : tunables  120   60    8 : slabdata      2      2      0
    scsi_io_context        0      0    104   37    1 : tunables  120   60    8 : slabdata      0      0      0
    ext3_inode_cache    4376   8216    492    8    1 : tunables   54   27    8 : slabdata   1027   1027      0
    ext3_xattr           165    234     48   78    1 : tunables  120   60    8 : slabdata      3      3      0
    journal_handle         8    169     20  169    1 : tunables  120   60    8 : slabdata      1      1      0
    journal_head         684   1008     52   72    1 : tunables  120   60    8 : slabdata     14     14      0
    revoke_table          18    254     12  254    1 : tunables  120   60    8 : slabdata      1      1      0
    revoke_record          0      0     16  203    1 : tunables  120   60    8 : slabdata      0      0      0
    uhci_urb_priv          0      0     28  127    1 : tunables  120   60    8 : slabdata      0      0      0
    UNIX                  56    112    512    7    1 : tunables   54   27    8 : slabdata     16     16      0
    flow_cache             0      0    128   30    1 : tunables  120   60    8 : slabdata      0      0      0
    cfq_ioc_pool           0      0     92   42    1 : tunables  120   60    8 : slabdata      0      0      0
    cfq_pool               0      0     96   40    1 : tunables  120   60    8 : slabdata      0      0      0
    crq_pool               0      0     44   84    1 : tunables  120   60    8 : slabdata      0      0      0
    deadline_drq         140    252     44   84    1 : tunables  120   60    8 : slabdata      3      3      0
    as_arq                 0      0     56   67    1 : tunables  120   60    8 : slabdata      0      0      0
    mqueue_inode_cache     1      6    640    6    1 : tunables   54   27    8 : slabdata      1      1      0
    isofs_inode_cache      0      0    368   10    1 : tunables   54   27    8 : slabdata      0      0      0
    hugetlbfs_inode_cache  1     11    340   11    1 : tunables   54   27    8 : slabdata      1      1      0
    ext2_inode_cache       0      0    476    8    1 : tunables   54   27    8 : slabdata      0      0      0
    ext2_xattr             0      0     48   78    1 : tunables  120   60    8 : slabdata      0      0      0
    dnotify_cache          2    169     20  169    1 : tunables  120   60    8 : slabdata      1      1      0
    dquot                  0      0    128   30    1 : tunables  120   60    8 : slabdata      0      0      0
    eventpoll_pwq          1    101     36  101    1 : tunables  120   60    8 : slabdata      1      1      0
    eventpoll_epi          1     30    128   30    1 : tunables  120   60    8 : slabdata      1      1      0
    inotify_event_cache    1    127     28  127    1 : tunables  120   60    8 : slabdata      1      1      0
    inotify_watch_cache   23     92     40   92    1 : tunables  120   60    8 : slabdata      1      1      0
    kioctx               135    135    256   15    1 : tunables  120   60    8 : slabdata      9      9      0
    kiocb                  0      0    128   30    1 : tunables  120   60    8 : slabdata      0      0      0
    fasync_cache           0      0     16  203    1 : tunables  120   60    8 : slabdata      0      0      0
    shmem_inode_cache    553    585    436    9    1 : tunables   54   27    8 : slabdata     65     65      0
    posix_timers_cache     0      0     88   44    1 : tunables  120   60    8 : slabdata      0      0      0
    uid_cache              5     59     64   59    1 : tunables  120   60    8 : slabdata      1      1      0
    ip_mrt_cache           0      0    128   30    1 : tunables  120   60    8 : slabdata      0      0      0
    tcp_bind_bucket       32    203     16  203    1 : tunables  120   60    8 : slabdata      1      1      0
    inet_peer_cache        1     59     64   59    1 : tunables  120   60    8 : slabdata      1      1      0
    secpath_cache          0      0     32  113    1 : tunables  120   60    8 : slabdata      0      0      0
    xfrm_dst_cache         0      0    384   10    1 : tunables   54   27    8 : slabdata      0      0      0
    ip_dst_cache           6     15    256   15    1 : tunables  120   60    8 : slabdata      1      1      0
    arp_cache              2     15    256   15    1 : tunables  120   60    8 : slabdata      1      1      0
    RAW                    2      7    512    7    1 : tunables   54   27    8 : slabdata      1      1      0
    UDP                    3      7    512    7    1 : tunables   54   27    8 : slabdata      1      1      0
    tw_sock_TCP            3     30    128   30    1 : tunables  120   60    8 : slabdata      1      1      0
    request_sock_TCP       4     30    128   30    1 : tunables  120   60    8 : slabdata      1      1      0
    TCP                   43     49   1152    7    2 : tunables   24   12    8 : slabdata      7      7      0
    blkdev_ioc             3    127     28  127    1 : tunables  120   60    8 : slabdata      1      1      0
    blkdev_queue          23     24    956    4    1 : tunables   54   27    8 : slabdata      6      6      0
    blkdev_requests      137    161    172   23    1 : tunables  120   60    8 : slabdata      7      7      0
    biovec-256             7      8   3072    2    2 : tunables   24   12    8 : slabdata      4      4      0
    biovec-128             7     10   1536    5    2 : tunables   24   12    8 : slabdata      2      2      0
    biovec-64              7     10    768    5    1 : tunables   54   27    8 : slabdata      2      2      0
    biovec-16              7     15    256   15    1 : tunables  120   60    8 : slabdata      1      1      0
    biovec-4               8     59     64   59    1 : tunables  120   60    8 : slabdata      1      1      0
    biovec-1             406    406     16  203    1 : tunables  120   60    8 : slabdata      2      2    300
    bio                  564    660    128   30    1 : tunables  120   60    8 : slabdata     21     22    204
    utrace_engine_cache    0      0     32  113    1 : tunables  120   60    8 : slabdata      0      0      0
    utrace_cache           0      0     32  113    1 : tunables  120   60    8 : slabdata      0      0      0
    sock_inode_cache     149    230    384   10    1 : tunables   54   27    8 : slabdata     23     23      0
    skbuff_fclone_cache   20     20    384   10    1 : tunables   54   27    8 : slabdata      2      2      0
    skbuff_head_cache     86    210    256   15    1 : tunables  120   60    8 : slabdata     14     14      0
    file_lock_cache       22     40     96   40    1 : tunables  120   60    8 : slabdata      1      1      0
    Acpi-Operand        1147   1196     40   92    1 : tunables  120   60    8 : slabdata     13     13      0
    Acpi-ParseExt          0      0     44   84    1 : tunables  120   60    8 : slabdata      0      0      0
    Acpi-Parse             0      0     28  127    1 : tunables  120   60    8 : slabdata      0      0      0
    Acpi-State             0      0     44   84    1 : tunables  120   60    8 : slabdata      0      0      0
    Acpi-Namespace       615    676     20  169    1 : tunables  120   60    8 : slabdata      4      4      0
    delayacct_cache      233    312     48   78    1 : tunables  120   60    8 : slabdata      4      4      0
    taskstats_cache       12     53     72   53    1 : tunables  120   60    8 : slabdata      1      1      0
    proc_inode_cache     622    693    356   11    1 : tunables   54   27    8 : slabdata     63     63      0
    sigqueue               8     27    144   27    1 : tunables  120   60    8 : slabdata      1      1      0
    radix_tree_node     6220   8134    276   14    1 : tunables   54   27    8 : slabdata    581    581      0
    bdev_cache            37     42    512    7    1 : tunables   54   27    8 : slabdata      6      6      0
    sysfs_dir_cache     4980   4992     48   78    1 : tunables  120   60    8 : slabdata     64     64      0
    mnt_cache             36     60    128   30    1 : tunables  120   60    8 : slabdata      2      2      0
    inode_cache         1113   1254    340   11    1 : tunables   54   27    8 : slabdata    114    114     81
    dentry_cache       11442  18560    136   29    1 : tunables  120   60    8 : slabdata    640    640    180
    filp                7607  10000    192   20    1 : tunables  120   60    8 : slabdata    500    500    120
    names_cache           19     19   4096    1    1 : tunables   24   12    8 : slabdata     19     19      0
    avc_node              14     72     52   72    1 : tunables  120   60    8 : slabdata      1      1      0
    selinux_inode_security 814   1170     48   78    1 : tunables  120   60    8 : slabdata     15     15      0
    key_jar               14     30    128   30    1 : tunables  120   60    8 : slabdata      1      1      0
    idr_layer_cache      170    203    136   29    1 : tunables  120   60    8 : slabdata      7      7      0
    buffer_head        38892  39024     52   72    1 : tunables  120   60    8 : slabdata    542    542      0
    mm_struct            108    135    448    9    1 : tunables   54   27    8 : slabdata     15     15      0
    vm_area_struct     11169  14904     84   46    1 : tunables  120   60    8 : slabdata    324    324    144
    fs_cache              82    177     64   59    1 : tunables  120   60    8 : slabdata      3      3      0
    files_cache          108    140    384   10    1 : tunables   54   27    8 : slabdata     14     14      0
    signal_cache         142    171    448    9    1 : tunables   54   27    8 : slabdata     19     19      0
    sighand_cache        127    135   1344    3    1 : tunables   24   12    8 : slabdata     45     45      0
    task_struct          184    246   1360    3    1 : tunables   24   12    8 : slabdata     82     82      0
    anon_vma            3313   5842     12  254    1 : tunables  120   60    8 : slabdata     23     23      0
    pgd                   84     84   4096    1    1 : tunables   24   12    8 : slabdata     84     84      0
    pid                  237    303     36  101    1 : tunables  120   60    8 : slabdata      3      3      0
    size-131072(DMA)       0      0 131072    1   32 : tunables    8    4    0 : slabdata      0      0      0
    size-131072            0      0 131072    1   32 : tunables    8    4    0 : slabdata      0      0      0
    size-65536(DMA)        0      0  65536    1   16 : tunables    8    4    0 : slabdata      0      0      0
    size-65536             2      2  65536    1   16 : tunables    8    4    0 : slabdata      2      2      0
    size-32768(DMA)        0      0  32768    1    8 : tunables    8    4    0 : slabdata      0      0      0
    size-32768             9      9  32768    1    8 : tunables    8    4    0 : slabdata      9      9      0
    size-16384(DMA)        0      0  16384    1    4 : tunables    8    4    0 : slabdata      0      0      0
    size-16384             6      6  16384    1    4 : tunables    8    4    0 : slabdata      6      6      0
    size-8192(DMA)         0      0   8192    1    2 : tunables    8    4    0 : slabdata      0      0      0
    size-8192              5      5   8192    1    2 : tunables    8    4    0 : slabdata      5      5      0
    size-4096(DMA)         0      0   4096    1    1 : tunables   24   12    8 : slabdata      0      0      0
    size-4096            205    205   4096    1    1 : tunables   24   12    8 : slabdata    205    205      0
    size-2048(DMA)         0      0   2048    2    1 : tunables   24   12    8 : slabdata      0      0      0
    size-2048            260    270   2048    2    1 : tunables   24   12    8 : slabdata    135    135      0
    size-1024(DMA)         0      0   1024    4    1 : tunables   54   27    8 : slabdata      0      0      0
    size-1024            204    204   1024    4    1 : tunables   54   27    8 : slabdata     51     51      0
    size-512(DMA)          0      0    512    8    1 : tunables   54   27    8 : slabdata      0      0      0
    size-512             367    464    512    8    1 : tunables   54   27    8 : slabdata     58     58      0
    size-256(DMA)          0      0    256   15    1 : tunables  120   60    8 : slabdata      0      0      0
    size-256             487    495    256   15    1 : tunables  120   60    8 : slabdata     33     33      0
    size-128(DMA)          0      0    128   30    1 : tunables  120   60    8 : slabdata      0      0      0
    size-128            2242   2490    128   30    1 : tunables  120   60    8 : slabdata     83     83      0
    size-64(DMA)           0      0     64   59    1 : tunables  120   60    8 : slabdata      0      0      0
    size-32(DMA)           0      0     32  113    1 : tunables  120   60    8 : slabdata      0      0      0
    size-64             1409   2950     64   59    1 : tunables  120   60    8 : slabdata     50     50      0
    size-32             3596   3842     32  113    1 : tunables  120   60    8 : slabdata     34     34      0
    kmem_cache           145    150    256   15    1 : tunables  120   60    8 : slabdata     10     10      0
    [root@localhost ~]# slabtop -d 5
    Active / Total Objects (% used)    : 97257 / 113249 (85.9%)
    Active / Total Slabs (% used)      : 4488 / 4488 (100.0%)
    Active / Total Caches (% used)     : 101 / 146 (69.2%)
    Active / Total Size (% used)       : 15076.34K / 17587.55K (85.7%)
    Minimum / Average / Maximum Object : 0.01K / 0.16K / 128.00K
      OBJS ACTIVE  USE OBJ SIZE  SLABS OBJ/SLAB CACHE SIZE NAME
    25776  25764  99%    0.05K    358       72      1432K buffer_head
    16146  15351  95%    0.08K    351       46      1404K vm_area_struct
    15138   7779  51%    0.13K    522       29      2088K dentry_cache
      9720   9106  93%    0.19K    486       20      1944K filp
      7714   7032  91%    0.27K    551       14      2204K radix_tree_node
      5070   5018  98%    0.05K     65       78       260K sysfs_dir_cache
      4826   4766  98%    0.01K     19      254        76K anon_vma
      4824   3406  70%    0.48K    603        8      2412K ext3_inode_cache
      3842   3691  96%    0.03K     34      113       136K size-32
      2190   2174  99%    0.12K     73       30       292K size-128
      1711   1364  79%    0.06K     29       59       116K size-64
      1210   1053  87%    0.33K    110       11       440K inode_cache
      1196   1147  95%    0.04K     13       92        52K Acpi-Operand
      1170    814  69%    0.05K     15       78        60K selinux_inode_security
       936    414  44%    0.05K     13       72        52K journal_head
       747    738  98%    0.43K     83        9       332K shmem_inode_cache
       693    617  89%    0.35K     63       11       252K proc_inode_cache
       676    615  90%    0.02K      4      169        16K Acpi-Namespace
       609    136  22%    0.02K      3      203        12K biovec-1
       495    493  99%    0.25K     33       15       132K size-256
       480    384  80%    0.12K     16       30        64K bio
       440    399  90%    0.50K     55        8       220K size-512
       312    206  66%    0.05K      4       78        16K delayacct_cache
       303    209  68%    0.04K      3      101        12K pid
       290    290 100%    0.38K     29       10       116K sock_inode_cache
    [root@localhost ~]# cat /etc/sysctl.conf
    # Kernel sysctl configuration file for Red Hat Linux
    # Controls IP packet forwarding
    net.ipv4.ip_forward=0
    # Controls source route verification
    net.ipv4.conf.default.rp_filter=1
    # Do not accept source routing
    net.ipv4.conf.default.accept_source_route=0
    # Oracle
    net.ipv4.ip_local_port_range=1024 65000
    net.core.rmem_default=4194304
    net.core.rmem_max=4194304
    net.core.wmem_default=262144
    net.core.wmem_max=262144
    net.ipv4.tcp_rmem=4096 65536 4194304
    net.ipv4.tcp_wmem=4096 65536 4194304
    # Keepalive Oracle
    net.ipv4.tcp_keepalive_time=3000
    net.ipv4.tcp_keepalive_intvl=30
    net.ipv4.tcp_keepalive_probes=15
    net.ipv4.tcp_retries2=3
    net.ipv4.tcp_syn_retries=2
    net.ipv4.tcp_sack=0
    net.ipv4.tcp_timestamps=0
    net.ipv4.tcp_window_scaling=0
    # Oracle
    fs.file-max = 6553600
    fs.aio-max-nr=3145728
    kernel.shmmni=4096
    kernel.sem=250 32000 100 142
    kernel.shmmax=2147483648
    kernel.shmall=3279547
    kernel.msgmnb=65536
    kernel.msgmni=2878
    kernel.msgmax=8192
    kernel.exec-shield=0
    # Controls the System Request debugging functionality of the kernel
    kernel.sysrq=1
    kernel.panic=60
    kernel.core_uses_pid=1
    [root@localhost ~]# free | grep Swap
    Swap:      3148700     319916    2828784
    [root@localhost ~]# cat /etc/fstab | grep "/dev/shm"
    tmpfs                   /dev/shm                tmpfs   size=1024M      0 0
    [root@localhost ~]# df | grep "/dev/shm"
    tmpfs                  1048576    452128    596448  44% /dev/shm
    NON-DEFAULT DB PARAMETERS:
    db_block_size        8192
    memory_target          633339904  /* automatic memory management */
    open_cursors         300
    processes            256
    disk_async_io        TRUE
    filesystemio_options SETALL

  • 100% CPU using LabView 7.1 and DSC module

    Seven years ago I used BridgeView and PXI to execute a project, and the results were so good that after that initial system, I installed one more using BridgeView, and three more using LabView 7.1.
    BridgeView is working very well, but lately, LabView 7.1 is giving me more and more problems. It all started in a system running LabView 7.1 and DSC on Windows XP, using a PXI-8187 controller with a PXI-1042 chassis. I have two PXI-6533 digital I/O boards, one PXI-6030E multifunction, one PXI-6713 analog output board, one PXI-6602 counter board and one PXI-8422 serial com. board. In may/06, all of the sudden, the CPU went to a 100% use. Since I am running PID's to control a flash-butt welding machine in a steel factory, this was extremely dangerous. I changed the controller and everything went back to normal. It was running fine until december/06, when the same behavior appeared again. This time changing the controller did not help. We increased the system memory, from 256 MB to 512 MB and everything worked fine. But one month later (january/07) the fault reappeared. This time we changed the chassis and from that moment to this time, we are running smoothly.
    Application problems were suspect from the very first time this problem appeared, but I was unable to identify the source, if any. I used PROFILE VI's and apparently the write/read tags were taking all the processor resources. However, changing the routines and disabling communications, and optimizing CPU intensive programs never solved the CPU overload.
    Until now, I was aware of only one system showing this erratic behavior. But today I went to check another system, with a totally different application. This one is used to measure the thickness of the steel sheet on a rolling mill. Is not so resource-intensive, but the maintenance folks told me that every time they turned off this particular system, they always had problems trying to turn it on.
    I was suspecting of a PLC-communication related issue, but what I found turned my alarms on. I turned off the system, which was fully functional, and turned it back on, and there it was, CPU load at 100%!. Is exactly the same problem that I have on the welder. This system has a PXI-8184, a PXI-1042 chassis, Windows XP, one PXI-6030E, one PXI-6713 and one PXI-6533. I battled for 20 minutes to put the system back in normal conditions.
    I specified every single board, installed everything and programmed all the applications. The BridgeView applications have never showed anything like this. I am using the DSC (Datalogging and Supervisory Control Module) on both applications, and the Lookout Protocol Drivers are communicating to Modicon PLC's.
    Please, I need help to solve this issue. I believe none of your actual Knowledge Base "100% CPU" articles apply to my case...
    Thanks in advance...
    Antonio Jimenez
    [email protected]

    Thanks for your reply...
    Yes, sometimes I have the feeling that the systems works again because some file or database gets initialized after so many reboots.
    Intentionally I turned off all the events and alarm logging to disk. Also the historical data logging is disabled. This is done by code, every time the main VI is started. This was included precisely to save CPU processing power. However, I am communicating to PLC's, and of course I have to declare variables inside the citadel database to make the communication possible.
    Right now I can't have access to the application, because the mill is rolling, but during the next maintenance stop I will check the database location and size, and I could change the directory location the next time the fault comes up.

  • 100% CPU load but no clue in thread dump, EP. Win a bottle of champagne...

    Hi,
    We are suddenly facing 100% CPU load in our EP cluster (5 x 8-way Xeon multiprocessor machines). We have a serious performance problem that is burning a lot of our time and causes a lot of stress for over 3 weeks now.
    We have taken tens of thread dumps from Application Nodes.
    - In none of the thread dumps we see the Finalizer thread
    running.
    - From the garbage collector log we see that full garbage
    collection runs occur very rarily (once an hour).
    - We use the compacting garbage collector.
    - In a lot of thread dumps we do not even see our own portal code in the stack traces of the threads!
    - In Windows Task Manager we see the jlaunch.exe processes
    consume all available CPU time.
    - Portal users see a blank portal page when the CPU load hits 100%. When the load goes down again, things return to normal.
    - There are no errors logged in any of the log files of the portal. We checked all of them. We expected a log full of errors somewhere but nothing even remotely interesting was found. Windows Event Viewer shows nothing either.
    - The amount of sockets in CLOSE_WAIT status is < 10 on every machine in the cluster.
    This forces me to conclude that something in the jlaunch.exe executable consumes the CPU time. This raises the following 3 questions:
    - What does the mystifying jlaunch.exe do besides executing java.exe ?
    - Why is the Java virtual machine launched by a custom executable like jlaunch (What is it that cannot be program med in Java) ? Can it be GZip compression ?
    - If the problem is not caused by jlaunch.exe, then it must be caused by the JVM. What activity, invisible in thread dumps, is performed by the JVM that can cause the high CPU load ?
    Our development- and support teams are desperate. All suggestions are welcome. The person that comes up with
    the solution to our problem gets a nice bottle of champagne.
    Regards,
    Chris Twigt

    Hi,
    - What does the mystifying jlaunch.exe do besides executing java.exe ?
    This is so that the startupframework can connect more easily and take control of the JVM in some situations
    - Why is the Java virtual machine launched by a custom executable like jlaunch (What is it that cannot be program med in Java) ?
    I assume when SAP release their JVM (in the next major release), that will be called directly.
    - If the problem is not caused by jlaunch.exe, then it must be caused by the JVM. What activity, invisible in thread dumps, is performed by the JVM that can cause the high CPU load ?
    Loads of thing, but there should be clues in the thread dumps.  (the reason why your code is not in those thread dumps is that your code is only active during the processing of a particular request, unless you have a service, afterwards there are no trace of it as the thread which does the processing goes back to sleep)
    I've experienced a similar situation with a an 6.40 portal, and it was then caused by the following:
    1. User A comes logs in and sees that some cache timeout has occured , therefore it issues a SQL query which does a full table scan on a table of approx. 1 GB (on of the UME tables)
    2. User B comes in just afterwards and also sees that the cache timeout has occured, and issues the same SQL query as User A
    3. User C .... and so on untill the query from User A eventually finishes
    So
    1. Check database. Any big queries running ?
    2. Check file activity, are there a lot of writing ?
    3. Check network activity, especially to the state controller which is the weakest link
    4. What about portal logs ? Any activity during the hang ?
    Also, please provide one of the thread dumps for further analysis..
    cheers
    Dagfinn

  • Fuzzy Logic 4 & 100% CPU Usage freeze

    Hi,
    is there any Fuzzy Logic 4 Version out there that works with KT3 Ultra2-R and XP?
    I tried 4.0.63.1 and 4.1.48.0 from the MSI Pages and the Version I got on CD
    4.0.63.1 just can't find the avi ...
    4.1.48.0 and the CD Version just add the Icon to the taskbar when starting and than take 100% CPU-Time and do nothing anymore.
    The Program is not even killable in Taskmanager so all I can do afterwards is wait 10 minutes until XP has shutdown with the leftover CPUtime.

    I understand the CS2 is probably not helping, but there is really a problem on other apps too - not only CS2 and those are universal.
    Page ins/outs are currently 142257/71109 and i have not been using or even opening CS2 - just safari, itunes, What size , MSEntourage, VLC and moving some files.
    I have taken some earlier advice on your posts regarding using multiple internal disks - so i moved itunes and iphoto libraries to a separate disk and also use that for scratch in CS2. The drives are 250GB WD and 250GB Seagate, and i am looking at replacing them with one or two 750GB WD RE2, although probably not in RAID ( dont want to complicate my life too much in one go !)
    Overall i think the page ins/outs look high from my searching in other posts, but can't see why it would be overloaded when i normally dont use the CS2 that much ( only a hobby)
    Also the private/var/vm directory has 3 swap files - two of 64 MB and one (Swapfile2) is 128MB, if that tells something else ?
    looks like i will have to invest in 4GB more memory as well as the HDD's. i was confused with the apparent further lack of support in CS3 for 64 bit programming (?) although i dont know when that would be launched so soon after CS3
    I have a case of a little knowledge ( which can be a dangerous thing!)
    Message was edited by: grahams

  • After starting up the listener the server consuming 100% CPU

    Hi,
    when i startup the database tier (EBS 12.1.3 and DB 11.2.0.2) its stared well and the CPU usage is normal.But when i start the listener the server (RHEL 5.8) start consuming 100% CPU.
    alert.log details
    in file /ebs/UAT/bin/db/tech_st/11.2.0/admin/UAT_dcvlodbdev/diag/rdbms/uat/UAT/trace/UAT_j000_7601.trc:
    ORA-00600: internal error code, arguments: [13011], [262414], [1644193998], [33], [1644194002], [0], [], [], [], [], [], []
    ORA-06512: at "APPS.WF_BES_CLEANUP", line 488
    ORA-06512: at line 1
    Wed Dec 12 10:11:33 2012
    Sweep [inc][480592]: completed
    Wed Dec 12 10:13:17 2012
    Errors in file /ebs/UAT/bin/db/tech_st/11.2.0/admin/UAT_dcvlodbdev/diag/rdbms/uat/UAT/trace/UAT_j001_7624.trc (incident=480612):
    ORA-00600: internal error code, arguments: [13011], [262414], [1644193998], [33], [1644194002], [0], [], [], [], [], [], []
    Use ADRCI or Support Workbench to package the incident.
    See Note 411.1 at My Oracle Support for error and packaging details.
    Errors in file /ebs/UAT/bin/db/tech_st/11.2.0/admin/UAT_dcvlodbdev/diag/rdbms/uat/UAT/trace/UAT_j001_7624.trc:
    ORA-00600: internal error code, arguments: [13011], [262414], [1644193998], [33], [1644194002], [0], [], [], [], [], [], []
    ORA-06512: at "APPS.WF_BES_CLEANUP", line 488
    ORA-06512: at line 1
    Wed Dec 12 10:13:18 2012
    Sweep [inc][480612]: completed
    Wed Dec 12 10:14:18 2012
    Errors in file /ebs/UAT/bin/db/tech_st/11.2.0/admin/UAT_dcvlodbdev/diag/rdbms/uat/UAT/trace/UAT_ora_7814.trc (incident=481092):
    ORA-00600: internal error code, arguments: [kdsgrp1], [], [], [], [], [], [], [], [], [], [], []
    Incident details in: /ebs/UAT/bin/db/tech_st/11.2.0/admin/UAT_dcvlodbdev/diag/rdbms/uat/UAT/incident/incdir_481092/UAT_ora_7814_i481092.trc
    Wed Dec 12 10:14:23 2012
    Dumping diagnostic data in directory=[cdmp_20121212101423], requested by (instance=1, osid=7814), summary=[incident=481092].
    Use ADRCI or Support Workbench to package the incident.
    See Note 411.1 at My Oracle Support for error and packaging details.
    Wed Dec 12 10:14:24 2012
    Sweep [inc][481092]: completed
    Sweep [inc2][481092]: completed
    Wed Dec 12 10:16:50 2012
    Errors in file /ebs/UAT/bin/db/tech_st/11.2.0/admin/UAT_dcvlodbdev/diag/rdbms/uat/UAT/trace/UAT_j001_8058.trc (incident=481492):
    ORA-00600: internal error code, arguments: [13011], [262414], [1644193998], [33], [1644194002], [0], [], [], [], [], [], []
    Use ADRCI or Support Workbench to package the incident.
    See Note 411.1 at My Oracle Support for error and packaging details.
    Errors in file /ebs/UAT/bin/db/tech_st/11.2.0/admin/UAT_dcvlodbdev/diag/rdbms/uat/UAT/trace/UAT_j001_8058.trc:
    ORA-00600: internal error code, arguments: [13011], [262414], [1644193998], [33], [1644194002], [0], [], [], [], [], [], []
    ORA-06512: at "APPS.WF_BES_CLEANUP", line 488
    ORA-06512: at line 1
    Wed Dec 12 10:19:04 2012
    Incremental checkpoint up to RBA [0xf.ac257.0], current log tail at RBA [0xf.c3691.0]
    Wed Dec 12 10:20:56 2012
    Active Session History (ASH) performed an emergency flush. This may mean that ASH is undersized. If emergency flushes are a recurring issue, you may consider increasing ASH size by setting the value of ASHSIZE to a sufficiently large value. Currently, ASH size is 2097152 bytes. Both ASH size and the total number of emergency flushes since instance startup can be monitored by running the following query:
    select total_size,awr_flush_emergency_count from v$ash_info;
    Wed Dec 12 10:21:26 2012
    Sweep [inc][481492]: completed

    Please see these docs.
    ORA-600/ORA-7445/ORA-700 Error Look-up Tool [ID 153788.1]
    ORA-600 [13011] "Problem occurred when trying to delete a row" [ID 28184.1]
    Workflow Control Queue Clean Up Program Fails With ORA-25226 [ID 334237.1]
    Thanks,
    Hussein

  • Emca -deconfig dbcontrol db -repos drop, perl 100%CPU

    Hello!
    My system is: Red Hat Enterprise Linux AS release 4 x64, Oracle 10.2.0.1.0
    Few days ago I had found that 2 perl processes eat 100% CPU.
    So I decided to restart EM. But the problem remain the same.
    Then I decided to recreate EM repository:
    emca -deconfig dbcontrol db -repos drop -SID db1 -HOST HP -ORACLE_HOME /app/oracle
    STARTED EMCA at Jul 9, 2010 11:49:17 AM
    EM Configuration Assistant, Version 10.2.0.1.0 Production
    Copyright (c) 2003, 2005, Oracle. All rights reserved.
    Enter the following information:
    Listener port number: 1521
    Password for SYS user:
    Password for SYSMAN user:
    Do you wish to continue? [yes(Y)/no(N)]: y
    Jul 9, 2010 11:49:31 AM oracle.sysman.emcp.EMConfig perform
    INFO: This operation is being logged at /app/oracle/cfgtoollogs/emca/ db1 /emca_2010-07-09_11-49-17-AM.log.
    Jul 9, 2010 11:49:31 AM oracle.sysman.emcp.util.DBControlUtil stopOMS
    INFO: Stopping Database Control (this may take a while) ...
    Jul 9, 2010 11:49:33 AM oracle.sysman.emcp.EMReposConfig dropRepository
    INFO: Dropping the EM repository (this may take a while) ...
    In this point command hangs.
    Looking to the processes:
    ps aux | grep perl
    oracle 15592 101 0.0 23752 8672 pts/2 R+ 12:11 0:24 /app/oracle/perl/bin/perl /app/oracle/sysman/admin/emdrep/bin/emrepmgr.pl -connect (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=HP)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME= db1))) -repos_user SYSMAN -action drop -verbose -output_file /app/oracle/cfgtoollogs/emca/ db1 /emca_repos_drop_2010-07-09_12-11-40-PM.log
    oracle 15667 0.0 0.0 51100 688 pts/4 S+ 12:12 0:00 grep perl
    Looking to the log:
    [oracle@HP db1]$ tail -n 50 /app/oracle/cfgtoollogs/emca/ db1 /emca_repos_drop_2010-07-09_12-11-40-PM.log
    [09-07-2010 12:11:40] Enter SYS user's password :
    [09-07-2010 12:11:40]
    [09-07-2010 12:11:40] Enter repository user password :
    [09-07-2010 12:11:40]
    [09-07-2010 12:11:40] Getting temporary tablespace from database...
    Could you please help me with this?
    Why does perl hang? And how to correctly recreate repository?
    (Is it possible to recreate repository without any outages(quiescing or restart the DB))
    Thanks!

    Yesterday I've started EM, but emagent had 100%CUP again.
    And there was an active session by sysman:
    BEGIN EMD_NOTIFICATION.QUEUE_READY(:1, :2, :3); END;
    After making some research, i've done this:
    sqlplus sysman@db1
    SQL>@/app/oracle/sysman/admin/emdrep/sql/core/latest/notification/notification_pkgbodys.sql
    (changing string DBMS_AQ.LISTEN (agents, qtimeout_in, agent);
    to DBMS_AQ.LISTEN (agents, 1200, agent);
    in it
    After restarting EM this problem remain the same.
    Logs:
    cat ./emagent.log
    2010-07-12 12:28:44 Thread-4136454368 Starting Agent 10.1.0.4.1 from /app/oracle (00701)
    2010-07-12 12:29:44 Thread-4136454368 target {db1, oracle_database} is broken: cannot compute dynamic properties in time. (00155)
    2010-07-12 12:29:44 Thread-4136454368 EMAgent started successfully (00702)
    and
    [oracle@HP log]$ tail -n 5 ./emdctl.trc
    2010-07-12 12:28:32 Thread-4136453824 WARN http: snmehl_connect: connect failed to (HP:3938): Connection refused (error = 111)
    2010-07-12 12:28:34 Thread-4136453824 WARN http: snmehl_connect: connect failed to (HP:3938): Connection refused (error = 111)
    2010-07-12 12:28:37 Thread-4136453824 WARN http: snmehl_connect: connect failed to (HP:3938): Connection refused (error = 111)
    2010-07-12 12:28:40 Thread-4136453824 WARN http: snmehl_connect: connect failed to (HP:3938): Connection refused (error = 111)
    2010-07-12 12:28:43 Thread-4136453824 WARN http: snmehl_connect: connect failed to (HP:3938): Connection refused (error = 111)
    Why does "Connection refused" appear?
    How to deal with this issue?
    Yours suggestions will be VERY appreciated. Thanks!
    Edited by: dmitry_rpd on Jul 13, 2010 12:33 AM

  • Premiere Elements 10 - Organiser 100% CPU

    Hi there folks, I hope someone can help me!
    I've recently bought the combined Photoshop & Premier Elements 10 package and installed it on my system, however I am having a massive problem with the Organiser.
    When I load either of the programs my CPU usage shoots up to 100% and my system runs very slowly.. if I quit it also keeps the process running in the background at 100% cpu..
    If I end the process my system returns to normal.
    Also the organiser does not show thumbnails for all of my video clips - only some.
    Does anyone know what could be causing this? I've tried removing and reinstalling it with no luck!
    Thanks in advance!
    System spec:
    Intel i5 2500 running at stock speed, 8gb DDR3-1600 Vengence, Asus H67 board, Intel 80gb SSD, Samsung Spinpoint 1Tb HDD, Windows 7 HP 64bit, Norton IS 2012, Klite mega codec pack, VLC media player

    No sorry I still have the issue. Have tried all of the fixes here to no avail (thanks all for the help though!)
    Only thing I have noticed is if you don't actually load the organiser at all and just load premier directly; you can use the inbuilt organiser (top right of screen) and premier works fine.
    I've given up on the organiser ever working correctly now. I've tried a complete system re-install and still no luck..

  • CS6 and AME 100% CPU utilisation

    So this is an odd question to ask maybe as we often asked for max CPU utilisation when encoding in the past to get stuff done quicker.
    But - this is entirely new behaviour for me at least. I have a 6 core i7 X980 with HT and 24GB ram. In the past, I could queue up several sequences and let them encode to H.264 in the background while i carry on editing. Worked fine with no problems.
    I recently upgraded my GPU to a 4GB GTX680 from a 1.2GB GTX570. There have also been 2 updates to PPro as well since I noticed this behaviour.
    So the issue is that when encoding, all 12 threads are at 100% CPU utilisation and my mouse control suffers terribly - very very slow mouse as obviously there's not enough CPU resources to drive the pointer properly. This never happened in the past as CPU utilisation was never maxed out like this.
    Anyone seen anything similar?
    Thanks,
    Paul.

    Hi Darren,
    I've not benchmarked the two cards in Premiere - I've not noticed any difference in real world use. Reading a few comparison reviews out there kind of said the same thing too (although gaming based reviews). The reason I went for the 680 was the availability of a 4GB VRAM model which was really important for me in After Effects using complex 3D models in the Video Copilot plugin, Element 3D.
    So it was worth it for the memory but maybe not just for Premiere. I don't tend to do a load of video layers at once, the most is maybe a couple of layers PIP on virtual studio type projects but then most of them end up in AE really as its just hugely more flexible and fun to work with

  • 100% CPU Usage caused by HMI

    Hi everybody:
    I'm working with LabVIEW DSC 8.2.1 in a system that monitors many variables of a plant, such a typical SCADA system. For this reason, the use of the graphic tools is highly used on the development of this system. Everything works fine, but I have only one problem.... the usage of the CPU.
    When I am working on the development system I (not the executable) I start the application and after the variables are initialized and every process has started and are running , the CPU usage is raised around 90 - 100%. After a few days investigating the reason of this, I realized thay when I change the view on the screen to another view, for example the block diagram of the application, while the application is still running, the CPU usage goes around 15 - 25%. I've tried these many times changing the view from Front panel to Block Diagram and viceversa and the result is always the same: Front Panel= around 100%; Block diagram or another view (other applications MMIs, or Block Diagrams, etc.)= around 20%.
    Another thing that I realized is that the other view (different to front panel) has to fill the entire screen to work the way I'm telling before.
    When I build and run the executable, the usage of the CPU is the same... (around 100%), but I can't see any other application, because the application built is the shell of the OS, so no other views are available.
    I don't know if there's some other consideration to take into account about the HMI when creating an application, and I'll appreciate very much your help.
    Thanks in advance!
    Ignacio von Unger

     From http://100cpuusage.blogspot.com/
    100 Percent CPU Usage when you run programs after you install Windows XP Service Pack 2
    CPU Usage 100% Symptoms
    When you run some programs, the CPU Usage meter in Task Manager may indicate CPU Usage 100%. When CPU utilization reaches 100 percent, programs will run very slowly or stop responding (hang) and your computer is freezing or crashing.
    Noteress CTRL+ALT+DEL to view CPU utilization, click Task Manager, and then click the Performance tab.
    These symptoms occur after you install Microsoft Windows XP Service Pack 2 (SP2).
    CPU Usage 100% Cause
    These problem occurs because of the user interface code that is included in Windows XP SP2. The high CPU utilization is caused by the additional overhead that occurs when the IsWindow function is called by the user interface code.
    RESOLUTION
    Hotfix information
    A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.
    To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:
    http://go.microsoft.com/?linkid=6294451
    Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:
    http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)
    Prerequisites
    To apply this hotfix, you must have Windows XP SP2 installed.
    Restart requirement
    You must restart the computer after you apply this hotfix.
    Hotfix replacement information
    This hotfix does not replace any other hotfixes.
    File information
    The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel. Date Time Version Size File name
    30-Mar-2005 19:53 5.1.2600.2643 577,024 User32.dll
    30-Mar-2005 01:30 5.1.2600.2643 1,836,544 Win32k.sys
    if you still do not know how to Fix CPU Usage 100%?
    I suggest you try targeted software - registry cleaner to fix cpu usage 100%
    Because there are many cases causing high cpu utilization.
    1. If you do a lot of web surfing and are concerned about spyware, adware infecting your machine, they will cause system crashes and CPU utilization reaches 100 percent. Some good registry cleaner has the function of spyware & adware removal.
    2. You install many beta version of the software, Drivers are not certified, which resulted in many errors, you get high cpu usage.
    3.100% CPU Usage while you use Internet Explorer
    4. many unneed Startup Program.
    5.Others PC Errors. - DLL errors, runtime errors, Windows-Installer Errors, Windows Startup Errors,paths Broken DLLs, OCX, and ActiveX Components all will cause 100% cpu usage. Your PC will run very slowly.
    Registry cleaner can do a complete scan of your entire file system and registry in under 2 minutes! Fix High Cpu Usage. Improve PC Speed By Up to 70%!
    http://www.100-cpu-usage.com/ suggest you to download registry cleaner to fix 100% cpu usage too.
    PCErrorsfixer.com - Top 3 Windows Registry Cleaners, Improve PC Performance,5 Star Rated. Fix 100% CPU Usage, Runtime Error, DLL Error,Windows Startup Errors,Internet Explorer Errors, Speed Up your slow PC.

  • Repaint() causes 100%cpu useage

    im not sure where ive gone wrong but its using 100% of cpu. source below (a little messey - im a beginner)
    its a graphing extention to an applet - thanks for the help
    public class MyCanvasGraph extends Canvas {
    public void update(Graphics g) {
    paint(g);
    int graph1X = 0;
    int graph1Y = 20;
    int graph2X = 0;
    int graph2Y = 175;
         public void paint(Graphics g){     
         String whichStation = Team.convertInt(monitorSelected);
    int scaleBY = 10 ;
    int scaleBY2 = 100 ;
    int[] dataRecieved = Team.getRecieved();
         int timeForGraph = Team.timeCounter();
         int[] dataWaiting = Team.getWaiting();
    timeForGraph=timeForGraph/500;     
    // retrieve values of data at A - H and Scale to fit graph by value of scaleBY
    if (timeChange!=timeForGraph) { // only update graph if data has changed - allows applet to run smoother
         if ( monitorChange == monitorSelected ) { // make sure the monitored station is the same otherwise graph needs to be cleared
              System.arraycopy(graphArrayWaiting, 1, graphArrayWaiting, 0, 240);
    graphArrayWaiting[239] = dataWaiting[monitorSelected]/scaleBY ;
    System.arraycopy(graphArrayRecieved, 1, graphArrayRecieved, 0, 240);
    int ammountRecieved = dataRecieved[monitorSelected]/scaleBY2 ;
    if ( ammountRecieved>=1000) {ammountRecieved=1000;}
    graphArrayRecieved[239] = ammountRecieved ;
    else { monitorChange = monitorSelected;
         for(int t=0;t<=240;t++){
    graphArrayWaiting[t]=0;
    graphArrayRecieved[t]=0;}
    // KEY
    g.setColor(Color.blue);
    g.fillRect( 25, 147 ,12,12);
    g.drawString("Data Waiting", 40, 158);
    g.setColor(Color.black);
    g.drawRect( 25, 147 ,12,12);
    g.setColor(Color.red);
    g.fillRect( 125, 147 ,12,12);
    g.drawString("Data Sent", 140 , 158);
    g.setColor(Color.black);
    g.drawRect( 125, 147 ,12,12);
    g.setColor(new Color(192,192,192));
    g.drawRect( 20, 143 ,180,20);
         // TOP GRAPH
              g.setColor(Color.black);
              g.drawLine(graph1X + 20, graph1Y+10, graph1X + 20, graph1Y + 110); // draw Y axis
              g.drawLine(graph1X + 20, graph1Y + 110, graph1X + 260, graph1Y + 110); // draw X axis
              g.drawString("T I M E", graph1X + 225 , graph1Y + 125); // write TIME
              g.drawString("D", graph1X + 9 , graph1Y + 40); // write DATA
              g.drawString("A", graph1X + 9 , graph1Y + 60);
              g.drawString("T", graph1X + 9 , graph1Y + 80);
              g.drawString("A", graph1X + 9 , graph1Y + 100);
         // BOTTOM GRAPH     
    g.drawLine(graph2X + 20, graph2Y, graph2X + 20, graph2Y + 100); // draw Y axis
              g.drawLine(graph2X + 20, graph2Y + 100, graph2X + 260, graph2Y + 100); // draw X axis
              g.drawString("A", graph2X + 30 , graph2Y + 125); // WRITE a - h
              g.drawString("B", graph2X + 60 , graph2Y + 125);
              g.drawString("C", graph2X + 90 , graph2Y + 125);
              g.drawString("D", graph2X + 120 , graph2Y + 125);
              g.drawString("E", graph2X + 150 , graph2Y + 125);
              g.drawString("F", graph2X + 180 , graph2Y + 125);
              g.drawString("G", graph2X + 210 , graph2Y + 125);
              g.drawString("H", graph2X + 240 , graph2Y + 125);     
              g.drawString("D", graph2X + 9 , graph2Y + 30); // write DATA
              g.drawString("A", graph2X + 9 , graph2Y + 50);
              g.drawString("T", graph2X + 9 , graph2Y + 70);
              g.drawString("A", graph2X + 9 , graph2Y + 90);
    g.setColor(Color.white);
    g.fillRect(graph1X + 21, graph1Y -19,239,129); // Get rid of previous lines on graph 1
    g.fillRect(graph2X + 21, graph2Y +1 ,239,99); // Get rid of previous lines on graph 2
    g.setColor(new Color(192,192,192)); // set bar graph grid colour to grey
    for(int s=1;s<=10;s++){ // draws 10 lines to make a grid for graph 1
    g.drawLine(graph1X + 20, graph1Y + 10*s , graph1X + 260, graph1Y + 10*s );
    for(int s=1;s<=10;s++){ // draws 10 lines to make a grid for graph 2
    g.drawLine(graph2X + 20, graph2Y + 10*s - 10, graph2X + 260, graph2Y + 10*s - 10);
         // WHICH STATION IS BEING MONITORED
         g.setColor(Color.black);
    g.drawRect( 130, 12 ,120,13);
    g.setColor(Color.blue);
    g.drawString("Monitoring Station ", 137 , 23);
    g.setColor(Color.red);
    g.drawString(whichStation, 238 , 23);
    g.setColor(Color.blue); // set line colour to blue
    // PLOT GRAPH ONE LINE GRAPH
    for(int t=1;t<=2;t++){          
         timeChange=timeForGraph ;// see if the tame hs changed     
         for(int s=1;s<=238;s++){
              g.setColor(Color.red);
              g.drawLine(graph1X+20+s, 130-graphArrayRecieved[s], graph1X+s+21, 130-graphArrayRecieved[s+1]);
              g.setColor(Color.blue);
              g.drawLine(graph1X+20+s, 130-graphArrayWaiting[s], graph1X+s+21, 130-graphArrayWaiting[s+1]);
              // prepare data for graph 2
    int dataAt ;
    int recievedAt ;
    int dataAtA = dataWaiting[1];
    dataAtA = dataAtA/scaleBY;
    int recievedAtA = dataRecieved[1];
    recievedAtA = recievedAtA/scaleBY2;
    int dataAtB = dataWaiting[2];
    dataAtB = dataAtB/scaleBY;
    int recievedAtB = dataRecieved[2];
    recievedAtB = recievedAtB/scaleBY2;
    int dataAtC = dataWaiting[3];
    dataAtC = dataAtC/scaleBY;
    int recievedAtC = dataRecieved[3];
    recievedAtC = recievedAtC     /scaleBY2;
    int dataAtD= dataWaiting[4];
    dataAtD = dataAtD/scaleBY;
    int recievedAtD = dataRecieved[4];
    recievedAtD = recievedAtD/scaleBY2;
    int dataAtE = dataWaiting[5];
    dataAtE = dataAtE/scaleBY;
    int recievedAtE = dataRecieved[5];
    recievedAtE = recievedAtE/scaleBY2;
    int dataAtF = dataWaiting[6];
    dataAtF = dataAtF/scaleBY;
    int recievedAtF = dataRecieved[6];
    recievedAtF = recievedAtF/scaleBY2;
    int dataAtG = dataWaiting[7];
    dataAtG = dataAtG/scaleBY;
    int recievedAtG = dataRecieved[7];
    recievedAtG = recievedAtG/scaleBY2;
    int dataAtH = dataWaiting[8];
    dataAtH = dataAtH/scaleBY;
    int recievedAtH = dataRecieved[8];
    recievedAtH = recievedAtH/scaleBY2;
    for(int s=1;s<=8;s++){  
    switch (s) {
    case 1 : dataAt = dataAtA;
              recievedAt = recievedAtA ;     
              break ;           
    case 2 : dataAt = dataAtB;
    recievedAt = recievedAtB ;
    break;
    case 3 : dataAt = dataAtC;
              recievedAt = recievedAtC ;
    break;
    case 4 : dataAt = dataAtD;
    recievedAt = recievedAtD ;
    break;
    case 5 : dataAt = dataAtE;
    recievedAt = recievedAtE ;
    break;
    case 6 : dataAt = dataAtF;
    recievedAt = recievedAtF ;
    break;
    case 7 : dataAt = dataAtG;
    recievedAt = recievedAtG ;
    break;
    case 8 : dataAt = dataAtH;
    recievedAt = recievedAtH ;
    break;
    default : dataAt = dataAtA;      
              recievedAt = recievedAtA ;
              break ;
    }// end case
         // PLOT GRAPH 2 (BAR GRAPH)
         g.fillRect( graph2X - 5 + 30*s , graph2Y + 100 - dataAt, 10, dataAt ); // bar for A
    g.setColor(Color.red);
         g.fillRect( graph2X +5 + 30*s , graph2Y + 100 - recievedAt, 10, recievedAt ); // bar for A
         g.setColor(Color.blue);
    } // end loop
    } //end if statement (refresh control)
    } // closes for loop
    repaint();
    } // closes paint
         } // closes MyCanvasGraph

    This is the second %100 cpu utilization message I see in less than 24 hours.
    I recommend you start with the basics, and learn about about paint() repaint() logic, if you have to wonder why calling repaint() is not necessary inside of paint() you need to learn the basics first.
    http://java.sun.com/docs/books/tutorial/uiswing/painting/overview.html
    http://java.sun.com/products/jfc/tsc/articles/painting/index.html
    Please read these two links.

  • 100% CPU use making me want to cry with 3 browsers

    I am using an Athlon XP 2500+ laptop/notebook with 1gb RAM
    and am having high CPU problems with Firefox 2.0.0.3 (no
    extensions), Opera 9.2 and IE.7.
    I have uninstalled and reinstalled Flash and Shockwave and
    uninstalled my AV, HIPS and firewall - temporarily!
    The following web slideshow makes any browser reach 100% CPU
    and causes the mouse to seriously lag on each browser.
    http://www.koat.com/slideshow/news/13245211/detail.html
    This high usage is constant, even when the mouse is not being
    touched and the page is not moving or playing music, etc.
    Strangely, if the controls of the slideshow are scrolled off
    the screen, then CPU returns to normal: <10%
    So I only get slowdown when I can SEE the buttons that move
    on to the next slide!
    Can anyone help?

    Hi,
    Welcome to the Discussions.
    This thread, Could it be the Logic Board?, is about the same problem. You may want to try the drive in an external firewire enclosure.
    John

Maybe you are looking for

  • Issue with multiple application installation and server share

    Hi, SCCM 2007 SP2 R3 ICP2 All servers W2K8R2 I am having an issue with software installs.  When using a variable for multiple applciation installs, I get access errors when the applications go to install.  It appears to be a multiple connection issue

  • Battery drains very fast on 4S after upgrading to iOS 6

    My phone battery was performing reasonably fine before the iOS 6. Now: The battery gets drained very fast. It used to last for 24hrs (on average) on the previous OS but now does not work for than 14hrs. The phone gets switched off when the battery re

  • Address Book too simplistic

    I don't understand why AB is so simplistic. No quick fill, doesn't even add a comma after a City when formatting for printing, etc. With all the other address books on the market (Now contact for instance) I would have thought the developers would ha

  • Greek Programming

    When is FIOS going to add more greek programming?  There are more greek channels out there and I do not want to get satellite TV.

  • External USB HD won't mount anymore

    I have a 1 TB HD that has all my media on it and today it's not connecting. In the past there have been connection issues such as: when I brought my computer and external to a friend's house it wouldn't mount at first, and after restarting a few time