Howdy, Stranger!
We are about to switch to a new forum software. Until then we have removed the registration on this forum.
Categories
- All Categories 25.7K
- Announcements & Guidelines 13
- Common Questions 30
- Using Processing 22.1K
- Programming Questions 12.2K
- Questions about Code 6.4K
- How To... 4.2K
- Hello Processing 72
- GLSL / Shaders 292
- Library Questions 4K
- Hardware, Integration & Other Languages 2.7K
- Kinect 668
- Arduino 1K
- Raspberry PI 188
- Questions about Modes 2K
- Android Mode 1.3K
- JavaScript Mode 413
- Python Mode 205
- Questions about Tools 100
- Espanol 5
- Developing Processing 548
- Create & Announce Libraries 211
- Create & Announce Modes 19
- Create & Announce Tools 29
- Summer of Code 2018 93
- Rails Girls Summer of Code 2017 3
- Summer of Code 2017 49
- Summer of Code 2016 4
- Summer of Code 2015 40
- Summer of Code 2014 22
- p5.js 1.6K
- p5.js Programming Questions 947
- p5.js Library Questions 315
- p5.js Development Questions 31
- General 1.4K
- Events & Opportunities 288
- General Discussion 365
In this Discussion
- PhiLho December 2013
Strange behavior when exiting exported Windows application with Alt-F4
Can't find any reference to this but if my exported Windows application (P2.0.2 on Win8) is ended using Alt-F4 then a javaw.exe *32 process is left behind consuming CPU cycles. Doing this multiple times (open app then close with Alt-F4) accumulates a new javaw.exe process, each consuming additional resources. Exiting the application with the Escape key leaves no such residual process. Is this a bug, or should I be coding a workaround (trap for and handle Alt-F4) or perhaps both?
Thanks in advance for your input
Answers
Strange... And what about the close button of the frame? How does it behave?