 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I am currently using Beta 36 and encounter 1-2 Crashes per day (for some reason
far less than the 5-6 from beta 35a?!).
I am then presented with a crash dump choice - small, large or none.
Which should I choose? Furthermore, where should I send/upload them to? Th large
dumps are all around 200MB in size. I was unable to find anything relating to
that (or missed it).
Also, I have started to record what I was changing/doing at the time (no
predictable behavior so far) - should I upload these notes as well?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> I am currently using Beta 36 and encounter 1-2 Crashes per day (for some reason
> far less than the 5-6 from beta 35a?!).
>
> I am then presented with a crash dump choice - small, large or none.
> Which should I choose? Furthermore, where should I send/upload them to? Th large
> dumps are all around 200MB in size. I was unable to find anything relating to
> that (or missed it).
>
> Also, I have started to record what I was changing/doing at the time (no
> predictable behavior so far) - should I upload these notes as well?
>
>
>
>
Place a post here about your crash and tell that you have a dump
available, and send the dump if a devloper ask you to. He'll give you an
adress to where to send it. As it can be possible for a dump to contain
some private data, never post it on any forum.
Before sending a dump, compress it as a zip file or another format the
devlopment team agree to. Use the highest compression possible. Most
dumps can compress by a factor of 90% to 98%.
Normaly, the small dump is enough. Only use the large one on request. No
dump is the choice after the expiration date.
Alain
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> I am currently using Beta 36 and encounter 1-2 Crashes per day (for some
> reason far less than the 5-6 from beta 35a?!).
Curiously enough, I'm using now beta 36 in Linux through Wine, and it
never crashes! I've a minor glitch with the buttons not appearing until I
resize the window, but for the rest it works very well.
--
Jaime Vives Piqueres
http://www.ignorancia.org
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 14.04.2010 21:27, schrieb philguy:
> I am currently using Beta 36 and encounter 1-2 Crashes per day (for some reason
> far less than the 5-6 from beta 35a?!).
Are these crashes during rendering, or during use of the UI?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
clipka <ano### [at] anonymous org> wrote:
> Am 14.04.2010 21:27, schrieb philguy:
> > I am currently using Beta 36 and encounter 1-2 Crashes per day (for some reason
> > far less than the 5-6 from beta 35a?!).
>
> Are these crashes during rendering, or during use of the UI?
Parsing or rendering. Once had a crash during use of the UI, but did not save
dump/record anything.
Well, I only wrote down what I was doing with the last two dumps, before that,
no clue. There seem to be no similarities among these crashes, neither any
reproducible behavior. They occur at about 1 every 100...200 renders, and
rendering generally finishes successfully in the background when the crash
message appears.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Clarification:
> There seem to be no similarities among these crashes,[...]
This concerns all crashes encountered with the 35a/36 betas, not just the two
recorded ones.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I would like to bring this up again as I have been modeling again these days and
crash frequency has been ridiculous. I encountered 14 crashes within a period of
~2h (spread over two sessions). Two of these crashes were
"hard", meaning POV-Ray did not close nicely but instead quit responding. All of
my work was with emission media, if that means anything.
I did note the one thing in common with all these crashes - they all happened at
0x00000001400b5c80. Does that mean there is a problem with my RAM? My computer
runs stable otherwise.
Unrelated: Can I tell the newsgroup server to email me when someone responds to
my thread?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> I would like to bring this up again as I have been modeling again these days and
> crash frequency has been ridiculous. I encountered 14 crashes within a period of
> ~2h (spread over two sessions). Two of these crashes were
> "hard", meaning POV-Ray did not close nicely but instead quit responding. All of
> my work was with emission media, if that means anything.
>
> I did note the one thing in common with all these crashes - they all happened at
> 0x00000001400b5c80. Does that mean there is a problem with my RAM? My computer
> runs stable otherwise.
>
> Unrelated: Can I tell the newsgroup server to email me when someone responds to
> my thread?
>
>
>
>
>
That's an address that uses 33 bits. It's possible that most of the time
that memory area is not used, or not much and never for importent
things, like executable code, but only for data.
If the error always appens at the same address, it can mean that there
is a problem with the RAM.
Try loading something, like note pad, and do a test. See if the error
still appens at the same location.
There are some RAM testers available. Normaly, they need to be run from
some removable, bootable, media.
Get one and let it run for a few hours, or beter, overnight.
Alain
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
