Loading Profile...
Rescue time won't even take password before crashing
So I feel like a bit of a disaster; Using the beta client I had an issue that after it crashed I completely stopped logging data. Previously I'd fixed this after talking to Joe by deleting rescuetime.cfg and moving on. After noticing the lost data (if need be, I have the log file with the requested logging level which has the upload errors beginning after the crash), I deleted the rescutime.cfg. Now the beta client crashes on startup:
Process: RescueTime [54751]
Path: /Users/username/Applications/RescueTime.app/Contents/MacOS/RescueTime
Identifier: com.rescuetime.RescueTime
Version: 2.0.0 (2.0.0.525)
Code Type: X86 (Native)
Parent Process: launchd [166]
Date/Time: 2009-03-25 21:16:18.134 -0600
OS Version: Mac OS X 10.5.6 (9G55)
Report Version: 6
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x000000000000010f
Crashed Thread: 0
Thread 0 Crashed:
0 libobjc.A.dylib 0x902b22d3 flush_marked_caches + 106
1 libobjc.A.dylib 0x902b5435 _read_images + 996
2 libobjc.A.dylib 0x902ab17d map_images + 6242
3 dyld 0x8fe04af8 dyld::notifyBatchPartial(dyld_image_states, bool, char const* (*)(dyld_image_states, unsigned int, dyld_image_info const*)) + 744
4 dyld 0x8fe1063b ImageLoader::link(ImageLoader::LinkContext const&, bool, bool, ImageLoader::RPathChain const&) + 251
5 dyld 0x8fe051ae dyld::link(ImageLoader*, bool, ImageLoader::RPathChain const&) + 158
6 dyld 0x8fe0bc33 dlopen + 691
7 libSystem.B.dylib 0x92c38202 dlopen + 66
8 com.apple.CoreFoundation 0x9065b863 _CFBundleDlfcnLoadBundle + 307
9 com.apple.CoreFoundation 0x9065c187 _CFBundleLoadExecutableAndReturnError + 567
10 com.apple.Foundation 0x9186cb73 _NSBundleLoadCode + 259
11 com.apple.Foundation 0x9186c2db -[NSBundle loadAndReturnError:] + 331
12 com.apple.Foundation 0x9186c18a -[NSBundle load] + 42
13 com.apple.Foundation 0x9186c14d -[NSBundle principalClass] + 45
14 com.apple.AppKit 0x967f27fd -[NSInputManager _loadBundle] + 137
15 com.apple.AppKit 0x967f1f9a -[NSInputManager initWithName:host:] + 2639
16 com.apple.AppKit 0x9634a525 +[NSInputManager initialize] + 1134
17 libobjc.A.dylib 0x902a88b8 _class_initialize + 367
18 libobjc.A.dylib 0x902a7239 _class_lookupMethodAndLoadCache + 81
19 libobjc.A.dylib 0x902b76d6 objc_msgSend + 102
20 com.apple.AppKit 0x963493a3 -[NSApplication run] + 83
21 com.rescuetime.RescueTime 0x0004491b 0x1000 + 276763
22 com.rescuetime.RescueTime 0x00043867 0x1000 + 272487
23 com.rescuetime.RescueTime 0x0003132f 0x1000 + 197423
24 com.rescuetime.RescueTime 0x00024c43 0x1000 + 146499
25 com.rescuetime.RescueTime 0x00002432 0x1000 + 5170
26 com.rescuetime.RescueTime 0x00002359 0x1000 + 4953
Thread 1:
0 libSystem.B.dylib 0x92c2f2e6 mach_wait_until + 10
1 libSystem.B.dylib 0x92ca63ad nanosleep + 314
2 libSystem.B.dylib 0x92cb6eab sleep + 63
3 com.rescuetime.RescueTime 0x0003f4ac 0x1000 + 255148
4 com.rescuetime.RescueTime 0x00025157 0x1000 + 147799
5 com.rescuetime.RescueTime 0x0006d94d (anonymous namespace)::system_error_category::~system_error_category() + 3965
6 libSystem.B.dylib 0x92c60095 _pthread_start + 321
7 libSystem.B.dylib 0x92c5ff52 thread_start + 34
Thread 2:
0 libSystem.B.dylib 0x92c2f2e6 mach_wait_until + 10
1 libSystem.B.dylib 0x92ca63ad nanosleep + 314
2 libSystem.B.dylib 0x92cb6eab sleep + 63
3 com.rescuetime.RescueTime 0x00002b27 0x1000 + 6951
4 com.rescuetime.RescueTime 0x00025157 0x1000 + 147799
5 com.rescuetime.RescueTime 0x0006d94d (anonymous namespace)::system_error_category::~system_error_category() + 3965
6 libSystem.B.dylib 0x92c60095 _pthread_start + 321
7 libSystem.B.dylib 0x92c5ff52 thread_start + 34
Thread 3:
0 libSystem.B.dylib 0x92c2f2e6 mach_wait_until + 10
1 libSystem.B.dylib 0x92ca63ad nanosleep + 314
2 libSystem.B.dylib 0x92cb6eab sleep + 63
3 com.rescuetime.RescueTime 0x00002e42 0x1000 + 7746
4 com.rescuetime.RescueTime 0x00025157 0x1000 + 147799
5 com.rescuetime.RescueTime 0x0006d94d (anonymous namespace)::system_error_category::~system_error_category() + 3965
6 libSystem.B.dylib 0x92c60095 _pthread_start + 321
7 libSystem.B.dylib 0x92c5ff52 thread_start + 34
Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x000000ff ebx: 0x902b2274 ecx: 0x001ba000 edx: 0x0012c300
edi: 0xbfffe8ac esi: 0xa002e5e4 ebp: 0xbfffe8c8 esp: 0xbfffe880
ss: 0x0000001f efl: 0x00010206 eip: 0x902b22d3 cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037
cr2: 0x0000010f
I’m confused
1
person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Thanks for the bug report Matt - could you send that debug_log to us at team AT rescuetime.com? I'm curious to see if you are experiencing a similar issue to the first logging problem you had.
We are trying to track down a problem where it appears that the hostname is changing while RescueTime is running, and I think that could be what we are seeing here.
We're knocking out a lot of bugs on the beta client with all of this great feedback from you guys - we really appreciate your patience while we try to stabilize the software!
I’m thankful for great testers!
1 person says
this solves the problem
-
Inappropriate?So this problem seems to be back: Same crash report as before. And as before it showed up after I attempted to restart the client after realizing it hadn't been sending its data. I have a 400kb log in the log directory, as well as a 200kb debug.log if you'd like it. This time removing the Rescuetime.com data directory is not helping.
Perhaps something worth doing would have a bit of visual indication if update uploading fails on the server; A little X in the menu item would help tonnes. -
Inappropriate?Matt, send us both of the log files that you have ( team AT rescuetime.com ) - I can run those through our test system to track down what inside of them is causing the crash and then make sure our code traps for that situation.
We have some changes that we're getting ready to push our with the Mac version that uses a different method for tracking the computer name and username that should hopefully be a lot more stable in environments where those change frequently.
Thank you!
EMPLOYEE
