 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Okay, here's the story. I have an automated process for rendering that uses the
command-line version of POV-Ray, compiled and distributed by MacPorts, for my
iMac. 3.7 has always been a bit dodgy on my Mac -- the GUI version runs just
fine, but starting with MacOS Mojave and continuing on to Catalina, the
command-line version crashes, hard, to the point where it's effectively useless,
and it doesn't matter if I use MacPort's version or one I compile myself from
the *nix source; the errors are the same. Tried looking up a contact at
MacPorts to report this, but no maintainer is listed for the POV port, so I'm
turning to this forum and you kind people for whatever assistance you can
provide. The last crash I was able to capture the error messages, which I would
think would be helpful (the crash report for Apple has gobs of data).
Anyway, any help would be appreciated. If I posted this in the wrong forum,
please accept my apologizes and kindly direct me to the correct forum/venue.
Thank you.
Dan Byers
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
This is Yvo Smellenbergh's sig info:
POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net
Maybe use
http://news.povray.org/povray.macintosh/
I'm sure it's heading-appropriate in either section...
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 10/16/19 8:36 PM, Dan Byers wrote:
> Okay, here's the story. I have an automated process for rendering that uses the
> command-line version of POV-Ray, compiled and distributed by MacPorts, for my
> iMac. 3.7 has always been a bit dodgy on my Mac -- the GUI version runs just
> fine, but starting with MacOS Mojave and continuing on to Catalina, the
> command-line version crashes, hard, to the point where it's effectively useless,
...
Any progress solving the problem?
Very odd the gui would be stable and the command line not, if running
identical scenes with the same options.
What first popped into my head was perhaps your command line was issued
from the mac-equivalent of an *nix xterm shell where your user limits
had been set too low for some necessary resource. I check my settings on
linux with 'ulimit -a'. After that maybe something different in your
command shell environment such as an alias command setting in conflict
with an argument or... If you've got non-ascii file names, that's
another possibility - should the gui you use be scrubbing them up or
something. There are open issues for the non-ascii file names.
Otherwise pointers Bald_Eagle offered good places to start.
If no progress with v3.7, worth giving a recent v3.8 a try. Fixes
aplenty there.
Bill P.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Thanks for the replies, everyone. Found the issue, and the crash report had the
answer (who knew, right? HA!). I was rendering with Display=on, which produced
all this lovely jibber-jabber:
************************************************************************************
2019-10-16 19:14:34.479 povray[38836:474601] *** Terminating app due to uncaught
exception 'NSInternalInconsistencyException', reason: 'NSWindow drag regions
should only be invalidated on the Main Thread!'
*** First throw call stack:
(
0 CoreFoundation 0x00007fff301fbd63
__exceptionPreprocess + 250
1 libobjc.A.dylib 0x00007fff660eabd4 objc_exception_throw
+ 48
2 CoreFoundation 0x00007fff3021630c -[NSException raise]
+ 9
3 AppKit 0x00007fff2d3e07b3
-[NSWindow(NSWindow_Theme)
_postWindowNeedsToResetDragMarginsUnlessPostingDisabled] + 310
4 AppKit 0x00007fff2d3ddce1 -[NSWindow
_initContent:styleMask:backing:defer:contentView:] + 1416
5 AppKit 0x00007fff2d3dd753 -[NSWindow
initWithContentRect:styleMask:backing:defer:] + 42
6 libSDL-1.2.0.dylib 0x0000000107b37649 -[SDL_QuartzWindow
initWithContentRect:styleMask:backing:defer:] + 262
7 libSDL-1.2.0.dylib 0x0000000107b353cc QZ_SetVideoMode +
1289
8 libSDL-1.2.0.dylib 0x0000000107b2d091 SDL_SetVideoMode +
581
9 povray 0x0000000107828694
_ZN12pov_frontend14UnixSDLDisplay4ShowEv + 598
10 povray 0x000000010783cddd
_ZN3vfe15VirtualFrontEnd7ProcessEv + 1833
11 povray 0x0000000107830a87
_ZN3vfe10vfeSession15ProcessFrontendEv + 27
12 povray 0x0000000107830dd4
_ZN3vfe10vfeSession12WorkerThreadEv + 546
13 libboost_thread-mt.dylib 0x0000000108104c47
_ZN5boost12_GLOBAL__N_112thread_proxyEPv + 119
14 libsystem_pthread.dylib 0x00007fff67655d76 _pthread_start + 125
15 libsystem_pthread.dylib 0x00007fff676525d7 thread_start + 15
)
libc++abi.dylib: terminating with uncaught exception of type NSException
/Users/danb/Documents/Movies/EC009/src/RenderStill.sh: line 3: 38836 Abort trap:
6 povray mac_still
***************************************************************
Switched Display=off, and it renders just fine.
I code for a living, so you'd think I'd read the damn crash report a little more
thoroughly BEFORE I go running & screaming to the hills... smdh... screw it,
it's Friday and I'm gonna go hang out with the better half & watch some stupid
TV...
Thanks again, everyone :D
Dan
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Dan Byers" <goofygraffix_at_geemail_dot_com> wrote:
> Thanks for the replies, everyone. Found the issue, and the crash report had the
> answer (who knew, right? HA!). I was rendering with Display=on, which produced
> all this lovely jibber-jabber:
> ************************************************************************************
> 2019-10-16 19:14:34.479 povray[38836:474601] *** Terminating app due to uncaught
> exception 'NSInternalInconsistencyException', reason: 'NSWindow drag regions
> should only be invalidated on the Main Thread!'
> *** First throw call stack:
> (
> 0 CoreFoundation 0x00007fff301fbd63
> __exceptionPreprocess + 250
> 1 libobjc.A.dylib 0x00007fff660eabd4 objc_exception_throw
> + 48
> 2 CoreFoundation 0x00007fff3021630c -[NSException raise]
> + 9
> 3 AppKit 0x00007fff2d3e07b3
> -[NSWindow(NSWindow_Theme)
> _postWindowNeedsToResetDragMarginsUnlessPostingDisabled] + 310
> 4 AppKit 0x00007fff2d3ddce1 -[NSWindow
> _initContent:styleMask:backing:defer:contentView:] + 1416
> 5 AppKit 0x00007fff2d3dd753 -[NSWindow
> initWithContentRect:styleMask:backing:defer:] + 42
> 6 libSDL-1.2.0.dylib 0x0000000107b37649 -[SDL_QuartzWindow
> initWithContentRect:styleMask:backing:defer:] + 262
> 7 libSDL-1.2.0.dylib 0x0000000107b353cc QZ_SetVideoMode +
> 1289
> 8 libSDL-1.2.0.dylib 0x0000000107b2d091 SDL_SetVideoMode +
> 581
> 9 povray 0x0000000107828694
> _ZN12pov_frontend14UnixSDLDisplay4ShowEv + 598
> 10 povray 0x000000010783cddd
> _ZN3vfe15VirtualFrontEnd7ProcessEv + 1833
> 11 povray 0x0000000107830a87
> _ZN3vfe10vfeSession15ProcessFrontendEv + 27
> 12 povray 0x0000000107830dd4
> _ZN3vfe10vfeSession12WorkerThreadEv + 546
> 13 libboost_thread-mt.dylib 0x0000000108104c47
> _ZN5boost12_GLOBAL__N_112thread_proxyEPv + 119
> 14 libsystem_pthread.dylib 0x00007fff67655d76 _pthread_start + 125
> 15 libsystem_pthread.dylib 0x00007fff676525d7 thread_start + 15
> )
> libc++abi.dylib: terminating with uncaught exception of type NSException
> /Users/danb/Documents/Movies/EC009/src/RenderStill.sh: line 3: 38836 Abort trap:
> 6 povray mac_still
>
> ***************************************************************
> Switched Display=off, and it renders just fine.
>
> I code for a living, so you'd think I'd read the damn crash report a little more
> thoroughly BEFORE I go running & screaming to the hills... smdh... screw it,
> it's Friday and I'm gonna go hang out with the better half & watch some stupid
> TV...
>
> Thanks again, everyone :D
a POV-Ray problem.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Dan Byers" <goofygraffix_at_geemail_dot_com> wrote:
> Thanks for the replies, everyone. Found the issue, and the crash report had the
> answer (who knew, right? HA!). I was rendering with Display=on, which produced
> all this lovely jibber-jabber:
> ************************************************************************************
> 2019-10-16 19:14:34.479 povray[38836:474601] *** Terminating app due to uncaught
> exception 'NSInternalInconsistencyException', reason: 'NSWindow drag regions
> should only be invalidated on the Main Thread!'
> *** First throw call stack:
> (
> 0 CoreFoundation 0x00007fff301fbd63
> __exceptionPreprocess + 250
> 1 libobjc.A.dylib 0x00007fff660eabd4 objc_exception_throw
> + 48
> 2 CoreFoundation 0x00007fff3021630c -[NSException raise]
> + 9
> 3 AppKit 0x00007fff2d3e07b3
> -[NSWindow(NSWindow_Theme)
> _postWindowNeedsToResetDragMarginsUnlessPostingDisabled] + 310
> 4 AppKit 0x00007fff2d3ddce1 -[NSWindow
> _initContent:styleMask:backing:defer:contentView:] + 1416
> 5 AppKit 0x00007fff2d3dd753 -[NSWindow
> initWithContentRect:styleMask:backing:defer:] + 42
> 6 libSDL-1.2.0.dylib 0x0000000107b37649 -[SDL_QuartzWindow
> initWithContentRect:styleMask:backing:defer:] + 262
> 7 libSDL-1.2.0.dylib 0x0000000107b353cc QZ_SetVideoMode +
> 1289
> 8 libSDL-1.2.0.dylib 0x0000000107b2d091 SDL_SetVideoMode +
> 581
> 9 povray 0x0000000107828694
> _ZN12pov_frontend14UnixSDLDisplay4ShowEv + 598
> 10 povray 0x000000010783cddd
> _ZN3vfe15VirtualFrontEnd7ProcessEv + 1833
> 11 povray 0x0000000107830a87
> _ZN3vfe10vfeSession15ProcessFrontendEv + 27
> 12 povray 0x0000000107830dd4
> _ZN3vfe10vfeSession12WorkerThreadEv + 546
> 13 libboost_thread-mt.dylib 0x0000000108104c47
> _ZN5boost12_GLOBAL__N_112thread_proxyEPv + 119
> 14 libsystem_pthread.dylib 0x00007fff67655d76 _pthread_start + 125
> 15 libsystem_pthread.dylib 0x00007fff676525d7 thread_start + 15
> )
> libc++abi.dylib: terminating with uncaught exception of type NSException
> /Users/danb/Documents/Movies/EC009/src/RenderStill.sh: line 3: 38836 Abort trap:
> 6 povray mac_still
>
> ***************************************************************
> Switched Display=off, and it renders just fine.
>
> I code for a living, so you'd think I'd read the damn crash report a little more
> thoroughly BEFORE I go running & screaming to the hills... smdh... screw it,
> it's Friday and I'm gonna go hang out with the better half & watch some stupid
> TV...
>
> Thanks again, everyone :D
>
> Dan
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|
