[chandler-users] Crash on launch

[Grant Baillie]

On 23 May, 2008, at 16:09, Lisa Dusseault wrote:

> I'm not sure the last shutdown was clean, but I didn't notice  
> anything amiss either.

Hopefully, that means the auto-export ran to completion.

> Chandler 0.7.6 also crashes immediately.   The crashed thread  
> reports quite differently though:
>
> Thread 0 Crashed:
> 0   libdb-4.6.dylib               	0x0bf2fb3c __txn_prepare + 2387
> 1   libdb-4.6.dylib               	0x0bf2ff42 __txn_begin + 297
> 2   libdb-4.6.dylib               	0x0bf302a9 __txn_begin_pp + 363
> 3   c.so                          	0x0bdc3253 _t_txn_init + 51  
> (txn.c:114)
> 4   c.so                          	0x0bdc158e t_env_txn_begin + 217  
> (env.c:359)
> ...

This crash is inside Berkeley DB code. Actually, the above trace was  
in your original crash log, too, but in one of the non-crashing  
threads. That usually means one of the threads is writing junk to  
memory, causing a random thread to crash soon thereafter.

If you are comfortable sending me a copy of your

~/Library/Application Support/Open Source Applications Foundation/ 
Chandler/xxxxxxxxx.default

I could certainly take a look. In the meantime, the workaround is:

- Back up that folder
- Launch Chandler, and immediately hold down the Control key to get  
the Startup Options dialog.
- Choose "Discard all my data and start with a fresh repository", and  
click OK.
- Use the "File >> Import >> Reload Chandler Data from .chex File"  
menu to reload your data from the file backup.chex in the above folder.

Cheers,
--Grant


> On May 23, 2008, at 3:38 PM, Grant Baillie wrote:
>
>>
>> On 23 May, 2008, at 14:06, Grant Baillie wrote:
>>
>>> When you say "crash", do you mean you're getting the OS crash  
>>> dialog? Or the app just quits?
>>
>> It turns out to have been the OS crash dialog. From the trace in  
>> the crash (excerpted below), I'm not sure what it going on: It  
>> looks like possibly a corrupted binary, or some kind of OS virtual  
>> memory/shared library problem. It could very well go away after a  
>> reboot, or a re-download of the app itself.
>>
>> If your previous quit (before all this crashiness) was  
>> "clean" (i.e. the app quit normally and wrote a complete  
>> backup.chex file in the folder below), I would back up the folder
>>
>> ~/Library/Application Support/Open Source Applications Foundation/ 
>> Chandler/xxxxxxxxx.default
>>
>> (just in case) and then try 0.7.6.
>>
>> --Grant
>>
>>> Thread 1 Crashed:
>>> 0   dyld                          	0x8fe0e46c  
>>> ImageLoader::containsAddress(void const*) const + 60
>>> 1   dyld                          	0x8fe06f22  
>>> dyld::bindLazySymbol(mach_header const*, unsigned long*) + 226
>>> 2   dyld                          	0x8fe18b6f  
>>> stub_binding_helper_interface2 + 21
>>> 3                                 	0x106dfc28 jio_fprintf + 248
>>> 4                                 	0x1076aeeb JVM_RaiseSignal +  
>>> 449931
>>> 5                                 	0x10769506 JVM_RaiseSignal +  
>>> 443302
>>> 6                                 	0x105a2ffd 0x104a4000 + 1044477
>>> 7                                 	0x105a2afd 0x104a4000 + 1043197
>>> 8                                 	0x105a2a9b 0x104a4000 + 1043099
>>> 9                                 	0x105a2929 0x104a4000 + 1042729
>>> 10  libSystem.B.dylib             	0x94e8141f mach_msg_server + 343
>>> 11                                	0x104b2ed5 0x104a4000 + 61141
>>> 12                                	0x104b2c95 0x104a4000 + 60565
>>> 13                                	0x10768cc5 JVM_RaiseSignal +  
>>> 441189
>>> 14  libSystem.B.dylib             	0x94e8853b _pthread_body + 27
>>>
>>
>>
>