Frama-C Bug Tracking System - Frama-C
View Issue Details
0000036Frama-CPlug-in > jessiepublic2009-04-07 15:262009-06-23 18:03
virgile 
virgile 
normalminoralways
closedfixed 
Frama-C Lithium-20081201 
Frama-C Beryllium-20090601-beta1 
0000036: GUI blocked (100% cpu used) when requested to display an assertion
[bug 7497 from old bts, reported by David Mentré] Hello, If I do: * Launch Jessie GUI on attached evoting.c file: "rama-c -jessie-analysis -jessie-atp alt-ergo -jessie-std-stubs -jessie-gui evoting.c"; * Enter Ctrl+C to collapse all functions; * Expand function "main Safety"; * Click on precondition 64. The GUI is blocked, using 100% of CPU. Yours, d.
Looks a bug in gwhy itself
No tags attached.
Issue History
2009-04-07 15:26virgileNew Issue
2009-04-07 15:41signolesStatusnew => acknowledged
2009-04-10 10:15signolesStatusacknowledged => assigned
2009-04-10 10:15signolesAssigned To => cmarche
2009-05-22 16:21cmarcheNote Added: 0000089
2009-05-22 16:21cmarcheStatusassigned => acknowledged
2009-05-22 18:31monateNote Added: 0000090
2009-06-18 17:08cmarcheStatusacknowledged => assigned
2009-06-18 17:08cmarcheAssigned Tocmarche => virgile
2009-06-19 16:16monateStatusassigned => resolved
2009-06-19 16:16monateFixed in Version => Frama-C Beryllium beta-1
2009-06-19 16:16monateResolutionopen => fixed
2009-06-23 18:02signolesStatusresolved => closed

Notes
(0000089)
cmarche   
2009-05-22 16:21   
The problem is that gwhy is trying to display the jc file, with colr highlighting, and it takes a LONG time
(0000090)
monate   
2009-05-22 18:31   
The performance issue stems from the hiliting tags creation. See in frama-c/src/gui/gtk_helper.ml how make_tag is implemented.