On Sunday, October 09, 2011, Knut Anders Hatlen elucidated thus: > "Joshua J. Kugler" <jos...@azariah.com> writes: > > On Friday, October 07, 2011, Lubos Kosco elucidated thus: > >> so first odd thing is why does it use an xml analyzer on xls file > > > > Well, because it was in fact an HTML file that someone had given an > > .xls extension. It does look like it was an excel export, but it > > was an HTML file. And it's 373MB > > > > So, the next question is: > > > > 1) Why is it dying? > > 2) Why is it dying with no errors, killing the indexing, and making > > it look like everything completed successfully? > > The indexer tends to use a lot of memory when it encounters big > files, so it might have run into an OutOfMemoryError on a file of > that size. There was a bug that prevented OutOfMemoryErrors from > being reported in OpenGrok 0.10, fixed on trunk: > > https://defect.opensolaris.org/bz/show_bug.cgi?id=18618
Being that it's a 373MB HTML file, that would make sense. Google Chrome starts using over 2GB (or was it 3?) of memory trying to render that file. So, not being very acquianted with Java development, how do I run the latest trunk? Check out trunk, cd into it, and type ant? Will that build all needed binaries, libraries, etc? I do suppose there are developer instructions on the web site, eh? :) j -- Joshua J. Kugler - Fairbanks, Alaska Azariah Enterprises - Programming and Website Design jos...@azariah.com - Jabber: pedah...@gmail.com PGP Key: http://pgp.mit.edu/ ID 0x73B13B6A _______________________________________________ opengrok-discuss mailing list opengrok-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/opengrok-discuss
