memory-leaks

问题 We're using an older version of ActiveMQ (5.3.2) (see: Is activemq reliable?) We've removed persistence because we needed more speed. Our worker can keep up with the messages, but, even though the queue typically is at 0 pending, after about 45000 messages processed (a message is typically 100 chars long), the Page file is 8GB!! It doesn't stop there though, it continues until 15 GB is reached (Our server has 16gb memory)! Stopping the ActiveMQ process doesn't clean up this pagefile, it

问题 We're using an older version of ActiveMQ (5.3.2) (see: Is activemq reliable?) We've removed persistence because we needed more speed. Our worker can keep up with the messages, but, even though the queue typically is at 0 pending, after about 45000 messages processed (a message is typically 100 chars long), the Page file is 8GB!! It doesn't stop there though, it continues until 15 GB is reached (Our server has 16gb memory)! Stopping the ActiveMQ process doesn't clean up this pagefile, it

问题 When I run my app, OpenGL Driver Monitor says the Textures count is rapidly increasing — within 30 seconds the Textures count increases by about 45,000. But I haven't been able to find the leak. I've instrumented every glGen*() call to print out every GL object name it returns — but they're all less than 50, so apparently GL objects created by glGen*() aren't being leaked. It's a large, complex app that renders multiple shaders to multiple FBOs on shared contexts on separate threads, so

问题 When I run my app, OpenGL Driver Monitor says the Textures count is rapidly increasing — within 30 seconds the Textures count increases by about 45,000. But I haven't been able to find the leak. I've instrumented every glGen*() call to print out every GL object name it returns — but they're all less than 50, so apparently GL objects created by glGen*() aren't being leaked. It's a large, complex app that renders multiple shaders to multiple FBOs on shared contexts on separate threads, so

问题 I run heavy JavaScript every 5 seconds and task manager shows constant increase of memory usage. However Heap snapshot doesn't. If I stop the script, memory is cleared after about half a minute two minutes. UPDATE: If I leave the script for a long time, the memory increases until the browser crashes. I also tried to run timeline test of chrome dev tools, and they also don't show the increase of memory usage, same as Heap snapshot. So I guess it's some kind of a leak, but I can't understand

问题 I'm trying to find memory issues in my app. When I use Xcode's debug navigator for memory issues I see increase in the overall usage of the application. For a specific flow, when I go back and forth I don't see memory being persisted. However if I go through same flow and instrument using Allocations, I do see 3Mbs getting persisted every time I go back and forth. Is Xcode's debug navigator not reliable or they're measuring something different or something else?! EDIT: So I've been told the

问题 This question already has answers here : is memory leak? why java.lang.ref.Finalizer eat so much memory (2 answers) Closed 4 years ago . Even with 7G of heap space, this will run out of memory. import scala.collection.mutable.Set class Foo() { val anEmptySet: Set[Int] = Set() def bar(ints: Traversable[Int]): Unit = {} override def finalize() { bar(anEmptySet) super.finalize() } } object FooTest { def main(args: Array[String]): Unit = { for (i <- 0 to 100000000) { val f = new Foo() } } } What

问题 Assume I have a C program (running under Linux) which manipulates many data structures, some complex, several of which can grow and shrink but should not in general grow over time. The program is observed to have a gradually increasing RSS over time (more so than can be explained by memory fragmentation). I want to find what is leaking. Running under valgrind is the obvious suggestion here, but valgrind (with --leak-check=full and --show-reachables=yes ) shows no leak. I believe this to be

问题 I have a very simple JFrame window that contains one button: No . In the main function I set setVisible(true); my JFrame and in the No button listener I want to close the window so I set the visibility to false: setVisible(false); and after that I do System.exit(0); in order to prevent possible memory leaks when running the program many times. I have two questions: Do I really need to System.exit(0); in the above case? If I have this JFrame as a popup window, I can't really use System.exit(0)

问题 What does it mean when Valgrind reports o bytes lost, like here: ==27752== 0 bytes in 1 blocks are definitely lost in loss record 2 of 1,532 I suspect it is just an artifact from creative use of malloc , but it is good to be sure (-; EDIT: Of course the real question is whether it can be ignored or it is an effective leak that should be fixed by freeing those buffers. 回答1: Yes, this is a real leak, and it should be fixed. When you malloc(0) , malloc may either give you NULL, or an address