memory-leaks

问题 I have a Windows service that periodically check database for new records and processes each record in a new thread (it may take up to 10 minutes). When the service is idle right after it's started it takes like 4 MB of RAM. When it starts processing the first record it goes up to 70+ MB and stays there even when the thread is finished (I guess that's OK, because this memory can soon be needed again). Then on the next request it goes from 70 to about 100 MB and also stays there after the

问题 I have a problem. I created the android app, when I start the app I see 48,09 MB cache memory. My app uses different libraries, has a lot of classes. I can't find a reason why the app uses so many cache memory? How do I find the problem? Interesting thing : When I start an empty app, this app uses approximately 4Mb cache memory , I think it's too much. 来源： https://stackoverflow.com/questions/37792548/mobile-app-uses-a-lot-of-cache-memory

问题 I am facing some strange memory leak in our existing iPad application, Here is a function which gives memory leak in instrument -(NSString *)retriveInfo:(NSString*)fromstring:(NSString*)searchstring { NSArray *arrRetrive = [fromstring componentsSeparatedByString:searchstring]; if([arrRetrive count]!=0){ if ([arrRetrive count]!=1){ NSString *strDisplayOrder = [arrRetrive objectAtIndex:1]; arrRetrive = [strDisplayOrder componentsSeparatedByString:@"<"]; //MEMORY LEAK } } return [arrRetrive

问题 I have one static HashMap for my entire system which contains some object's references; let's call it myHash . The objects are only instantiated once I needed them such as private static HashMap<String, lucene.store.Directory> directories; public static Object getFoo(String key) { if (directories == null) { directories = new HashMap<String, Directory>(); } if (directories.get(key) == null) { directories.put(key, new RAMDirectory()); } return directories.get(key); // warning } Now, Eclipse is

问题 I'm using UMDH(x64) to test memory leak. My code is neither FPO optimized nor using customized allocators. It uses just "new" operator. "Create User Mode stack trace Database" is enabled in the Gflags(x64) for the image that's being tested. I have tracked my application using UMDH both in non-leaky case and leaky case and obtained the logs in both the cases. And compared the logs with UMDH. It has picked the right pdb as evident from its comment lines in the top. Problem: The call stack doesn

问题 I'm having a typical WindowLeaked exception 03-03 21:03:26.441: ERROR/WindowManager(631): Activity com.myapp.Player has leaked window com.android.internal.policy.impl.PhoneWindow$DecorView@45136c38 that was originally added here 03-03 21:03:26.441: ERROR/WindowManager(631): android.view.WindowLeaked: Activity com.myapp.Player has leaked window com.android.internal.policy.impl.PhoneWindow$DecorView@45136c38 that was originally added here 03-03 21:03:26.441: ERROR/WindowManager(631): at android

问题 Can drool 5.1 cause memory leak issues? We are using complex validation rules where we are calling java codes. Each request to backend load 2-3 drool files and new KnowledgeBase is created for each request. Can anyone throw more light on this? private void initRulesEngine() { kbase = KnowledgeBaseFactory.newKnowledgeBase(); if (kbuilder != null) { kbase.addKnowledgePackages(kbuilder.getKnowledgePackages()); } } public void executeRules(BaseUOW requestedUOW) { initRulesEngine(); ksession =

问题 I have an AsyncTask which I need to "restart" if the user does configurations such as Switch Color. When he do so I start the AsyncTask like this: myWorkerClass.clearMemory(); myWorkerClass = new WorkerClass(getApplicationContext(), gv, searchbar, width, scaleButtonText); myWorkerClass.execute(); In the AsyncTask I add a onTextChangeListener to my EditText!(Which causes the MemoryLeak later). To prevent MemoryLeaks I have a Method in my AsyncTask which removes the onTextChangedListener :

问题 I did Analyze and got potential leak of an object stored into warning in my code below + (ABAddressBookRef)getABAddressBookRef { unsigned long long lastAddressBookGeneration = _addressBookGeneration; unsigned long long addressBookGeneration =[[NSThread currentThread].threadDictionary[kAddressBookGeneration] unsignedLongLongValue]; ABAddressBookRef addressBook = (__bridge ABAddressBookRef)[NSThread currentThread].threadDictionary[kAddressBook]; if (addressBook == nil || (addressBookGeneration

问题 I have a very strange, very repeatable leak that doesn't appear to have anything to do with the functions I have defined. As you can see the responsible library is lybsystem_c. Instruments reports a 48B leak when I scroll my grouped table view down below the screen (by dragging very fast). It bounces back, and the red bar appears. Has anyone experienced this issue? Does anyone understand how I might be responsible for this? Is there a way to prove this is a framework bug? Or an Instruments