- html - 出于某种原因,IE8 对我的 Sass 文件中继承的 html5 CSS 不友好?
- JMeter 在响应断言中使用 span 标签的问题
- html - 在 :hover and :active? 上具有不同效果的 CSS 动画
- html - 相对于居中的 html 内容固定的 CSS 重复背景?
当我使用 JetPack Navigation 在 fragment 之间转换时,我很难找到发生泄漏的原因。
请参阅下面的 from 泄漏金丝雀的堆栈跟踪
D/LeakCanary:
┬───
│ GC Root: System class
│
├─ android.view.inputmethod.InputMethodManager class
│ Leaking: NO (InputMethodManager↓ is not leaking and a class is never leaking)
│ ↓ static InputMethodManager.sInstance
├─ android.view.inputmethod.InputMethodManager instance
│ Leaking: NO (DecorView↓ is not leaking and InputMethodManager is a singleton)
│ ↓ InputMethodManager.mNextServedView
├─ com.android.internal.policy.DecorView instance
│ Leaking: NO (LinearLayout↓ is not leaking and View attached)
│ View is part of a window view hierarchy
D/LeakCanary: │ View.mAttachInfo is not null (view attached)
│ View.mWindowAttachCount = 1
│ mContext instance of com.android.internal.policy.DecorContext, wrapping activity com.carepay.flows.CarePayActivity
│ with mDestroyed = false
│ ↓ DecorView.mContentRoot
├─ android.widget.LinearLayout instance
│ Leaking: NO (CarePayActivity↓ is not leaking and View attached)
│ View is part of a window view hierarchy
│ View.mAttachInfo is not null (view attached)
│ View.mWindowAttachCount = 1
│ mContext instance of com.carepay.flows.CarePayActivity with mDestroyed = false
│ ↓ LinearLayout.mContext
├─ com.carepay.flows.CarePayActivity instance
│ Leaking: NO (NavHostFragment↓ is not leaking and Activity#mDestroyed is false)
│ mApplication instance of com.carepay.MemberApp
│ mBase instance of androidx.appcompat.view.ContextThemeWrapper, not wrapping known Android context
│ ↓ CarePayActivity.mFragments
├─ androidx.fragment.app.FragmentController instance
│ Leaking: NO (NavHostFragment↓ is not leaking)
│ ↓ FragmentController.mHost
├─ androidx.fragment.app.FragmentActivity$HostCallbacks instance
│ Leaking: NO (NavHostFragment↓ is not leaking)
│ this$0 instance of com.carepay.flows.CarePayActivity with mDestroyed = false
│ mActivity instance of com.carepay.flows.CarePayActivity with mDestroyed = false
│ mContext instance of com.carepay.flows.CarePayActivity with mDestroyed = false
│ ↓ FragmentActivity$HostCallbacks.mFragmentManager
D/LeakCanary: ├─ androidx.fragment.app.FragmentManagerImpl instance
│ Leaking: NO (NavHostFragment↓ is not leaking)
│ ↓ FragmentManagerImpl.mPrimaryNav
├─ androidx.navigation.fragment.NavHostFragment instance
│ Leaking: NO (Fragment#mFragmentManager is not null)
│ ↓ NavHostFragment.mNavController
│ ~~~~~~~~~~~~~~
├─ androidx.navigation.NavHostController instance
│ Leaking: UNKNOWN
│ Retaining 1313968 bytes in 7994 objects
│ mActivity instance of com.carepay.flows.CarePayActivity with mDestroyed = false
│ mContext instance of com.carepay.flows.CarePayActivity with mDestroyed = false
│ ↓ NavHostController.mOnDestinationChangedListeners
│ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
├─ java.util.concurrent.CopyOnWriteArrayList instance
│ Leaking: UNKNOWN
│ Retaining 1302920 bytes in 7681 objects
│ ↓ CopyOnWriteArrayList.elements
│ ~~~~~~~~
├─ java.lang.Object[] array
│ Leaking: UNKNOWN
│ Retaining 1302896 bytes in 7679 objects
│ ↓ Object[].[2]
D/LeakCanary: │ ~~~
├─ androidx.navigation.ui.ActionBarOnDestinationChangedListener instance
│ Leaking: UNKNOWN
│ Retaining 5425 bytes in 190 objects
│ mActivity instance of com.carepay.flows.CarePayActivity with mDestroyed = false
│ mContext instance of dagger.hilt.android.internal.managers.ViewComponentManager$FragmentContextWrapper, wrapping
│ activity com.carepay.flows.CarePayActivity with mDestroyed = false
│ ↓ ActionBarOnDestinationChangedListener.mContext
│ ~~~~~~~~
├─ dagger.hilt.android.internal.managers.ViewComponentManager$FragmentContextWrapper instance
│ Leaking: UNKNOWN
│ Retaining 4365 bytes in 162 objects
│ mBase instance of com.carepay.flows.CarePayActivity with mDestroyed = false
│ ViewComponentManager$FragmentContextWrapper wraps an Activity with Activity.mDestroyed false
│ ↓ ViewComponentManager$FragmentContextWrapper.fragment
│ ~~~~~~~~
╰→ com.carepay.flows.treatmentdetail.TreatmentDetailFragment instance
Leaking: YES (ObjectWatcher was watching this because com.carepay.flows.treatmentdetail.TreatmentDetailFragment
received Fragment#onDestroy() callback and Fragment#mFragmentManager is null)
Retaining 3565 bytes in 129 objects
key = 3b650fce-861c-463b-8ccb-78255dfc535a
watchDurationMillis = 22434
retainedDurationMillis = 16751
componentContext instance of dagger.hilt.android.internal.managers.ViewComponentManager$FragmentContextWrapper,
wrapping activity com.carepay.flows.CarePayActivity with mDestroyed = false
所有 fragment 转换都会引发此泄漏,因此我将分享来自所选堆栈跟踪中的 fragment 的此 fragment 。
class TreatmentDetailFragment : OverlayFragment(R.layout.fragment_treatment_detail) {
private val binding get() = (_binding as FragmentTreatmentDetailBinding?)!!
private val args: TreatmentDetailFragmentArgs by navArgs()
private val viewModel by viewModels<TreatmentDetailViewModel>()
override fun onCreateView(
inflater: LayoutInflater, container: ViewGroup?,
savedInstanceState: Bundle?
): View {
_binding = FragmentTreatmentDetailBinding.inflate(inflater, container, false)
val adapter = ItemsAdapter()
binding.treatmentItems.adapter = adapter
setupObservers(adapter)
viewModel.fetchTreatment(args.treatmentId, lifecycle)
return binding.root
}
private fun setupObservers(adapter: ItemsAdapter) {
viewModel.treatment.observe(viewLifecycleOwner){ treatment ->
binding.titleView.text = getString(R.string.treatment, treatment.treatmentCode)
binding.treatment = treatment
adapter.items = treatment.getItems()
adapter.notifyDataSetChanged()
}
}
}
OverlayFragment
abstract class OverlayFragment(@LayoutRes layoutResource: Int) : BaseFragment(layoutResource) {
override fun onViewCreated(view: View, savedInstanceState: Bundle?) {
super.onViewCreated(view, savedInstanceState)
val activity = requireActivity() as CarePayActivity
activity.showBackButton(true)
activity.showCloseIcon(true)
activity.showBottomNavigation(View.GONE)
}
}
基础 fragment
@AndroidEntryPoint
abstract class BaseFragment(@LayoutRes layoutResource: Int) : Fragment(layoutResource) {
@Inject
protected lateinit var memberSettingsRepository: MemberSettingsRepository
protected var _binding: ViewBinding? = null
override fun onViewCreated(view: View, savedInstanceState: Bundle?) {
super.onViewCreated(view, savedInstanceState)
val navController = findNavController()
val appBarConfiguration = AppBarConfiguration(
setOf(
R.id.navigation_health,
R.id.navigation_benefits,
R.id.navigation_clinics,
R.id.navigation_account
)
)
val toolbar = view.findViewById<Toolbar>(R.id.toolbar)
val activity = requireActivity() as CarePayActivity
activity.setSupportActionBar(toolbar)
activity.setupActionBarWithNavController(navController, appBarConfiguration)
}
}
Activity
@AndroidEntryPoint
class CarePayActivity : AppCompatActivity() {
@Inject
lateinit var memberSettingsRepository: MemberSettingsRepository
override fun onCreate(savedInstanceState: Bundle?) {
super.onCreate(savedInstanceState)
setContentView(R.layout.activity_carepay)
val navView: BottomNavigationView = findViewById(R.id.nav_view)
val navController = findNavController(R.id.nav_host_fragment)
val inflater = navController.navInflater
val graph = inflater.inflate(R.navigation.mobile_navigation)
when {
intent.hasExtra(RESUMED) -> {
graph.startDestination = R.id.navigation_health
}
else -> {
graph.startDestination = R.id.navigation_setup
}
}
navController.graph = graph
navView.setupWithNavController(navController)
}
override fun onSupportNavigateUp(): Boolean {
return findNavController(R.id.nav_host_fragment).navigateUp() || super.onSupportNavigateUp()
}
override fun onBackPressed() {
val currentDestination = findNavController(R.id.nav_host_fragment).currentDestination
when (currentDestination?.id) {
R.id.navigation_health -> {
val dialog = getDialog(
getString(R.string.exit),
getString(R.string.exit_message, getString(R.string.app_name)),
getString(R.string.yes),
getString(R.string.no),
object : DialogButtonEvents {
override fun onButtonClicked(id: Int) {
if (id == R.id.positiveButton) {
finish()
}
}
})
dialog.show()
dialog.window?.setBackgroundDrawable(ColorDrawable(Color.TRANSPARENT));
}
else -> {
findNavController(R.id.nav_host_fragment).navigateUp()
}
}
}
}
最佳答案
val toolbar = view.findViewById<Toolbar>(R.id.toolbar)
val activity = requireActivity() as CarePayActivity
activity.setSupportActionBar(toolbar)
activity.setupActionBarWithNavController(navController, appBarConfiguration)
这些行会导致泄漏,因为您提供的是
navController
属于
Fragment
到
Activity
,所以每当
Fragment
正在销毁,因为
navController
将无法取消引用.
关于android - 导航 Controller fragment 泄漏,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/65299446/
IntentReceiver 正在泄漏 由于 onDetachedFromWindow 在某些情况下未被调用。 @Override protected void onDetachedFromWind
好吧,我很难追踪这个内存泄漏。运行此脚本时,我没有看到任何内存泄漏,但我的 objectalloc 正在攀升。 Instruments 指向 CGBitmapContextCreateImage >
我编写了一个测试代码来检查如何使用 Instrument(Leaks)。我创建了一个单一 View 应用程序,单击按钮后我加载了一个像这样的新 View ... - (IBAction)btn_clk
我正在使用这个简单的代码并观察单调增加的内存使用量。我正在使用这个小模块将内容转储到磁盘。我观察到它发生在 unicode 字符串上而不是整数上,我做错了什么吗? 当我这样做时: >>> from u
我有以下泄漏的代码。 Instruments 表示,泄漏的是 rssParser 对象。我“刷新”了 XML 提要,它运行了该 block 并且发生了泄漏...... 文件.h @interface
我在我编写的以下代码片段中发现了内存泄漏 NSFileManager *fileManager=[[NSFileManager alloc] init]; fileList=[[fileManager
因此,我正在开发HTML5 / javascript rts游戏。观察一直有几种声音在播放。因此,对我来说,是一段时间后声音听起来像是“崩溃”,并且此浏览器选项卡上的所有声音都停止了工作。我只能通过重
下面是我正在使用的一段代码及其输出。 my $handle; my $enterCount = Devel::Leak::NoteSV($handle); print "$date entry $en
在这篇关于 go-routines 泄漏的帖子之后,https://www.ardanlabs.com/blog/2018/11/goroutine-leaks-the-forgotten-sende
我想知道为什么在执行 ./a.out 后随机得到以下结果。有什么想法我做错了吗?谢谢 http://img710.imageshack.us/img710/8708/trasht.png 最佳答案 正
我正在 Swift 中开发一个应用程序,在呈现捕获我放在一起的二维码的自定义 ViewController 后,我注意到出现了巨大的内存跳跃。 该代码本质上基于以下示例:http://www.appc
下面是我的 javascript 代码片段。它没有按预期运行,请帮我解决这个问题。 function getCurrentLocation() { console.log("insi
我们在生产环境中部署了 3 个代理 Kafka 0.10.1.0。有些应用程序嵌入了 Kafka Producer,它们将应用程序日志发送到某个主题。该主题有 10 个分区,复制因子为 3。 我们观察
我正在使用仪器来检测一些泄漏,但有一些泄漏我无法解决; NSMutableString *textedetails = [[NSMutableString alloc] init];
如果我使用性能工具测试我的代码 - 泄漏,它没有检测到任何泄漏。这是否意味着代码没有泄漏任何内存? 我有一个越狱的 iPhone,我可以监控可用内存。如果有人知道,那就是 SBSettings。我测试
我在从 AddressBook 中获取图像时遇到了很大的问题,下面我粘贴了我的代码。此 imageData 从未被释放,在我的 Allocations Instruments 上它看起来总是在内存中它
- (NSMutableArray *)getArrayValue:(NSArray *)array{ NSMutableArray *valueArray = [NSMutableArra
Instruments 工具说这是一个泄漏,有什么想法吗? 我在 for 循环结束时释放变量对象 在上述方法的开头,这就是我设置变量对象的方式,即自动释放; NSMutableArray *varia
我正在跟踪我的 iOS 应用程序的内存泄漏,我有一个奇怪的泄漏导致我的应用程序崩溃......负责的框架是:CGImageMergeXMPPropsWhithLegacyProps。在某些时候,我的应
我正在尝试使用 NSOperationQueue 在后台线程中执行一个方法,如下所示: NSOperationQueue *queue = [NSOperationQueue new]; NS
我是一名优秀的程序员,十分优秀!