Mailing-List: contact pylucene-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: pylucene-dev@lucene.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Date: Thu, 14 Apr 2011 17:01:18 -0700 (PDT)
From: Andi Vajda <vajda@apache.org>
Reply-To: Andi Vajda <vajda@apache.org>
To: pylucene-dev@lucene.apache.org
Subject: Re: finding exceptions the crash pylucene
In-Reply-To: <BANLkTin_-AOh82e+MLHzxxzmp8=TwpA1pw@mail.gmail.com>
Message-ID: <alpine.OSX.2.01.1104141700180.21250@yuzu.local>
References: <BANLkTi=Dkw76-j2Rvs49az=M5K5gfimV+A@mail.gmail.com>
 <alpine.OSX.2.01.1104141406141.21025@yuzu.local>
 <BANLkTin_-AOh82e+MLHzxxzmp8=TwpA1pw@mail.gmail.com>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed


On Thu, 14 Apr 2011, Marcus wrote:

> thanks.
>
> I have documents that will consistently cause this upon writing them to the
> index. let me see if I can reduce them down to the crux of the crash.
> granted, these are docs are very large, unruly "bad" data, that should have
> never gotten this stage in our pipeline, but I was hoping for a java or
> lucene exception.
>
> I also get "Java GC overhead" exceptions passed into my code from time to
> time, but those manageable, and not crashes.
>
> Are there known memory constraint scenarios that force a c++ exception,
> whereas in a normal Java environment,  you would get a memory error?

Not sure.

> and just confirming, do "java.lang.OutOfMemoryError" errors pass into
> python, or force a crash?

Not sure, I've never seen these as I make sure I've got enough memory.
initVM() is the place where you can configure the memory for your JVM.

Andi..

>
> thanks again
> Marcus
>
> On Thu, Apr 14, 2011 at 2:07 PM, Andi Vajda <vajda@apache.org> wrote:
>
>>
>> On Thu, 14 Apr 2011, Marcus wrote:
>>
>>  in certain cases when a java/pylucene exception occurs,  it gets passed up
>>> in my code, and I'm able to analyze the situation.
>>> sometimes though,  the python process just crashes, and if I happen to be
>>> in
>>> top (linux top that is), I see a JCC exception flash up in the top
>>> console.
>>> where can I go to look for this exception, or is it just lost?
>>> I looked in the locations where a java crash would be located, but didn't
>>> find anything.
>>>
>>
>> If you're hitting a crash because of an unhandled C++ exception, running a
>> debug build with symbols under gdb will help greatly in tracking it down.
>>
>> An unhandled C++ exception would be a PyLucene/JCC bug. If you have a
>> simple way to reproduce this failure, send it to this list.
>>
>> Andi..
>>
>