Jerzy Chałupski

Results 18 comments of Jerzy Chałupski

Can you just add -noverify option by default to work around the Java 1.7 + robolectric issues? On Jan 15, 2015 7:21 PM, "Evan Tatarka" [email protected] wrote: > Yep, that's...

I have missed the other PR somehow, thanks for pointing it out. I have very few `isNullOrEmpty()` usages. For now I'm just doing `assertThat(Strings.isNullOrEmpty()).isTrue()`, and I'll probably end up changing...

It seems that the root cause of these crashes was a memory leak. I've managed to reproduce it with a very simple application with a data flow that resembles what...

I'd go with columns aliases + separate POJO for joined results. So I'd have three annotated POJOs: ``` java class Foo { @Column("id") long id; @Column("name") String name; } class...

It would have to be separate method (wrapCursor?), because of type erasure.

Related: http://commonsware.com/blog/2014/03/31/cwac-loaderex-failed-abstractions.html

I have run the following code without any issues: ``` java public class MyActivity extends FragmentActivity implements LoaderCallbacks { private ArrayAdapter mAdapter; @Override protected void onCreate(Bundle savedInstanceState) { super.onCreate(savedInstanceState); setContentView(R.layout.activity_list);...

@ultraon Cursors aren't closed by LazyCursorList, they are managed by ComposedCursorLoader and closed in releaseResources call. Getting back to your problem - do you observe the leak in 100% of...

`onAbandon` is definitely not a place to release resources - you should keep the already loaded data until the 2nd instance of loader created after `restartLoader()` delivers its data. I'll...

I still can't figure out how this can happen. I have few more questions that might help me pinpoint this issue: 1. Which version of android-db-commons do you use? 2....