After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 478165 - fix crash when stats updated and creation event thread has not ended
fix crash when stats updated and creation event thread has not ended
Status: RESOLVED FIXED
Product: chronojump
Classification: Other
Component: chronojump
unspecified
Other All
: Urgent major
: ---
Assigned To: Xavier de Blas
Xavier de Blas
Depends on:
Blocks:
 
 
Reported: 2007-09-18 20:32 UTC by Xavier de Blas
Modified: 2007-09-25 23:19 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Xavier de Blas 2007-09-18 20:32:46 UTC
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.)
Comment 1 Xavier de Blas 2007-09-25 23:19:35 UTC
Fixed deactivating automatic stats updating after every test.

In the future threads on tests will be improved and we can check if this still happens