Author Topic: drserver - wxWidgets error - and many unhandled exception windows  (Read 2402 times)

2017-12-19, 23:44:06

J

  • Active Users
  • **
  • Posts: 14
    • View Profile
please see attached image

So lately this wxwidgets error has been popping up when running drserver but this is the first time I have been able to get a clear screen grab of the error window as it is usually covered in unhandled exception windows.

For some mild entertainment:
You may notice up/down arrows on the bottom right near the system tray.
This is a partial screenshot of an ultrawide monitor and I had to press the down arrow 5 times to get to the bottom row of icons from all the error messages.
I found this amusing.

Anyway, the error seems to appear at random and is not isolated to any specific machine. Hopefully there is just a try/catch missing somewhere.

3dsmax 2015, Corona 1.6.3

2018-01-03, 13:02:06
Reply #1

maru

  • Corona Team
  • Active Users
  • ****
  • Posts: 13667
  • Marcin
    • View Profile
I think a minidump generated from the application that crashed could help: https://coronarenderer.freshdesk.com/support/solutions/articles/5000524006
Another thing is that this is 1.6 hf3, and the current version is 1.7 hf2. Is there a chance you could try with 1.7 hf2 and see if you are getting the same thing?
Marcin Miodek | chaos-corona.com
3D Support Team Lead - Corona | contact us

2018-01-08, 12:39:09
Reply #2

jkacza

  • Active Users
  • **
  • Posts: 9
    • View Profile
I'm using 1.7 hf2 and this behavior happens when DR Server keeps open for 10min, I think.

2018-02-05, 03:30:18
Reply #3

J

  • Active Users
  • **
  • Posts: 14
    • View Profile
I had a computer do the solitaire thing again and I have uploaded a minidump called 1517791431_drserver-wxwidgets-error.dmp

We are not able to update to 1.7 at this time so I cannot test it. It is always difficult to find a suitable time to upgrade as there are always projects with tight deadlines that we do not want to disrupt. Our general policy is not to update any software until at least a few patch releases and that the benefits are worth the effort to switch.

Regardless, jkacza seems to be experiencing the same issue in 1.7.2.