crash in [FSEvent uidFromArg:]
Bug #1100841 reported by
Mike McCracken
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu One FsEvents daemon |
Fix Committed
|
High
|
Mike McCracken |
Bug Description
I've now seen this in a couple of users' logs:
Thread 3 Crashed:
0 com.ubuntu.
1 com.ubuntu.
2 com.ubuntu.
3 com.apple.
4 com.apple.
5 libsystem_c.dylib 0x00007fff893de8bf _pthread_start + 335
6 libsystem_c.dylib 0x00007fff893e1b75 thread_start + 13
tags: | added: u1-by-dev u1-filesync u1-on-production |
tags: |
added: u1-syncdaemon removed: u1-filesync |
Changed in ubuntuone-fsevents-daemon: | |
status: | Confirmed → Fix Committed |
Changed in ubuntuone-fsevents-daemon: | |
status: | Confirmed → Fix Committed |
To post a comment you must log in.
Reopened because the linked branch fixes a similar crash in gidFromArg, but not the one in uidFromArg.
Here's another recent crash backtrace from the original uidFromArg bug:
Thread 3 Crashed: one.fsevents 0x0000000100001d2d +[FSEvent uidFromArg:] + 61 one.fsevents 0x0000000100002660 -[FSEvent setEventArgs: withOffset: withTotalSize: ] + 1456 one.fsevents 0x00000001000043cb -[FSEventDispatcher run] + 859 Foundation 0x00007fff93150612 __NSThread__main__ + 1345
0 com.ubuntu.
1 com.ubuntu.
2 com.ubuntu.
3 com.apple.
4 libsystem_c.dylib 0x00007fff9691b742 _pthread_start + 327
5 libsystem_c.dylib 0x00007fff96908181 thread_start + 13