<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv="Content-Type" content="text/html; charset=us-ascii"> <meta name="Generator" content="Microsoft Word 14 (filtered medium)"> <style></style> </head> <body lang="EN-US" link="blue" vlink="purple"> <div class="WordSection1"> 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?<o:p></o:p> <o:p> </o:p> 04/10/2018<o:p></o:p> <o:p> </o:p> flexSA14523.log:The program 'flextrdr_gtk' received an X Window System error.<o:p></o:p> flexSA14523.log-This probably reflects a bug in the program.<o:p></o:p> flexSA14523.log-The error was 'BadLength (poly request too large or internal Xlib length erro'.<o:p></o:p> flexSA14523.log- (Details: serial 28147239 error_code 16 request_code 32 minor_code 0)<o:p></o:p> flexSA14523.log- (Note to programmers: normally, X errors are reported asynchronously;<o:p></o:p> flexSA14523.log- that is, you will receive the error a while after causing it.<o:p></o:p> flexSA14523.log- To debug your program, run it with the --sync command line<o:p></o:p> flexSA14523.log- option to change this behavior. You can then get a meaningful<o:p></o:p> flexSA14523.log- backtrace from your debugger if you break on the gdk_x_error() function.)<o:p></o:p> flexSA14523.log-[13:58:16.163836] - **ERROR** :FtDialog::~FtDialog(): destructor called when m_dialog is NULL<o:p></o:p> --<o:p></o:p> flexSA21884.log:The program 'flextrdr_gtk' received an X Window System error.<o:p></o:p> flexSA21884.log-This probably reflects a bug in the program.<o:p></o:p> flexSA21884.log-The error was 'BadLength (poly request too large or internal Xlib length erro'.<o:p></o:p> flexSA21884.log- (Details: serial 7177316 error_code 16 request_code 32 minor_code 0)<o:p></o:p> flexSA21884.log- (Note to programmers: normally, X errors are reported asynchronously;<o:p></o:p> flexSA21884.log- that is, you will receive the error a while after causing it.<o:p></o:p> flexSA21884.log- To debug your program, run it with the --sync command line<o:p></o:p> flexSA21884.log- option to change this behavior. You can then get a meaningful<o:p></o:p> flexSA21884.log- backtrace from your debugger if you break on the gdk_x_error() function.)<o:p></o:p> flexSA21884.log-[11:16:46.093565] - **ERROR** :FtDialog::~FtDialog(): destructor called when m_dialog is NULL<o:p></o:p> --<o:p></o:p> flexSA21993.log:The program 'flextrdr_gtk' received an X Window System error.<o:p></o:p> flexSA21993.log-This probably reflects a bug in the program.<o:p></o:p> flexSA21993.log-The error was 'BadLength (poly request too large or internal Xlib length erro'.<o:p></o:p> flexSA21993.log- (Details: serial 16919110 error_code 16 request_code 1 minor_code 0)<o:p></o:p> flexSA21993.log- (Note to programmers: normally, X errors are reported asynchronously;<o:p></o:p> flexSA21993.log- that is, you will receive the error a while after causing it.<o:p></o:p> flexSA21993.log- To debug your program, run it with the --sync command line<o:p></o:p> flexSA21993.log- option to change this behavior. You can then get a meaningful<o:p></o:p> flexSA21993.log- backtrace from your debugger if you break on the gdk_x_error() function.)<o:p></o:p> flexSA21993.log-[15:05:10.120525] - **ERROR** :FtDialog::~FtDialog(): destructor called when m_dialog is NULL<o:p></o:p> <o:p> </o:p> 04/09/2018<o:p></o:p> <o:p> </o:p> flexSA28811.log:The program 'flextrdr_gtk' received an X Window System error.<o:p></o:p> flexSA28811.log-This probably reflects a bug in the program.<o:p></o:p> flexSA28811.log-The error was '156'.<o:p></o:p> flexSA28811.log- (Details: serial 9773998 error_code 156 request_code 144 minor_code 5)<o:p></o:p> flexSA28811.log- (Note to programmers: normally, X errors are reported asynchronously;<o:p></o:p> flexSA28811.log- that is, you will receive the error a while after causing it.<o:p></o:p> flexSA28811.log- To debug your program, run it with the --sync command line<o:p></o:p> flexSA28811.log- option to change this behavior. You can then get a meaningful<o:p></o:p> flexSA28811.log- backtrace from your debugger if you break on the gdk_x_error() function.)<o:p></o:p> flexSA28811.log-[10:42:57.150157] - **ERROR** :FtDialog::~FtDialog(): destructor called when m_dialog is NULL<o:p></o:p> <o:p> </o:p> flexSA12824.log:The program 'flextrdr_gtk' received an X Window System error.<o:p></o:p> flexSA12824.log-This probably reflects a bug in the program.<o:p></o:p> flexSA12824.log-The error was 'BadLength (poly request too large or internal Xlib length erro'.<o:p></o:p> flexSA12824.log- (Details: serial 26306665 error_code 16 request_code 32 minor_code 0)<o:p></o:p> flexSA12824.log- (Note to programmers: normally, X errors are reported asynchronously;<o:p></o:p> flexSA12824.log- that is, you will receive the error a while after causing it.<o:p></o:p> flexSA12824.log- To debug your program, run it with the --sync command line<o:p></o:p> flexSA12824.log- option to change this behavior. You can then get a meaningful<o:p></o:p> flexSA12824.log- backtrace from your debugger if you break on the gdk_x_error() function.)<o:p></o:p> flexSA12824.log-[14:30:46.048814] - **ERROR** :FtDialog::~FtDialog(): destructor called when m_dialog is NULL<o:p></o:p> <o:p> </o:p> not sure what the error means. Please help.<o:p></o:p> </div> </body> </html>