[Bug 478165] New: fix crash when stats updated and creation event thread has not ended



If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=478165

  chronojump | chronojump | Ver: unspecified
           Summary: fix crash when stats updated and creation event thread
                    has not ended
           Product: chronojump
           Version: unspecified
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: major
          Priority: Normal
         Component: chronojump
        AssignedTo: xaviblas cvs gnome org
        ReportedBy: xaviblas cvs gnome org
         QAContact: xaviblas cvs gnome org
     GNOME version: Unspecified
   GNOME milestone: Unspecified


If stats are openede, sometimes chronojump can crash when a new event is added.


Normally this is output:
----------WRITING----------
INSERT INTO jumpRj (uniqueID, personID, sessionID, type, tvMax, tcMax, fall,
weight, description, tvAvg, tcAvg, tvString, tcString, jumps, time, limited    
)VALUES (NULL, 5, 2, 'RJ(j)', 0.700000000000001, 0.35, '20', '0', '',
0.600000000000001, 0.275, '0.5=0.700000000000001', '0.35=0.2', 2, 1.75, '2J')
ON JUMP RJ FINISHED
----------FILLING treeview stats---------------
SELECT MAX(jumps) from jumpRj WHERE ( sessionID == 2) group by jumps order by
jumps DESC limit 1




but this crashes:

----------WRITING----------
INSERT INTO jumpRj (uniqueID, personID, sessionID, type, tvMax, tcMax, fall,
weight, description, tvAvg, tcAvg, tvString, tcString, jumps, time, limited    
)VALUES (NULL, 5, 2, 'RJ(j)', 0.45, 0.25, '20', '0', '', 0.45, 0.225,
'0.45=0.45', '0.25=0.2', 2, 1.35, '2J')
ON JUMP RJ FINISHED
----------FILLING treeview stats---------------
SELECT MAX(jumps) from jumpRj WHERE ( sessionID == 2) group by jumps order by
jumps DESC limit 1
RunningThe application 'chronojump.prg' lost its connection to the display
:0.0;
most likely the X server was shut down or you killed/destroyed
the application.


Probably thread should end before.

Another sample:

----------WRITING----------
INSERT INTO jumpRj (uniqueID, personID, sessionID, type, tvMax, tcMax, fall,
weight, description, tvAvg, tcAvg, tvString, tcString, jumps, time, limited    
)VALUES (NULL, 5, 2, 'RJ(j)', 0.7, 0.35, '20', '0', '', 0.55, 0.325, '0.7=0.4',
'0.35=0.3', 2, 1.75, '2J')
ON JUMP RJ FINISHED
----------FILLING treeview stats---------------
SELECT MAX(jumps) from jumpRj WHERE ( sessionID == 2) group by jumps order by
jumps DESC limit 1
RunningSELECT person.name, person.sex, sessionID, ((tvavg-tcavg)*100/tcavg) AS
rj_index, tcString, tvString, fall, jumpRj.type  FROM jumpRj, person,
jumpRjType WHERE ( sessionID == 2)  AND jumpRj.Type == jumpRjType.name  AND
jumpRj.personID == person.uniqueID ORDER BY  rj_index DESC, tvavg DESC 
The program 'chronojump.prg' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadRequest (invalid request code or no such operation)'.
  (Details: serial 678608 error_code 1 request_code 0 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=478165.



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]