#7071 closed bug (duplicate)
Memory leak in app_server
Reported by: | jonas.kirilla | Owned by: | axeld |
---|---|---|---|
Priority: | normal | Milestone: | R1 |
Component: | Servers/app_server | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description
Running the old Be Sample Code named "Whistle" and moving its sliders using either mouse or keyboard makes app_server gobble up memory which is not returned when the app quits.
I haven't been able to figure out exactly what gets leaked or exactly how it's triggered, but I have made a very stripped down version of Whistle which does trigger the leakage, most of the time. (on a quad core, fwiw) Run this and watch app_server's memory use rise.
http://www.kirilla.com/haiku/StrippedWhistle.zip
I think BeZillaBrowser triggers the same app_server memory leak, which can result in e.g. 500MB still used by app_server, having quit all apps.
Change History (4)
comment:1 by , 14 years ago
comment:2 by , 14 years ago
Could you please check if hrev40364 does also exhibit the bug? Thanks in advance.
comment:3 by , 10 years ago
Blocked By: | 1713 added |
---|---|
Resolution: | → duplicate |
Status: | new → closed |
comment:4 by , 10 years ago
Blocked By: | 1713 removed |
---|
(In #1713) And I can't reproduce the leak anymore, either, so we can finally close this!
The whistle readme says: "A word of caution: Whistle's interface uses app server features that are largely untested, and uses them a lot. The interface *does* leak memory, but we're not sure where the leak is yet."