On Wed, Jun 18, 2014 at 07:33:09AM +0300, Randomcoder wrote:
> > > Thank you Andi, I will try to increase the jvm memory.
> > > But if this was indeed a jvm problem, shouldn't a jvm exception be thrown
> > > instead of the C++ runtime std::bad_alloc ?
> &g
On Tue, Jun 17, 2014 at 09:25:27PM -0700, Andi Vajda wrote:
> > Thank you Andi, I will try to increase the jvm memory.
> > But if this was indeed a jvm problem, shouldn't a jvm exception be thrown
> > instead of the C++ runtime std::bad_alloc ?
>
> With JNI, all is possible. And without a stacktr
On Tue, Jun 17, 2014 at 08:54:50PM -0700, Andi Vajda wrote:
> > [..]
> > terminate called after throwing an instance of 'std::bad_alloc' what():
> > std::bad_alloc Aborted
> > [..]
> >Has anyone bumped into this before ?
>
> You might need to increase the RAM default for the JVM when calling
>
Hi,
I've been using pylucene 4.8.0-1(the latest release) to index a lot of
data(~100GB) on a machine
with 16GB of memory.
After the index reaches 3GB the following C++ run-time exception is being
thrown:
terminate called after throwing an instance of 'std::bad_alloc' what():
std::bad_allo
Hi,
I've been using pylucene 4.8.0-1(the latest release) to index a lot of
data(~100GB) on a machine
with 16GB of memory.
After the index reaches 3GB the following C++ run-time exception is being
thrown:
terminate called after throwing an instance of 'std::bad_alloc' what():
std::bad_allo
