Logo by Sockratease - Contribute your own Logo!
News: Support us via Flattr FLATTR Link
 
*
Welcome, Guest. Please login or register. June 27, 2017, 02:08:59 AM


Login with username, password and session length



Pages: 1 [2]   Go Down
  Print  
Share this topic on DiggShare this topic on FacebookShare this topic on GoogleShare this topic on RedditShare this topic on StumbleUponShare this topic on Twitter
Author Topic: Version 2.10, Clients Crashing  (Read 574 times)
Description: including a workaround
0 Members and 1 Guest are viewing this topic.
paigan0
Iterator
*
Posts: 182



stephen.sink.9
« Reply #15 on: March 05, 2017, 05:47:32 PM »

Quote
Closing the connection lost Message Box (for the earlier event) caused both Client apps to crash.
Mandelbulber has always given me a "lost connection" box every time I've ever started up any flavor of version 2. I had to stop clicking "ok" and closing that, though, because it now crashes the client if I do so. So, I just leave the message box open and everything works fine.

I have noticed that clients can now come online when I start them in the middle of a render job, and they will sit there as "ready" until the current frame is over, and then start working at the start of the next frame. I no longer have to stop the render and restart with the added client to get it to start working. That's awesome, as I can start with a few clients and then roll them in one by one and watch the render farm get bigger, the render times get smaller, and never have to start and re-stop the whole job.   
Logged

Stephen (Steve) Sink, Paigan Productions
(SoundCloud) http://soundcloud.com/stephen-sink-1
(3D Fractal Music Videos) http://vimeo.com/channels/fractals
CCV
Explorer
****
Posts: 59


« Reply #16 on: March 06, 2017, 01:41:05 AM »

Mandelbulber has always given me a "lost connection" box every time I've ever started up any flavor of version 2. I had to stop clicking "ok" and closing that, though, because it now crashes the client if I do so. So, I just leave the message box open and everything works fine.
Same here, except I'm now using a modified version of 2.10 intended to fix a different networking bug. A side benefit of which is the lost connection problem - ERROR flashing for a fraction of a second before connection is established - also being fixed, so I don't get the message box unless connection is lost by some other means.
I tended to ignore it and just leave it there too. I don't remember the Client crashing, as a rule, when I did get around to clicking it off tho. It definitely does now, if rendering is underway at the time. I want to see what happens when I close it without rendering in progress and I will test it once a current task is complete. (was estimated at about 8 hours, but is going take at least four times that) I have a vague notion it doesn't crash unless rendering, but we'll see...

I have noticed that clients can now come online when I start them in the middle of a render job, and they will sit there as "ready" until the current frame is over, and then start working at the start of the next frame. I no longer have to stop the render and restart with the added client to get it to start working. That's awesome, as I can start with a few clients and then roll them in one by one and watch the render farm get bigger, the render times get smaller, and never have to start and re-stop the whole job.
That is interesting. I didn't know, but will bear it in mind. Thank you.  smiley
Logged
CCV
Explorer
****
Posts: 59


« Reply #17 on: March 08, 2017, 04:46:38 AM »

Mandelbulber has always given me a "lost connection" box every time I've ever started up any flavor of version 2. I had to stop clicking "ok" and closing that, though, because it now crashes the client if I do so. So, I just leave the message box open and everything works fine.

It has generally been my habit to ignore any lost connection message boxes until I'm ready to close the program anyway. That is, after rendering has stopped. In that case, and I tested it again, closing the message box doesn't crash the client. Neither does closing it before starting render, as far as I've checked. It certainly does crash the client when rendering is in progress.

I'm now using mandelbulber2-win64-2.10 - NetRender bug fix version, because the 2.10 release version was producing errors (marked in red in the attachment) which crashed the client(s) as soon as render started. The NetRender bug fix, as an additional benefit, stopped the "Error: Connection" lost problem. So, hopefully, we can look forward to it being gone in the next release. 


* Clients.jpg (240.04 KB, 981x514 - viewed 37 times.)
Logged
Pages: 1 [2]   Go Down
  Print  
 
Jump to:  

Related Topics
Subject Started by Replies Views Last post
Version 1.3.4 is available Mandel Machine Botond Kósa 0 326 Last post November 06, 2014, 05:31:00 PM
by Botond Kósa
Version 1.3.5 is available Mandel Machine Botond Kósa 9 582 Last post November 14, 2014, 11:24:47 AM
by Botond Kósa
Crashing Wave & Source Images Showcase (Rate My Fractal) C.K. 4 359 Last post February 13, 2015, 07:34:27 AM
by Dinkydau
NetRender - better use of clients Feature Requests Dave13 6 364 Last post April 04, 2016, 03:21:01 PM
by Dave13
2.08-3 Constant Crashing - "No Symbol file loaded"' Bug Reporting « 1 2 » CCV 17 715 Last post September 10, 2016, 09:13:14 AM
by Buddhi

Powered by MySQL Powered by PHP Powered by SMF 1.1.21 | SMF © 2015, Simple Machines

Valid XHTML 1.0! Valid CSS! Dilber MC Theme by HarzeM
Page created in 0.175 seconds with 29 queries. (Pretty URLs adds 0.011s, 2q)