-
C4D NET client crashes
We set up a render network using NET 8.5 on OSX 10.4.6. But “NET Client” quits unexpectedly within an hour or so. It does this on every machine, though some seem to go longer than others. And it happens regardless of which project is being rendered.
Any thoughts. FWIW, I’ve posted the kernel error below for anyone who understands it. It’s always the same code that crashes CLient.
Thread 4 Crashed:
0 C4D Client 0x0243dfc0 0x2008000 + 4415424
1 C4D Client 0x0243eb2c 0x2008000 + 4418348
2 C4D Client 0x0243ec24 0x2008000 + 4418596
3 C4D Client 0x02018120 0x2008000 + 65824
4 C4D Client 0x0201a188 0x2008000 + 74120
5 C4D Client 0x024401fc 0x2008000 + 4424188
6 C4D Client 0x0201f554 0x2008000 + 95572
7 …ple.CoreServices.CarbonCore 0x90bf590c InvokeThreadEntryUPP + 24
8 …ple.CoreServices.CarbonCore 0x90bf552c CooperativeThread + 220
9 libSystem.B.dylib 0x9002ba68 _pthread_body + 96 -
2 Replies
-
Maybe unrelated but recently I was having Server crash problems that stopped when I changed the server’s port from 8080
-
There are lots of info here;
https://forums.cgsociety.org/showthread.php?t=373028first R8.5 and Panther was absolutely rocksolid, allways. It leads to Tiger (10.4).
In short, the server must either run on Panther (10.3) – or – run on a single processor.The Clients can use Tiger
I have opt to turn of the second processor in my server machine while NET rendering.second(even if you say it is happening to all sorts of renderings) there are crashes if the frames rendered
are very “empty”, that is, they render very fast (as they started to do with my quads…) typically under a second.Cheers
Lennart
Reply to this Discussion! Login or Sign Up