I have been scouring every knowledgebase available to me including exceed/open text resource to figure out why my application is crashing. I basically use exceed to export the display to my windows pc. So far this week, I had 5 crashes. Wondering if anyone knows or have dealt with this in the past?
04/10/2018 flexSA14523.log:The program 'flextrdr_gtk' received an X Window System error. flexSA14523.log-This probably reflects a bug in the program. flexSA14523.log-The error was 'BadLength (poly request too large or internal Xlib length erro'. flexSA14523.log- (Details: serial 28147239 error_code 16 request_code 32 minor_code 0) flexSA14523.log- (Note to programmers: normally, X errors are reported asynchronously; flexSA14523.log- that is, you will receive the error a while after causing it. flexSA14523.log- To debug your program, run it with the --sync command line flexSA14523.log- option to change this behavior. You can then get a meaningful flexSA14523.log- backtrace from your debugger if you break on the gdk_x_error() function.) flexSA14523.log-[13:58:16.163836] - **ERROR** :FtDialog::~FtDialog(): destructor called when m_dialog is NULL -- flexSA21884.log:The program 'flextrdr_gtk' received an X Window System error. flexSA21884.log-This probably reflects a bug in the program. flexSA21884.log-The error was 'BadLength (poly request too large or internal Xlib length erro'. flexSA21884.log- (Details: serial 7177316 error_code 16 request_code 32 minor_code 0) flexSA21884.log- (Note to programmers: normally, X errors are reported asynchronously; flexSA21884.log- that is, you will receive the error a while after causing it. flexSA21884.log- To debug your program, run it with the --sync command line flexSA21884.log- option to change this behavior. You can then get a meaningful flexSA21884.log- backtrace from your debugger if you break on the gdk_x_error() function.) flexSA21884.log-[11:16:46.093565] - **ERROR** :FtDialog::~FtDialog(): destructor called when m_dialog is NULL -- flexSA21993.log:The program 'flextrdr_gtk' received an X Window System error. flexSA21993.log-This probably reflects a bug in the program. flexSA21993.log-The error was 'BadLength (poly request too large or internal Xlib length erro'. flexSA21993.log- (Details: serial 16919110 error_code 16 request_code 1 minor_code 0) flexSA21993.log- (Note to programmers: normally, X errors are reported asynchronously; flexSA21993.log- that is, you will receive the error a while after causing it. flexSA21993.log- To debug your program, run it with the --sync command line flexSA21993.log- option to change this behavior. You can then get a meaningful flexSA21993.log- backtrace from your debugger if you break on the gdk_x_error() function.) flexSA21993.log-[15:05:10.120525] - **ERROR** :FtDialog::~FtDialog(): destructor called when m_dialog is NULL 04/09/2018 flexSA28811.log:The program 'flextrdr_gtk' received an X Window System error. flexSA28811.log-This probably reflects a bug in the program. flexSA28811.log-The error was '156'. flexSA28811.log- (Details: serial 9773998 error_code 156 request_code 144 minor_code 5) flexSA28811.log- (Note to programmers: normally, X errors are reported asynchronously; flexSA28811.log- that is, you will receive the error a while after causing it. flexSA28811.log- To debug your program, run it with the --sync command line flexSA28811.log- option to change this behavior. You can then get a meaningful flexSA28811.log- backtrace from your debugger if you break on the gdk_x_error() function.) flexSA28811.log-[10:42:57.150157] - **ERROR** :FtDialog::~FtDialog(): destructor called when m_dialog is NULL flexSA12824.log:The program 'flextrdr_gtk' received an X Window System error. flexSA12824.log-This probably reflects a bug in the program. flexSA12824.log-The error was 'BadLength (poly request too large or internal Xlib length erro'. flexSA12824.log- (Details: serial 26306665 error_code 16 request_code 32 minor_code 0) flexSA12824.log- (Note to programmers: normally, X errors are reported asynchronously; flexSA12824.log- that is, you will receive the error a while after causing it. flexSA12824.log- To debug your program, run it with the --sync command line flexSA12824.log- option to change this behavior. You can then get a meaningful flexSA12824.log- backtrace from your debugger if you break on the gdk_x_error() function.) flexSA12824.log-[14:30:46.048814] - **ERROR** :FtDialog::~FtDialog(): destructor called when m_dialog is NULL not sure what the error means. Please help.
_______________________________________________ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: https://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
