#20 ✓resolved
jean-pierre

CheetahWatch crashes on startup

Reported by jean-pierre | September 2nd, 2009 @ 06:35 PM

Hi,

I have just upgraded my computer to snow leopard , I have notice that I couldn't launch "CheetahWatch" ; It look it couldn't start.

Cordially Jean-Pierre

Comments and changes to this ticket

  • Patrick Quinn-Graham

    Patrick Quinn-Graham September 14th, 2009 @ 07:03 AM

    • State changed from “new” to “open”

    Hi,

    Please try upgrading to 10.6.1, as I'm not able to reproduce this problem under such.

    If you continue to see crashes, please send me any crash logs that appear in your Library/Logs/Crash Logs folder.

    thanks,
    Patrick

  • jean-pierre

    jean-pierre September 14th, 2009 @ 05:09 PM

    Hi

    I have just done a new test with 10.6.1 , but I still have the crash. I joint with this ticket the last crash report

    Cordially Jean-pierre

  • Dan Milne

    Dan Milne September 15th, 2009 @ 09:41 AM

    Hi there,
    I've the same problem as the reporter. Application doesn't start - don't even see it bounce in the dock.

    Cheers,
    Dan

  • Stephen Harrington

    Stephen Harrington September 15th, 2009 @ 07:44 PM

    I'm also seeing this behaviour, I'm on 10.6.1 and CheetahWatch 1.3 doesn't start at all, no bounce on dock, no error message. Crash Report attached.

    Cheers,

    Stephen

  • Lachlan Wells

    Lachlan Wells October 4th, 2009 @ 06:10 PM

    • Tag set to “leopard, snow”

    This issue also occurs with my setup, Mac OS X 10.6.1 and CheetahWatch 1.3.

    Attached is my crash report :)

    Thankyou,
    Lachlan Wells

  • Shez

    Shez October 5th, 2009 @ 09:21 AM

    Hi, same problem here.

    I upgraded to 10.6.1, in case that would fix the problem, but no luck. The .app file doesn't open at all, and I can briefly see CrashReporter running in the background.

    I've attached my crashlog.

    Rgds

  • kitsonk

    kitsonk October 29th, 2009 @ 02:37 AM

    Just as a way of information, I have a Core Duo MacBook Pro 13" which basically means that OS X 10.6.1 attempts to run everything in 64-bit mode. I did a Get Info on the .app (Cmd-I) and ticked the "Open In 32-bit Mode" and then the application would launch and I saw the application in the titlebar and could attempt to connect.

    I am still having problems connecting, but I am unsure if this is due to some other issue, because attempting to connect manually using the Network Control panel also fails exactly in the same fashion.

    I suspect the situations where it was fixed with 10.6.1 were due to the fact that it was probably being run on older hardware that doesn't support 64-bit.

    I have tried to re-compile the code as a 64-bit Universal .app but it maybe worth a go.

  • Patrick Quinn-Graham

    Patrick Quinn-Graham November 16th, 2009 @ 07:08 PM

    Apologies for my delay in sorting this issue - I've had a number of personal issues (one parent passing away, the other undergoing chemotherapy for a similar cancer, and myself ending up in the emergency 4 times recently).

    Please try downloading a v1.3.2b2 build from:
    http://static.patrick.geek.nz/cheetahwatch/CheetahWatch_1.3.2b2.zip

    And report back with your experience.

    thanks,
    Patrick

  • Horstbert

    Horstbert November 26th, 2009 @ 12:22 AM

    Hey,
    I'm very sorry for your personal issues! Thanks for keeping up your good work! I installed the Beta, here are my experiences (MB C2D 1,83, 10.6.2): CheetahWatch starts up normally again. It detects my Modem (Unlocked Vodafone K3565 a.k.a. Huawei E160x) and shows signal strength and connection mode in the taskbar. However, it fails to start a connection, I have to connect via OS X' network prefpane. Once the connection is established, the bars in the taskbar go blue as supposed to and the menu says 'connected'. If i detach the Modem, it doesn't react and still shows the last signal strength until i restart the program. One more thing: The data counter in the status window works for the actual transfer, the 'Total'-counter, however, adds like 100MB per second to the ammount. Kinda funny, I wish for 3G networks being really that fast! ;) Ah yeah, the carrier name doesn't show up either.

    Hope this is a little help for you!

    Greetings from Germany!

  • Horstbert

    Horstbert November 27th, 2009 @ 09:52 PM

    A little correction... Today connecting via CheetahWatch worked, the other problems, however, remained. Additionally, CW has nearly 100% CPU usage, causing the fans to go crazy and the battery to last for like only an hour.

  • Nick Hibma

    Nick Hibma February 18th, 2010 @ 07:16 PM

    • Title changed from “CheetahWatch” to “CheetahWatch crashes on startup”

    Crash on start seems to have been resolved.

    High CPU usage is a duplicate of bug #15.

  • Patrick Quinn-Graham

    Patrick Quinn-Graham March 24th, 2011 @ 01:52 PM

    • State changed from “open” to “resolved”
    • Milestone order changed from “0” to “0”

    Resolved in 1.4

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป

This little mac app provides you with signal strength, network mode (GRPS/WCDMA/HSDPA), network name control over your connection, and statistics about your current connection (current throughput, total data transferred, connection time). It does this through a little icon in your menu bar (and a bigger window, if you want to see it), and also helps you keep track of your usage - no need for a nasty surprise from your provider.

People watching this ticket

Attachments

Tags

Referenced by

Pages