Eu tenho um problema estranho com o listview, enquanto uso o adaptador simplecursor. Aqui está o erro

08-31 21:50:14.540: INFO/dalvikvm(12195): Uncaught exception thrown by finalizer (will be discarded):
08-31 21:50:14.540: INFO/dalvikvm(12195): java.lang.IllegalStateException: Binder has been finalized!
08-31 21:50:14.540: INFO/dalvikvm(12195):     at android.os.BinderProxy.transact(Native Method)
08-31 21:50:14.540: INFO/dalvikvm(12195):     at android.database.BulkCursorProxy.close(BulkCursorNative.java:289)
08-31 21:50:14.540: INFO/dalvikvm(12195):     at android.database.BulkCursorToCursorAdaptor.close(BulkCursorToCursorAdaptor.java:141)
08-31 21:50:14.540: INFO/dalvikvm(12195):     at android.database.CursorWrapper.close(CursorWrapper.java:43)
08-31 21:50:14.540: INFO/dalvikvm(12195):     at android.content.ContentResolver$CursorWrapperInner.close(ContentResolver.java:1575)
08-31 21:50:14.540: INFO/dalvikvm(12195):     at android.content.ContentResolver$CursorWrapperInner.finalize(ContentResolver.java:1586)
08-31 21:50:14.540: INFO/dalvikvm(12195):     at dalvik.system.NativeStart.run(Native Method)

Eu executei oQueryOnBackgroundThread implementado no meu cursorAdapter, que é chamado pela chamada do método Filter.filter da atividade. Portanto, não tenho nenhuma referência do cursor na minha atividade. Toda vez que faço uma consulta, entendo que recebo um retorno de chamada alterado do cursor no meu adaptador de cursor, que estende o SimpleCursorAdapter

Aqui está como parece

public void changeCursor(Cursor cursor) {
        Log.d(TAG, "Cursor changed ... **************** "+ cursor);
        if (cursor != null) {
            setLoading(false);
        }
        super.changeCursor(cursor);
        initSectionHeaders(cursor);
        notifyDataSetChanged();
    }

runQueryOnBackgroundThread() apenas retorna um cursor de uma consult

Estou faltando alguma coisa, o cursor deve ser fechado ou gerenciado em qualquer lugar? Qualquer ajuda nos leads ajudaria bastante. Desde já, obrigado

**ATUALIZAR* Trechos do meu adaptador

public Cursor runQueryOnBackgroundThread(CharSequence constraint) {
        Log.d(TAG, "runQueryOnBackgroundThread "+ constraint);
        if (getFilterQueryProvider() != null) {
            return getFilterQueryProvider().runQuery(constraint);
        }
        return doQuery(constraint, People.CONTENT_URI);
    }

private Cursor doQuery(CharSequence constraint, Uri queryUri){
        StringBuilder selectionStrBuilder = new StringBuilder();
        String selectionArgs[] = null;
        String selection = null;

        if(constraint!=null){
            //ADDING GLOB so that the sql query can interpret linux style wildcards
            selectionStrBuilder.append("(UPPER(").append(People.DISPLAY_NAME).append(") GLOB ?)");

            selection = selectionStrBuilder.toString();
            String constraintStr = constraint.toString().toUpperCase();

            //prepend and append '*' - TODO improve
            constraintStr = "*"+ constraintStr;
            constraintStr +="*";

            selectionArgs = new String[]{constraintStr};
        }
        ContentResolver contentRes = context.getContentResolver();
        return contentRes.query(queryUri, null, selection, selectionArgs, People.DISPLAY_NAME);
    }

Outras duas funções, substituí o changeCursor conforme publicado anteriormente e use o cursor na visualização de ligação para obter os dados. Não fecho ou modifico as propriedades do cursor em nenhum outro luga

função getQuery do meu provedor se parece com

SQLiteDatabase db = dbHelper.getReadableDatabase();
        Cursor c = qb.query(db, projection, selection, selectionArgs, null, null, orderBy);

        // Tell the cursor what uri to watch,
        // so it knows when its source data changes
        c.setNotificationUri(getContext().getContentResolver(), uri);
        return c;

UPDATE2 *

Quando executo o mesmo programa no emulador, recebo esse rastreamento de pilha, que é muito diferente do que vejo no table

01-03 17:21:44.130: ERROR/IMemory(9328): binder=0x3891a0 transaction failed fd=-2147483647, size=0, err=-2147483646 (Unknown error: 2147483646)
01-03 17:21:44.130: ERROR/IMemory(9328): cannot dup fd=-2147483647, size=0, err=-2147483646 (Bad file number)
01-03 17:21:44.130: ERROR/IMemory(9328): cannot map BpMemoryHeap (binder=0x3891a0), size=0, fd=-1 (Bad file number)
01-03 17:21:44.130: WARN/dalvikvm(9328): JNI WARNING: JNI method called with exception raised
01-03 17:21:44.130: WARN/dalvikvm(9328):              in Ldalvik/system/NativeStart;.run ()V (CallStaticVoidMethodV)
01-03 17:21:44.130: WARN/dalvikvm(9328): Pending exception is:
01-03 17:21:44.130: INFO/dalvikvm(9328): Ljava/lang/RuntimeException;: No memory in memObj
01-03 17:21:44.130: INFO/dalvikvm(9328):     at android.database.CursorWindow.native_init(Native Method)
01-03 17:21:44.130: INFO/dalvikvm(9328):     at android.database.CursorWindow.<init>(CursorWindow.java:518)
01-03 17:21:44.130: INFO/dalvikvm(9328):     at android.database.CursorWindow.<init>(CursorWindow.java:27)
01-03 17:21:44.130: INFO/dalvikvm(9328):     at android.database.CursorWindow$1.createFromParcel(CursorWindow.java:493)
01-03 17:21:44.130: INFO/dalvikvm(9328):     at android.database.CursorWindow$1.createFromParcel(CursorWindow.java:491)
01-03 17:21:44.130: INFO/dalvikvm(9328):     at android.content.ContentProviderNative.onTransact(ContentProviderNative.java:103)
01-03 17:21:44.130: INFO/dalvikvm(9328):     at android.os.Binder.execTransact(Binder.java:320)
01-03 17:21:44.130: INFO/dalvikvm(9328):     at dalvik.system.NativeStart.run(Native Method)
01-03 17:21:44.130: INFO/dalvikvm(9328): "Binder Thread #3" prio=5 tid=9 NATIVE
01-03 17:21:44.130: INFO/dalvikvm(9328):   | group="main" sCount=0 dsCount=0 obj=0x405de828 self=0x8e288
01-03 17:21:44.130: INFO/dalvikvm(9328):   | sysTid=9336 nice=0 sched=0/0 cgrp=[fopen-error:24] handle=959480
01-03 17:21:44.130: INFO/dalvikvm(9328):   at dalvik.system.NativeStart.run(Native Method)
01-03 17:21:44.130: ERROR/dalvikvm(9328): VM aborting

Falha no aplicativo.

Encontrei um relatório de bug sobre esse problemaaqu

Alguém enfrentou o mesmo problema? Qualquer ajuda seria apreciada. Obrigad