Vidiwell make CPU allways 100 %
Bug #622867 reported by
Jill Royer
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Vidiwell |
Fix Released
|
Critical
|
Jill Royer | ||
| 0.3 |
Fix Released
|
Critical
|
Jill Royer | ||
Bug Description
After first typing in a new document, vidiwell cpu consumption become huge, like it takes all the available cycle, and cpu is never idle.
Revision history for this message
| Jill Royer (jillro) wrote | #1 |
| Changed in vidiwell: | |
| status: | Confirmed → In Progress |
| Changed in vidiwell: | |
| status: | In Progress → Fix Committed |
| Changed in vidiwell: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
First observation : it only appears when invisible tags are disabled. Probably linked to the fact that applying Gtk.TextTag on text already tagged generate an "expose" event, and that the expose event generate retagging... and so a kind of infinite loop.
This explication must be checked.