Bug #615
GDB_MI2 high cpu usage (One core is fully loaded)
| Status: | Approved | Start date: | 12/21/2013 | |
|---|---|---|---|---|
| Priority: | High | Due date: | ||
| Assignee: | Miroslav Fidler | % Done: | 100% | |
| Category: | IDE | Spent time: | - | |
| Target version: | - |
Description
It seems that GDB_MI2 has got infinity loop and one core is always fully loaded when debugging.
- I recommend "top" command to check cpu usage by application on GNU/Linux.
History
#1 Updated by Zbigniew Rebacz over 10 years ago
- Assignee deleted (
Miroslav Fidler)
#2 Updated by Miroslav Fidler over 10 years ago
I have to ask for more detailed description (here everything seems to work just fine).
#3 Updated by Zbigniew Rebacz over 10 years ago
- File GDB_MI2_High_CPU_Usage.png added
Hello Mirek,
Now, I know how to reproduce this bug:
1. Turn on TheIDE.
2. Select any package.
3. Debug with GDB_MI2.
4. Click on TheIDE (If you don't click on IDE the CPU usage will be on normal level (around 2-3% CPU usage)).
5. Measuring CPU usage using your favorite application like "top".
6. Stop debugging.
7. From now, every debug session associated with high CPU usage.
Personally, I think that the main problem is that GDB_MI2 completely blocks TheIDE interface. Above situation can contribute to bugs like this.like this.
#4 Updated by Miroslav Fidler over 10 years ago
- Status changed from New to Ready for QA
- Assignee set to Zbigniew Rebacz
Reproduced and fixed. Thanks for detailed bug report.
#5 Updated by Zbigniew Rebacz over 10 years ago
- Status changed from Ready for QA to Approved
#6 Updated by Zbigniew Rebacz over 10 years ago
- Status changed from Approved to New
- Assignee changed from Zbigniew Rebacz to Miroslav Fidler
Hello Mirek,
IDE can be still lock by clicking on "Autos"(Enable by default) "Local", "Watches" tabs. Only "Explorer" tab dosen't block ide.
#7 Updated by Zbigniew Rebacz about 10 years ago
- Status changed from New to In Progress
#8 Updated by Massimo Del Fedele about 10 years ago
- Status changed from In Progress to Ready for QA
- % Done changed from 0 to 100
#9 Updated by Miroslav Fidler about 10 years ago
- Status changed from Ready for QA to Approved
#10 Updated by Massimo Del Fedele about 10 years ago
- Status changed from Approved to Ready for QA
Gdb_MI2 was completely refactored, with data display in background (timed callback or MT).
Most lags/cpu usage should be gone now.
Please re-test.
#11 Updated by Miroslav Fidler about 10 years ago
- Status changed from Ready for QA to Approved