|
 |
Am 16.11.2016 um 01:55 schrieb [GDS|Entropy]:
> I noticed that under Win 10 x64 that when switching to/from the UberPov
> window it will freeze for a second or two, and when there is a completed or
> working render it is a bit more pronounced.
>
> Has anyone else noticed such?
I can't think of any reason whatsoever why that should happen with
UberPOV but not with official contemporary POV-Ray pre-releases. They
differ in the set of features, but the overall architecture is virtually
identical, and as of recently the pre-releases also use exactly the same
build environment.
Post a reply to this message
|
|
|
|
clipka <ano### [at] anonymous org> wrote:
> Am 16.11.2016 um 01:55 schrieb [GDS|Entropy]:
>> I noticed that under Win 10 x64 that when switching to/from the UberPov
>> window it will freeze for a second or two, and when there is a completed or
>> working render it is a bit more pronounced.
>>
>> Has anyone else noticed such?
>
> I can't think of any reason whatsoever why that should happen with
> UberPOV but not with official contemporary POV-Ray pre-releases. They
> differ in the set of features, but the overall architecture is virtually
> identical, and as of recently the pre-releases also use exactly the same
> build environment.
>
>
It is quite possible that it is some aspect of Windows 10 pro, but yes it
is puzzling.
Ian
Post a reply to this message
|
|
|
|
[GDS|Entropy] <gdsHYPHENentropyAThotmaolDOTcom> wrote:
> clipka <ano### [at] anonymousorg> wrote:
> > Am 16.11.2016 um 01:55 schrieb [GDS|Entropy]:
> >> I noticed that under Win 10 x64 that when switching to/from the UberPov
> >> window it will freeze for a second or two, and when there is a completed or
> >> working render it is a bit more pronounced.
> >>
> >> Has anyone else noticed such?
> >
> > I can't think of any reason whatsoever why that should happen with
> > UberPOV but not with official contemporary POV-Ray pre-releases. They
> > differ in the set of features, but the overall architecture is virtually
> > identical, and as of recently the pre-releases also use exactly the same
> > build environment.
>
> It is quite possible that it is some aspect of Windows 10 pro, but yes it
> is puzzling.
Win 10 64-bit here too and no pauses from program transitions, however, I've had
a couple crashes from the POV-Ray alpha versions going back a month or two.
Saved 2 sets of dump files, hundreds of megabytes. Thought I would wait to see
if it would happen a lot more or change with newer releases.
Event Viewer does show something went wrong with UberPOV in September:
Fault bucket 50, type 5
Event Name: RADAR_PRE_LEAK_64
Response: Not available
Cab Id: 0
Problem signature:
P1: uberpov64.exe
P2: 3.7.0.0
P3: 10.0.14393.2.0.0
P4:
P5:
P6:
P7:
P8:
P9:
P10:
Attached files:
\\?\C:\Users\Bob\AppData\Local\Temp\RDRFF43.tmp\empty.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFF82.tmp.WERInternalMetadata.xml
These files may be available here:
Analysis symbol:
Rechecking for solution: 0
Report Id: 320daf4b-7a6f-11e6-9bed-dc5360a9a04b
Report Status: 0
Hashed bucket: 654db5c4b9e65eb5527a9f78fc1a0507
&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
While the alpha POV-Ray very recently shows this:
Application popup: POV-Ray for Windows : Unfortunately, it appears that a memory
access violation at address 0x0000000140349AA5 has caused this unofficial
POV-Ray build to crash. This dialog will allow you to choose whether or not a
dump file (useful for diagnostics) is written.
And also going back to September, or August, I've seen an application memory
error message (possibly some other type) flash on the screen at Shutdown.
Happens too fast for me to see or read anything. Probably a dozen or more of
those to date, but I haven't tried to check what it might be in the Event Viewer
next Startup. Only looking for things now because of this message post.
Post a reply to this message
|
|
