Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Crash on Lion after indexing #31

Closed
gf3 opened this Issue Aug 22, 2011 · 12 comments

Comments

Projects
None yet
10 participants

gf3 commented Aug 22, 2011

Ingredients first launched properly, and began to index the docs. When it was done indexing, the app crashed. Now the app crashes immediately on launch.

Here's the info from the crash reporter: https://gist.github.com/6a2573ed09436fab70b1

timeimp commented Aug 25, 2011

I'll +1 on this issue. Indexed fine. Went to search for something. Ingredients died. Same error as above. (Lion 10.7.1)

bjtitus commented Aug 26, 2011

Same issue here. Same backtrace on the crashed thread with a problem in sqlite3Api.

vytis commented Aug 31, 2011

I also get this crash. Unfortunately the app is unusable on 10.7.1 :/

Same here. Crash on 10.7.1.

dannolan commented Sep 7, 2011

Crashes on 10.7.1 on my machine as well.

Same issue here on Lion 10.7.1 with XCode 4.2 Build 4D177b.

pypt commented Oct 5, 2011

I'd guess it has something to do with Core Data not being happy with running in a separate thread, encountering random freed pointers, etc.

I've tried changing - (dispatch_queue_t)backgroundQueue method in IGKApplicationDelegate.mm in a way so that the "background" processes of the app run on the same (main) thread:

- (dispatch_queue_t)backgroundQueue
{
    if (backgroundQueue == NULL) {
        //backgroundQueue = dispatch_queue_create(NULL, NULL);
        backgroundQueue = dispatch_get_main_queue();
    }

    return backgroundQueue;
}

Now it appears to work fine on Lion (unless I didn't provoke it enough to crash), just that the interface became sluggish as the UI has to wait for Core Data to fetch search results. Anyway, not that bad as a temporary solution.

dannolan commented Oct 6, 2011

Fork, patch it and submit a pull request, I'd say

On Thursday, 6 October 2011 at 6:33 AM, Linas V. wrote:

I'd guess it has something to do with Core Data not being happy with running in a separate thread, encountering random freed pointers, etc.

I've tried changing - (dispatch_queue_t)backgroundQueue method in IGKApplicationDelegate.mm in a way so that the "background" processes of the app run on the same (main):

  • (dispatch_queue_t)backgroundQueue
    {
    if (backgroundQueue == NULL) {
    //backgroundQueue = dispatch_queue_create(NULL, NULL);
    backgroundQueue = dispatch_get_main_queue();
    }

    return backgroundQueue;
    }

Now it appears to work fine on Lion (unless I didn't provoke it enough to crash), just that the interface became sluggish as the UI has to wait for Core Data to fetch search results. Anyway, not that bad as a temporary solution.

Reply to this email directly or view it on GitHub:
fileability#31 (comment)

pypt commented Oct 6, 2011

As this would be a "better than nothing" fix, I don't see how that would get pushed to master.

+1 same here with lion 10.7.1

anddam commented Jan 19, 2012

Isn't this issue a duplicate of #16?

pypt commented Jan 21, 2012

Issue #16 looks very similar, yes.

@gf3 gf3 closed this Jun 1, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment