| | [ Return to Bugs & Features | Roadmap 1.3 | SVN ⇄ GIT ]
STR #3394
| Application: | FLTK Library |
|---|
| Status: | 2 - Closed w/o Resolution |
|---|
| Priority: | 4 - High, e.g. key functionality not working |
|---|
| Scope: | 2 - Specific to an operating system |
|---|
| Subsystem: | None |
|---|
| Summary: | when window is locked (window+L) fltk window cpu usage is very high |
|---|
| Version: | 1.3.4 |
|---|
| Created By: | zery.choi |
|---|
| Assigned To: | AlbrechtS |
|---|
| Fix Version: | Will Not Fix |
|---|
| Update Notification: | |
|---|
Trouble Report Files:
No files
Trouble Report Comments:
| |
| #1 | zery.choi
04:31 Aug 09, 2017 |
| In Window System, when Windows screen is locked (window+L), fltk window size, resize function is called, a cpu usage is very high..
when Windows screen is not locked, it is ok (not spend cpu usage..)
but.. when window screen is locked, below application's cpu usage get high..
#include <FL/Fl.H>
#include <FL/Fl_Window.H>
Fl_Window *window = 0;
int size = 0;
void timerfunc(void* u)
{
size++;
window->resize(50,50, 300+size,200+size);
Fl::repeat_timeout(1, timerfunc, u);
}
int main()
{
window = new Fl_Window(50,50, 300,200);
window->end();
window->show();
Fl::add_timeout(1, timerfunc);
return Fl::run();
} | |
| |
| #2 | AlbrechtS
03:30 Aug 16, 2017 |
| Thanks for the report and the test program, but unfortunately I can't reproduce the issue under Windows 10 with FLTK 1.3.4.
Which Windows system/version do you use? Is it a normal Windows box, a VM (virtual machine), or some kind of Windows Terminal Server? Anything else? | |
| |
| #3 | AlbrechtS
03:44 Aug 16, 2017 |
| Additional question: how did you build your application, e.g. Visual Studio, MinGW, MinGW-w64, Cygwin, ..., and which version? | |
| |
| #4 | zery.choi
02:12 Aug 17, 2017 |
| Thanks for your rapid reply..
My environment is win7, and I built fltk 1.3.4.1 under MS Visual studio 9 and 10.
I tested this program under win7, winxp, win server 2003 and the issue was same. (cpu very high ..)
I found the simple test way. If you run this program first and then cover this window with another window (such as TaskManager), the issue appears | |
| |
| #5 | AlbrechtS
10:16 Dec 07, 2018 |
| Does this STR still apply, is there any new information?
I got one new question: are you maybe using some kind of Windows remote access (terminal server, citrix, whatever it is called...)? | |
| |
| #6 | AlbrechtS
06:38 Jan 01, 2019 |
| This STR has not been updated by the submitter for two or more weeks and has been closed as required by the FLTK Configuration Management Plan. If the issue still requires resolution, please re-submit a new STR.
Sorry, I can't replicate this - and the OP didn't provide more info as requested. | |
[ Return to Bugs & Features ]
|
| |
