Try removing the Finney and Institutes modules, or build bibletime with no modules in your sword install. I had the same problem, check the archives for <a href="mailto:tjcford@gmail.com">tjcford@gmail.com</a>. I was apparently using some older modules and bibletime croaks when it tries to start -- eats up the CPU and memory as it goes in a big loop rereading some flaky modules. <br>
<br>I now build sword from source, then bibletime and then xiphos. Xiphos doesn't croak on the modules but bibletime does.<br><br>Tom <br><br><div class="gmail_quote">On Thu, Dec 16, 2010 at 4:36 PM, Linus Ulrick <span dir="ltr"><<a href="mailto:meow8282@gmail.com">meow8282@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hello Everyone,<br>
I have been attempting to build and run Bibletime from SVN for quite some time<br>
now. If I remember correctly, if I start Bibletime with NO Sword<br>
modules in the<br>
expected location, Bibletime will start... Otherwise, Bibletime will<br>
not start,<br>
it will consume a fairly large amount of the resources of one of my CPU cores,<br>
and the memory that it uses will just keep growing. I also compile and install<br>
Xiphos from their development tree. It starts and runs perfectly with the same<br>
Sword modules that Bibletime "SEEMS" to be choking on.<br>
<br>
I compile with the following cmake line:<br>
<br>
cmake .. -DCMAKE_INSTALL_PREFIX=/usr/local/spu/spu-$(xdate)/kde -<br>
DCMAKE_CXX_FLAGS="-fno-var-tracking-assignments" -DCMAKE_BUILD_TYPE=debug<br>
<br>
I THINK that this means that I am building a debug build of Bibletime.<br>
But when<br>
I run it from a terminal, absolutely no output.<br>
<br>
Using the potentially un-precise method of ksysguard, I will now open Bibletime<br>
and let it run for a few minutes, to see what happens to my system:<br>
<br>
1. Before starting Bibletime, ksysguard shows the following:<br>
CPU: 11%<br>
Memory: 1.7 GiB / 7.8 Gib<br>
<br>
2. So, let's start Bibletime, and see what happens...<br>
<br>
3. CPU: 36%<br>
Memory: 1.8 GiB / 7.8 Gib<br>
The actual Bibletime process now says:<br>
CPU Memory<br>
25% 79.7 M<br>
<br>
Okay, now I will let it run a few minutes, and we will see what CPU & Memory<br>
consumption looks like...<br>
<br>
While we are waiting, a description of my system:<br>
Intel Xeon QuadCore processor, 2.0GhZ<br>
8 GiB of RAM<br>
<br>
4. In the time that it took me to type that, here's how things look:<br>
The system in general:<br>
CPU: 34%<br>
Memory: 1.9 GiB<br>
<br>
The Bibletime process itself:<br>
CPU Memory<br>
25% 214.8 M<br>
<br>
So, Bibletime has now been running for about 10-15 minutes, and I see the<br>
following:<br>
1. Bibletime is still merely a running process. The application itself has not<br>
started yet...<br>
2. CPU % on the Bibletime process is running at 25%, and memory usage has<br>
increased from 79.7 MiB when I started Bibletime, to 320 MiB right<br>
now. Now 335<br>
MiB...<br>
<br>
All of this, and Bibletime is still nothing more than the splash screen right<br>
now...<br>
<br>
Not saying that the problem is not on my end. Just saying that Bibletime from<br>
SVN is not working for me, and I don't know how to fix it :)<br>
<br>
Steven P. Ulrick<br>
<br>
P.S.: Off to try Bibletime from the Official Fedora 13 Repo...<br>
<br>
_______________________________________________<br>
bt-devel mailing list<br>
<a href="mailto:bt-devel@crosswire.org">bt-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/bt-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/bt-devel</a><br>
</blockquote></div><br>