Announcement

Collapse
No announcement yet.

Occasional hang-ups

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
  • #1

    Occasional hang-ups

    Have encountered several freeze-ups over the past few days: main chart and three or four spawned charts all stopped and totally frozen after running undisturbed for a while. Had to use Task Manager to kill applet then restart from scratch. There is no way to just refresh it as in the legacy LC. New applet seems more stable than the old most of the time, but it still can fail unexpectedly.
    Tags: None
  • #2
    Livecharts "Freeze"

    Hi There,

    Thanks for your forum post.

    Could you please check through the following:

    Our program utilizes Java Applets to give you the best Quote and Charting experience. If you currently have Sun Java® Virtual Machine installed, it may be corrupted or need to be updated. Uninstall all versions of Java Runtime Environment currently installed on your system. You will then need to download and install Sun Java® Runtime Environment by going to http://www.java.com/en/download/download_the_latest.jsp and click on the Begin Download button. Windows XP SP2 users: if you encounter an error, look at the top of the page for a yellow bar that reads "This site might require the following ActiveX control: 'J2SE Runtime Environment 6.0 Update 3' from 'Sun Microsystems, Inc.'. Click here to install..." Click the yellow bar and choose "Install ActiveX Control..." to allow installation to proceed. When the installation window opens, select Typical Installation and click on the Accept button. PLEASE NOTE: During the installation, you may be prompted to install the Google Toolbar for Internet Explorer. If you choose to install this, a pop up blocker is installed as a component of the toolbar. This popup blocker must be disabled or modified for the program to function properly. Per the Google Help section, “To add a site to your popup blocker white list, visit the site and press the Popup Blocker button. The button text will change to read "Allow site popups," indicating that the Popup Blocker is disabled on the site in question.”

    In order to fully experience the power of the application, the use of cookies is required. To ensure that you can accept cookies. (From your menu bar choose Tools -> Internet Options. Click on the "Privacy" tab. Please ensure that you are set at a Medium Privacy level. You may have to click on the "Default" button to show the privacy slider bar again. You can choose either Medium, Medium-Low, or Low for security settings. We suggest that you choose Medium security.

    Popup blockers and privacy software must be disabled for the program to open properly. When the program opens, it automatically attempts to open a 2nd window. Pop-up blockers may disallow this from happening. A pop-up blocker could be installed as a stand alone program, a feature of a firewall, a feature of a virus protection program, an add-on to a browser toolbar, or as part of the Windows operating system. Due to the myriad different installations and configurations that are available, we have no way of identifying the one installed on your system. You can test your machine to see if a pop-up blocker is installed at the following link: http://www.popuptest.com/ and click the Multi-PopUp Test link.

    - Clear your cache: Open your browser, click Tools - Internet Options. From the General tab, click "Delete All Files" under the Temporary Internet Files section.
    - Delete all cookies: Open your browser, click Tools - Internet Options. From the General tab, click "Settings" under the Temporary Internet Files section. Select "View Files", then select all the files shown and delete them.

    Please do not use any shortcuts/bookmarks when accessing your login page:

    The program requires 128K of broadband internet bandwidth in order to provide real time streaming data and news. The 128K of bandwidth must be maintained on both the upload and download side of the connection. If your connection speed fluctuates below the minimum requirement of 128K, either inbound or outbound, your pc will not be able to communicate with our servers properly and your workspaces will not open, update or save correctly. If your internet connection cannot maintain the minimum requirement, the program will not function properly and our technical support team will be unable to support the product. If you would like to test your connection speed, go to http://www.speakeasy.net/speedtest.

    In order to function from behind a firewall, the program requires that TCP port 2812 is open for access. Ports are logical channels through which traffic enters or leaves your computer. Your computer has thousands of ports, each identified by a number. Whenever another computer sends a message to your computer, it addresses that message to a specific port. For example, a server delivering a Web page to your browser, using the Hypertext Transfer Protocol (HTTP), traditionally sends to port 80.For more specific information regarding working from behind a firewall, go to http://kb.esignalcentral.com/article...icle=2798&p=15

    Kind Regards,

    Comment

    • #3
      No freeze-ups now

      Have encountered no hang-ups over the past several days. Though the good advice given below did not apply in my case, there is one thing I did change since my last freeze: I kept the IE new.quote.com login window active, though minimized; it had been closed when I had my freeze-ups, leaving just the applet running with no IE support.

      Does that matter??

      Comment

      • #4
        Freezing again

        Well I spoke too soon: today I had two freeze-ups affecting all four applet windows. As happened with other posters, one of my two CPU cores was running near 100%, giving overall usage a little over 50% (normally would be from 1 to 4%). Killed the IE process to restore my system to normal, then started a new IE process and new LiveCharts session. As with the legacy LiveCharts, one has to keep an eye on the time displayed on the applet to tell whether or not it is still running.

        Comment

        • #5
          Same things happend to me EVERYDAY When is the new LiveChart ever going to be fixed

          Comment

          • #6
            The 100% CPU usage problem is still being investigated, but as yet, it hasn't been replicated in house via computers on the network or on DSL. Via Vista or XP (using IE 7.0, IE 6.0 and firefox on XP, and IE 7.0 and Firefox on Vista).

            I'll pass along any information that I receive on this issue.

            Comment

            • #7
              I was able to induce the 100% CPU this morning by investigating what happens after the 3 java errors on array occurred (see other thread).

              I went through the following shutdown and restart of the four secondary charts and wanted to watch memory usage. Here are the before and after for each cycle and the last cycle cause the 100% spike....

              100MB ->124MB (this was the difference in before/after the 3 errors)
              124MB -> 140MB (this was change after drop 4 and readd 4)
              140 -> 150MB (same cycle)
              150 -> freeze (CPU pegged at 100% during attempt to add)

              The array out of bounds error appears connected to attempts to reconnect secondary charts after main chart failure and reconnect.

              I tried the cycle technique with NO errors in the log and got steady creep in memory usage (leak), but did not get the 100% after 6 full cycles.

              I have noted that better stability seems to occur with a totally Empty portfilio, i.e. the more Subscribed symbols, the higher the latency (possibly) for server retrieves and the higher the other disconnect errors, like the following:

              Communication error: java.net.SocketException: Resource temporarily unavailable: recv failed

              That error and the array error have some interesting discussion at the Java Development Group Forum.

              It might be a good idea to see if the problems increase with network latency, i.e. physical distance/router hops from the server. If you're at HQ or near the server, that might translate to no network latency and stable operation.

              Edit: Still stable with Nasdaq heartbeat on Main, 4 secondary charts (solid), and an Empty Portfolio, i.e. 5 symbols subscribed to service showing on Console log. We may actually have something working here. I should add that the Java Console log looks reasonably clean too, no errors. The socket 2812 session is unbroken since 12:28:57 EDT.
              Last edited by dannol48; 04-23-2008, 11:27 AM.

              Comment

              • #8
                Knock Knock....

                I pinged (until halted) your front door, so your engineers could look at network latency from my location to yours. My front door (last router) is ( 71.74.88.1 ), so you can verify the hops with a tracert. ISP is Insight sub-ing service from TimeWarner Roadrunner. Here's the session....

                Microsoft Windows XP [Version 5.1.2600]
                (C) Copyright 1985-2001 Microsoft Corp.

                C:\

                Pinging 199.217.10.233 with 32 bytes of data:

                Reply from 199.217.10.233: bytes=32 time=84ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=81ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=77ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=78ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=81ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=76ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=80ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=79ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=75ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=79ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=78ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=81ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=78ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=78ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=79ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=80ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=77ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=113ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=126ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=76ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=79ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=76ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=80ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=78ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=87ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=78ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=78ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=77ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=78ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=78ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=133ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=149ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=219ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=90ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=76ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=75ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=79ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=76ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=79ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=77ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=78ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=80ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=79ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=83ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=81ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=77ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=80ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=79ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=78ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=79ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=77ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=77ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=78ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=81ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=79ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=77ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=84ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=77ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=78ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=77ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=77ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=77ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=78ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=80ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=77ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=78ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=77ms TTL=241
                Reply from 199.217.10.233: bytes=32 time=83ms TTL=241

                Ping statistics for 199.217.10.233:
                Packets: Sent = 68, Received = 68, Lost = 0 (0% loss),
                Approximate round trip times in milli-seconds:
                Minimum = 75ms, Maximum = 219ms, Average = 83ms
                Control-C

                Comment

                • #9
                  I have forwarded this information to engineering as they continue to investigate this issue.

                  Comment

                  • #10
                    Freeze event

                    Re freeze with high CPU usage rate.

                    Today I had the charts running all day with no interruption and continuing after-hours (to watch AAPL earnings response). Then a regularly-scheduled spy-ware scan by my ZoneAlarm Suite took place and left a scan results window on top of the still running charts (main chart and two spawned windows). When I clicked on the "Done" button to acknowledge the scan results the two spawned charts turned blank and the main chart stopped; Task Manager showed my dual core CPU usage at 55%, divided unevenly between the two cores (roughly 30%/80%). This 50% usage was entirely attributed to the IE process supporting LiveCharts. Memory usage and VM Size was not larger than before failure, though it had been slowly increasing throughout the day from 34M/79M to 105M/120M, roughly.

                    So it seems that the charts are more susceptible to failure when another window is placed on top of them and moved or closed. I noticed this before on two occasions when I moved a Firefox window around on top of the charts, so I now avoid doing this as much as possible (I have two monitors).
                    Last edited by rduclos; 04-23-2008, 05:14 PM.

                    Comment

                    Previous template Next
                    Working...
                    X