 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
oh, I got too excited that didn't even remember I have only
single-core... :P
oh, well, the source may be entertaining enough!
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hi,
already compiled it in a x86_64 GNU/Linux box, but still some bugs around.
Most critical one for me is that even tough I have 64G RAM and a 4 quad-core
Xeon, I get a "Fatal error in renderer: Out of memory." due to some problem
with interiors. Does anyone know about the status of this bug?
Anyway, SMP works perfectly!
Cheers
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"b-soain" <nomail@nomail> wrote:
> Most critical one for me is that even tough I have 64G RAM and a 4 quad-core
> Xeon, I get a "Fatal error in renderer: Out of memory." due to some problem
> with interiors. Does anyone know about the status of this bug?
I can't find a full, up-to-date list of known bugs. Perhaps the best thing to do
would be to start a new thread and post a minimal scene to show the problem.
Tom
Post a reply to this message
|
|
| |
| |
|
|
From: Thorsten Froehlich
Subject: Re: 3.7 beta Unix/Linux source code now available.
Date: 27 Feb 2008 20:02:34
Message: <47c6082a$1@news.povray.org>
|
|
|
| |
| |
|
|
b-soain wrote:
> already compiled it in a x86_64 GNU/Linux box, but still some bugs around.
> Most critical one for me is that even tough I have 64G RAM and a 4 quad-core
> Xeon, I get a "Fatal error in renderer: Out of memory." due to some problem
> with interiors. Does anyone know about the status of this bug?
This is not a bug, it is an internal buffer that trades speed for memory
limits. It should not be needed, but a better solution is complicated and
time intensive to implement.
Thorsten
Post a reply to this message
|
|
| |
| |
|
|
From: Warp
Subject: Re: 3.7 beta Unix/Linux source code now available.
Date: 28 Feb 2008 03:46:14
Message: <47c674d6@news.povray.org>
|
|
|
| |
| |
|
|
Thorsten Froehlich <tho### [at] trf de> wrote:
> This is not a bug, it is an internal buffer that trades speed for memory
> limits. It should not be needed, but a better solution is complicated and
> time intensive to implement.
Could the reaching this limit be detected and a better error message be
shown? Now it looks just like a regular "out of memory" error while it
really isn't, as it's a particular special case. Perhaps a more informative
message could be better in this situation.
--
- Warp
Post a reply to this message
|
|
| |
| |
|
|
From: Thorsten Froehlich
Subject: Re: 3.7 beta Unix/Linux source code now available.
Date: 28 Feb 2008 05:23:05
Message: <47c68b89$1@news.povray.org>
|
|
|
| |
| |
|
|
Warp wrote:
> Thorsten Froehlich <tho### [at] trfde> wrote:
>> This is not a bug, it is an internal buffer that trades speed for memory
>> limits. It should not be needed, but a better solution is complicated and
>> time intensive to implement.
>
> Could the reaching this limit be detected and a better error message be
> shown?
I said a better solution is possible, did I not? ;-)
Thorsten
Post a reply to this message
|
|
| |
| |
|
|
From: Chris Cason
Subject: Re: 3.7 beta Unix/Linux source code now available.
Date: 28 Feb 2008 07:20:36
Message: <47c6a714$1@news.povray.org>
|
|
|
| |
| |
|
|
b-soain wrote:
> already compiled it in a x86_64 GNU/Linux box, but still some bugs around.
> Most critical one for me is that even tough I have 64G RAM and a 4 quad-core
> Xeon, I get a "Fatal error in renderer: Out of memory." due to some problem
> with interiors. Does anyone know about the status of this bug?
Sample scene please?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Not sure if this is the right location to post this...
I managed to get it compiled on a quadcore system running Fedora 8, though it
took a while to figure out that I had to configure with the option
"--with-boost-thread=boost_thread-mt"
Test render during compilation worked fine, but when I went to render some old
scenes I had laying around I would get the message:
"Timed out waiting for worker thread startup"
If I keep running the command it will eventually work, but I generally get the
time out message instead of parsing and rendering.
I decided to try beta binary and got the same thing.
Seems like it should be something simple, but I don't know where to start.
SMP worked fine when it would actually render.
--paul
Post a reply to this message
|
|
| |
| |
|
|
From: Alain
Subject: Re: 3.7 beta Unix/Linux source code now available.
Date: 28 Feb 2008 11:14:58
Message: <47c6de02@news.povray.org>
|
|
|
| |
| |
|
|
Thorsten Froehlich nous apporta ses lumieres en ce 2008/02/28 05:23:
> Warp wrote:
>> Thorsten Froehlich <tho### [at] trfde> wrote:
>>> This is not a bug, it is an internal buffer that trades speed for
>>> memory limits. It should not be needed, but a better solution is
>>> complicated and time intensive to implement.
>>
>> Could the reaching this limit be detected and a better error message be
>> shown?
>
> I said a better solution is possible, did I not? ;-)
>
> Thorsten
>
The error message should read "Buffer overflow", not "Out of memory".
--
Alain
-------------------------------------------------
You know you've been raytracing too long when you can recite your high school
Trig book from memory.
Post a reply to this message
|
|
| |
| |
|
|
From: Nicolas Alvarez
Subject: Re: 3.7 beta Unix/Linux source code now available.
Date: 28 Feb 2008 11:16:33
Message: <47c6de61$1@news.povray.org>
|
|
|
| |
| |
|
|
Alain escribió:
> The error message should read "Buffer overflow", not "Out of memory".
>
That will scare the hell out of users who know those two words related
to security vulnerabilities.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
