tencent / loli_profiler Goto Github PK
View Code? Open in Web Editor NEWMemory instrumentation tool for android app&game developers.
License: Other
Memory instrumentation tool for android app&game developers.
License: Other
你好。我写一个demo测试了一下。在我的demo中,有一个按钮,每点击一次,都会创建一个线程;在这个线程中,通过jni调用了setValue()方法。
在setValue()方法中,有一个for循环,每1s钟通过malloc()分配了一个3.8M的内存;在setValue()的末尾又调用free()方法释放了内存;
我的问题是:
按照文档:https://github.com/Tencent/loli_profiler/blob/master/docs/GAME_ENGINE_CN.md 修改UE 4.27源码,测试下来发现:
- 修改MallocBinned2.h MallocBinned2.cpp 不能跟踪到实际内存分配
- 修改MallocBinned3.h MallocBinned3.cpp 不能跟踪到
去修改AndroidPlatformMemory.cppx强制降级为FMallocAnsi,可以跟踪到,但发现跟踪到内存增量只有47MB, 但实际PSS增长100MB,有50多MB没跟踪到,求大神解答?
sindney,你好!
请问LoliProfiler是否支持memalign、mmap/mmap64的监控?
i cannot captured records when i debug my debugable app.
i want to konw is it caused by my UNROOT phone?
and loliprofiler show,
Starting application ...
Application Started!
Connecting to application server ...
Cached 0 records.
Captured 0 records.
9-18 17:55:51.428 25222 25222 I Loli : JNI_OnLoad
09-18 17:55:51.428 25222 25222 I Loli : mode: 0, build: default, minRecSize: 256, blacklist: 0, hookLibs: libunity,libil2cpp,libmtmap.so,libtbtengine.so,
09-18 17:55:51.429 25222 25222 I Loli : loli start status 0
09-18 17:55:51.432 25222 25342 I Loli : libxxx.so (/data/app/com.) is loaded
09-18 17:55:51.432 25222 25342 I Loli : libxxx.so (/data/app/com.) is loaded
09-18 17:55:51.441 25222 25342 I Loli : loaded in Android at 0x07061000
09-18 17:55:51.441 25222 25342 E Loli : failed to open
09-18 17:55:51.441 25222 25342 I Loli : Error dlopen:
09-18 17:55:51.441 25222 25342 I Loli : loaded in Android at 0x07061000
09-18 17:55:51.441 25222 25342 E Loli : failed to open
09-18 17:55:51.441 25222 25342 I Loli : Error dlopen:
09-18 17:55:51.441 25222 25342 I Loli : loaded in Android at 0x07061000
09-18 17:55:51.441 25222 25342 E Loli : failed to open
09-18 17:55:51.441 25222 25342 I Loli : Error dlopen:
09-18 17:55:51.441 25222 25342 I Loli : loaded in Android at 0x07061000
09-18 17:55:51.441 25222 25342 E Loli : failed to open
09-18 17:55:51.441 25222 25342 I Loli : Error dlopen:
09-18 17:55:53.789 25222 25341 I Loli : Client connected
09-18 17:58:11.492 25222 25341 I Loli : Client disconnected, ecode: 0
你好,我们想集成到自动化测试中,想了解下是否支持命令行调用的方式
在检查时间段Leak时提示需要mark time,但这个操作在ui和文档里都没有看到有做提示,最后阅读源码才看到是Shift+拖拽。
能否改成默认拖拽就是mark Time,Ctrl+拖拽是移动坐标轴;或者是hover时候弹窗提示一下组合键,这个键位组合确实不容易发现,也缺少指引。
大神 ,我想把文档都看懂一遍, Instrumented 和 Frame pointer 这两个优化的介绍我没太懂。
Unreal Engine 4 和 Unity Engine,是游戏引擎吗,是不是我们项目中没有用Unreal Engine 4 、Unity Engine这两个 ,我就不用看
Instrumented 和 Frame pointer 这俩优化的介绍了。
launch之后就一直卡在
Injecting libloli.so xxx
meminfo折线图里面有显示,程序正常运行,就是StackTrack里面什么也不显示,空的。
用的是Ue4的 Demo工程,adb logcat -s Loli输出,求楼主看看还有救吗?祈求回复阿
C:\Users\luo>adb logcat -s Loli
--------- beginning of system
--------- beginning of main
11-24 09:41:11.508 7137 7137 I Loli : JNI_OnLoad
11-24 09:41:11.509 7137 7137 I Loli : mode: 1, build: default, minRecSize: 10240, blacklist: 0, hookLibs: libUE4.so,
11-24 09:41:11.510 7137 7137 I Loli : loli start status 0
11-24 09:41:11.512 7137 7241 I Loli : libUE4.so (/data/app/com.YourCompany.luo-NgvYhgqdItpy03Kvqg0OPA==/lib/arm64/libUE4.so) is loaded
11-24 09:41:11.526 7137 7241 I Loli : loaded in Android at 0x6ff93000
11-24 09:41:11.526 7137 7241 E Loli : failed to open
11-24 09:41:11.526 7137 7241 I Loli : Error dlopen:
11-24 09:41:11.541 7137 7241 I Loli : All desired libraries are loaded.
一直提示如下:
Starting application ...
Application Started!
Connecting to application server ...
Connection lost ...
Kill your app or re-plug USB cable and try again.
翻了下FQA说是可能无法连接 apk中 的服务器,需要提供网络权限。目前判断网络权限应该是的,可以正常连接游戏服务器。是不是还需要前置的集成工作才能使用?logcat没有捕捉到相关的日志
Lanuch形式启动时,应该是jdwp不好使 log里显示 ERROR/jdwp : [-] Exception: unpack requires a string argument of length 11。
我换Attach方式启动却好使(说明我配置什么的都正确了)。
这是为什么呢,怎么才能解决launch那个报错呢
重启Android机器和电脑也无法连接上设备进行调试,报错信息
Starting application ...
Application Started!
Connecting to application server ...
Connection lost ...
Kill your app or re-plug USB cable and try again.
Will be easier to find leaks after long running.
adb logcat -s Loli
--------- beginning of system
--------- beginning of main
10-25 12:52:29.793 11204 12234 I Loli : Client disconnected, ecode: 0
10-25 12:53:21.589 12742 12742 I Loli : JNI_OnLoad
10-25 12:53:21.589 12742 12742 I Loli : mode: 0, build: default, minRecSize: 256, blacklist: 0, hookLibs: libunity,libil2cpp,
10-25 12:53:21.589 12742 12742 I Loli : loli start status 0
10-25 12:53:24.429 12742 14281 I Loli : Client connected
10-25 12:54:17.871 12742 14281 I Loli : Client disconnected, ecode: 0
adb logcat -s xhook
--------- beginning of system
--------- beginning of main
OS: Android 10.
Device: HONOR ViewPad 6
你好,这个框架说是有unity排查内存泄露的能力,实验下来是不行的,询问后又说需要unity mono层自己定位,unity是自己有profiler可以定位的,但是框架的开发目的就是替代这些能力;
是这样的如果做不到这些能力的话不应该写到readme里面来抬高自己框架的价值,谢谢!!
Application Started!
Connecting to application server ...
Connection lost ...
Kill your app or re-plug USB cable and try again.
看logcat有crash:
r0q:/ $ logcat -b crash
--------- beginning of crash
08-16 15:49:11.424 30326 30326 F libc : Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x763b736be6bbfc in tid 30326 (problemtestdemo), pid 30326 (problemtestdemo)
08-16 15:49:11.687 30443 30443 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
08-16 15:49:11.687 30443 30443 F DEBUG : Build fingerprint: 'samsung/r0qzcx/r0q:13/TP1A.220624.014/S9010ZCU3CWCF:user/release-keys'
08-16 15:49:11.687 30443 30443 F DEBUG : Revision: '14'
08-16 15:49:11.687 30443 30443 F DEBUG : ABI: 'arm64'
08-16 15:49:11.687 30443 30443 F DEBUG : Processor: '4'
08-16 15:49:11.687 30443 30443 F DEBUG : Timestamp: 2024-08-16 15:49:11.477058389+0800
08-16 15:49:11.687 30443 30443 F DEBUG : Process uptime: 17s
08-16 15:49:11.687 30443 30443 F DEBUG : Cmdline: com.example.memoryproblemtestdemo
08-16 15:49:11.687 30443 30443 F DEBUG : pid: 30326, tid: 30326, name: problemtestdemo >>> com.example.memoryproblemtestdemo <<<
08-16 15:49:11.687 30443 30443 F DEBUG : uid: 10373
08-16 15:49:11.687 30443 30443 F DEBUG : tagged_addr_ctrl: 0000000000000001 (PR_TAGGED_ADDR_ENABLE)
08-16 15:49:11.687 30443 30443 F DEBUG : pac_enabled_keys: 000000000000000f (PR_PAC_APIAKEY, PR_PAC_APIBKEY, PR_PAC_APDAKEY, PR_PAC_APDBKEY)
08-16 15:49:11.687 30443 30443 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x00763b736be6bbfc
08-16 15:49:11.687 30443 30443 F DEBUG : x0 00000000d2801168 x1 00763b736be6bbfc x2 0000007ff6ec78e0 x3 00763b736be6bbfb
08-16 15:49:11.687 30443 30443 F DEBUG : x4 000000706157fae8 x5 000000706157fa58 x6 0000007061411200 x7 0000007061411000
08-16 15:49:11.687 30443 30443 F DEBUG : x8 0000000000000001 x9 0000000000007676 x10 0000000000007676 x11 00000070614110b0
08-16 15:49:11.687 30443 30443 F DEBUG : x12 0000000000000000 x13 0000000000000001 x14 ffffffffffffffff x15 000004de3f2ed8b7
08-16 15:49:11.687 30443 30443 F DEBUG : x16 0000000000000001 x17 000000739d6534f8 x18 000000739ca7a000 x19 0000007ff6ec7e00
08-16 15:49:11.687 30443 30443 F DEBUG : x20 0000007ff6ec7a40 x21 0000000000000000 x22 000000706149d568 x23 0000007ff6ec8488
08-16 15:49:11.687 30443 30443 F DEBUG : x24 b40000719b8b2140 x25 000000000000017a x26 000000739c46a000 x27 00000000000007d3
08-16 15:49:11.687 30443 30443 F DEBUG : x28 b40000714b8cab90 x29 0000007ff6ec7910
08-16 15:49:11.687 30443 30443 F DEBUG : lr 000000706151c32c sp 0000007ff6ec7910 pc 000000706151c340 pst 0000000080001000
08-16 15:49:11.687 30443 30443 F DEBUG : backtrace:
08-16 15:49:11.687 30443 30443 F DEBUG : NOTE: Function names and BuildId information is missing for some frames due
08-16 15:49:11.687 30443 30443 F DEBUG : NOTE: to unreadable libraries. For unwinds of apps, only shared libraries
08-16 15:49:11.687 30443 30443 F DEBUG : NOTE: found under the lib/ directory are readable.
08-16 15:49:11.687 30443 30443 F DEBUG : NOTE: On this device, run setenforce 0 to make the libraries readable.
08-16 15:49:11.687 30443 30443 F DEBUG : NOTE: Unreadable libraries:
08-16 15:49:11.687 30443 30443 F DEBUG : NOTE: /data/data/com.example.memoryproblemtestdemo/libloli.so
08-16 15:49:11.687 30443 30443 F DEBUG : #00 pc 000000000010b340 /data/data/com.example.memoryproblemtestdemo/libloli.so
08-16 15:49:11.687 30443 30443 F DEBUG : #1 pc 000000000010c754 /data/data/com.example.memoryproblemtestdemo/libloli.so
08-16 15:49:11.687 30443 30443 F DEBUG : #2 pc 000000000008c534 /data/data/com.example.memoryproblemtestdemo/libloli.so
08-16 15:49:11.687 30443 30443 F DEBUG : #3 pc 0000000000082c90 /data/data/com.example.memoryproblemtestdemo/libloli.so
08-16 15:49:11.687 30443 30443 F DEBUG : #4 pc 00000000000834c4 /data/data/com.example.memoryproblemtestdemo/libloli.so
08-16 15:49:11.687 30443 30443 F DEBUG : #5 pc 000000000006b980 /system/lib64/libbinder.so (android::Parcel::continueWrite(unsigned long)+1020) (BuildId: b856eb1854000ff13fc66d2f822fcb0a)
08-16 15:49:11.687 30443 30443 F DEBUG : #6 pc 000000000006abf8 /system/lib64/libbinder.so (android::Parcel::writeObject(flat_binder_object const&, bool)+152) (BuildId: b856eb1854000ff13fc66d2f822fcb0a)
08-16 15:49:11.687 30443 30443 F DEBUG : #7 pc 000000000006aa3c /system/lib64/libbinder.so (android::Parcel::flattenBinder(android::spandroid::IBinder const&)+916) (BuildId: b856eb1854000ff13fc66d2f822fcb0a)
08-16 15:49:11.687 30443 30443 F DEBUG : #8 pc 0000000000169520 /system/lib64/libandroid_runtime.so (android::android_os_Parcel_writeStrongBinder(_JNIEnv*, _jclass*, long, _jobject*)+72) (BuildId: a34fb35e38cbccfd38d422e9a88ec8e8)
08-16 15:49:11.687 30443 30443 F DEBUG : #9 pc 00000000001cdedc /system/framework/arm64/boot-framework.oat (art_jni_trampoline+108) (BuildId: 5f59674d21f4a72e20c0f2175204a7f8c6806a3e)
08-16 15:49:11.687 30443 30443 F DEBUG : #10 pc 0000000000209a9c /apex/com.android.art/lib64/libart.so (nterp_helper+1948) (BuildId: 289d75599f6112d5757113220599e90b)
08-16 15:49:11.687 30443 30443 F DEBUG : #11 pc 000000000020666c /system/framework/framework.jar (android.os.Parcel.writeStrongBinder+4)
08-16 15:49:11.687 30443 30443 F DEBUG : #12 pc 000000000020a254 /apex/com.android.art/lib64/libart.so (nterp_helper+3924) (BuildId: 289d75599f6112d5757113220599e90b)
08-16 15:49:11.687 30443 30443 F DEBUG : #13 pc 0000000000206694 /system/framework/framework.jar (android.os.Parcel.writeStrongInterface+16)
08-16 15:49:11.687 30443 30443 F DEBUG : #14 pc 000000000020a254 /apex/com.android.art/lib64/libart.so (nterp_helper+3924) (BuildId: 289d75599f6112d5757113220599e90b)
08-16 15:49:11.687 30443 30443 F DEBUG : #15 pc 0000000000232e7e /system/framework/framework.jar (android.app.INotificationManager$Stub$Proxy.enqueueTextToastForDex+78)
08-16 15:49:11.687 30443 30443 F DEBUG : #16 pc 000000000020be84 /apex/com.android.art/lib64/libart.so (nterp_helper+11140) (BuildId: 289d75599f6112d5757113220599e90b)
08-16 15:49:11.687 30443 30443 F DEBUG : #17 pc 000000000038300e /system/framework/framework.jar (android.widget.Toast.show+1302)
08-16 15:49:11.687 30443 30443 F DEBUG : #18 pc 000000000020a254 /apex/com.android.art/lib64/libart.so (nterp_helper+3924) (BuildId: 289d75599f6112d5757113220599e90b)
08-16 15:49:11.687 30443 30443 F DEBUG : #19 pc 00000000000008c8 /data/data/com.example.memoryproblemtestdemo/code_cache/.overlay/base.apk/classes3.dex (com.example.memoryproblemtestdemo.MainActivity.onResume+20)
08-16 15:49:11.687 30443 30443 F DEBUG : #20 pc 000000000020a254 /apex/com.android.art/lib64/libart.so (nterp_helper+3924) (BuildId: 289d75599f6112d5757113220599e90b)
08-16 15:49:11.687 30443 30443 F DEBUG : #21 pc 0000000000246906 /system/framework/framework.jar (android.app.Instrumentation.callActivityOnResume+6)
08-16 15:49:11.687 30443 30443 F DEBUG : #22 pc 000000000020a254 /apex/com.android.art/lib64/libart.so (nterp_helper+3924) (BuildId: 289d75599f6112d5757113220599e90b)
08-16 15:49:11.687 30443 30443 F DEBUG : #23 pc 00000000001d145a /system/framework/framework.jar (android.app.Activity.performResume+150)
08-16 15:49:11.687 30443 30443 F DEBUG : #24 pc 000000000020a254 /apex/com.android.art/lib64/libart.so (nterp_helper+3924) (BuildId: 289d75599f6112d5757113220599e90b)
08-16 15:49:11.687 30443 30443 F DEBUG : #25 pc 00000000001c0544 /system/framework/framework.jar (android.app.ActivityThread.performResumeActivity+184)
08-16 15:49:11.687 30443 30443 F DEBUG : #26 pc 000000000020a254 /apex/com.android.art/lib64/libart.so (nterp_helper+3924) (BuildId: 289d75599f6112d5757113220599e90b)
08-16 15:49:11.687 30443 30443 F DEBUG : #27 pc 00000000001c71c4 /system/framework/framework.jar (android.app.ActivityThread.handleResumeActivity+12)
08-16 15:49:11.687 30443 30443 F DEBUG : #28 pc 000000000020a254 /apex/com.android.art/lib64/libart.so (nterp_helper+3924) (BuildId: 289d75599f6112d5757113220599e90b)
08-16 15:49:11.687 30443 30443 F DEBUG : #29 pc 00000000002f0850 /system/framework/framework.jar (android.app.servertransaction.ResumeActivityItem.execute+24)
08-16 15:49:11.687 30443 30443 F DEBUG : #30 pc 000000000020a254 /apex/com.android.art/lib64/libart.so (nterp_helper+3924) (BuildId: 289d75599f6112d5757113220599e90b)
08-16 15:49:11.687 30443 30443 F DEBUG : #31 pc 00000000002eda30 /system/framework/framework.jar (android.app.servertransaction.ActivityTransactionItem.execute+8)
08-16 15:49:11.687 30443 30443 F DEBUG : #32 pc 000000000020a254 /apex/com.android.art/lib64/libart.so (nterp_helper+3924) (BuildId: 289d75599f6112d5757113220599e90b)
08-16 15:49:11.687 30443 30443 F DEBUG : #33 pc 00000000002f1970 /system/framework/framework.jar (android.app.servertransaction.TransactionExecutor.executeLifecycleState+64)
08-16 15:49:11.687 30443 30443 F DEBUG : #34 pc 000000000020a254 /apex/com.android.art/lib64/libart.so (nterp_helper+3924) (BuildId: 289d75599f6112d5757113220599e90b)
08-16 15:49:11.687 30443 30443 F DEBUG : #35 pc 00000000002f181a /system/framework/framework.jar (android.app.servertransaction.TransactionExecutor.execute+158)
08-16 15:49:11.688 30443 30443 F DEBUG : #36 pc 000000000020a254 /apex/com.android.art/lib64/libart.so (nterp_helper+3924) (BuildId: 289d75599f6112d5757113220599e90b)
08-16 15:49:11.688 30443 30443 F DEBUG : #37 pc 00000000001bc9f2 /system/framework/framework.jar (android.app.ActivityThread$H.handleMessage+298)
08-16 15:49:11.688 30443 30443 F DEBUG : #38 pc 000000000020a254 /apex/com.android.art/lib64/libart.so (nterp_helper+3924) (BuildId: 289d75599f6112d5757113220599e90b)
08-16 15:49:11.688 30443 30443 F DEBUG : #39 pc 00000000001cad72 /system/framework/framework.jar (android.os.Handler.dispatchMessage+38)
08-16 15:49:11.688 30443 30443 F DEBUG : #40 pc 000000000020a254 /apex/com.android.art/lib64/libart.so (nterp_helper+3924) (BuildId: 289d75599f6112d5757113220599e90b)
08-16 15:49:11.688 30443 30443 F DEBUG : #41 pc 00000000001faee6 /system/framework/framework.jar (android.os.Looper.loopOnce+346)
08-16 15:49:11.688 30443 30443 F DEBUG : #42 pc 0000000000209334 /apex/com.android.art/lib64/libart.so (nterp_helper+52) (BuildId: 289d75599f6112d5757113220599e90b)
08-16 15:49:11.688 30443 30443 F DEBUG : #43 pc 00000000001fb654 /system/framework/framework.jar (android.os.Looper.loop+164)
08-16 15:49:11.688 30443 30443 F DEBUG : #44 pc 0000000000209334 /apex/com.android.art/lib64/libart.so (nterp_helper+52) (BuildId: 289d75599f6112d5757113220599e90b)
08-16 15:49:11.688 30443 30443 F DEBUG : #45 pc 00000000001c88ae /system/framework/framework.jar (android.app.ActivityThread.main+214)
08-16 15:49:11.688 30443 30443 F DEBUG : #46 pc 0000000000457e00 /apex/com.android.art/lib64/libart.so (art_quick_invoke_static_stub+576) (BuildId: 289d75599f6112d5757113220599e90b)
08-16 15:49:11.688 30443 30443 F DEBUG : #47 pc 000000000048c038 /apex/com.android.art/lib64/libart.so (_jobject* art::InvokeMethod<(art::PointerSize)8>(art::ScopedObjectAccessAlreadyRunnable const&, _jobject*, _jobject*, _jobject*, unsigned long)+1560) (BuildId: 289d75599f6112d5757113220599e90b)
08-16 15:49:11.688 30443 30443 F DEBUG : #48 pc 000000000048b9f8 /apex/com.android.art/lib64/libart.so (art::Method_invoke(_JNIEnv*, _jobject*, _jobject*, _jobjectArray*) (.__uniq.165753521025965369065708152063621506277)+48) (BuildId: 289d75599f6112d5757113220599e90b)
08-16 15:49:11.688 30443 30443 F DEBUG : #49 pc 0000000000099148 /system/framework/arm64/boot.oat (art_jni_trampoline+120) (BuildId: c1e4535ad118667c012bcf950ce15dd7736d7b04)
08-16 15:49:11.688 30443 30443 F DEBUG : #50 pc 000000000020a2b0 /apex/com.android.art/lib64/libart.so (nterp_helper+4016) (BuildId: 289d75599f6112d5757113220599e90b)
08-16 15:49:11.688 30443 30443 F DEBUG : #51 pc 0000000000500d1a /system/framework/framework.jar (com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run+22)
08-16 15:49:11.688 30443 30443 F DEBUG : #52 pc 0000000000516cfc /system/framework/arm64/boot-framework.oat (com.android.internal.os.ZygoteInit.main+3404) (BuildId: 5f59674d21f4a72e20c0f2175204a7f8c6806a3e)
08-16 15:49:11.688 30443 30443 F DEBUG : #53 pc 0000000000457e00 /apex/com.android.art/lib64/libart.so (art_quick_invoke_static_stub+576) (BuildId: 289d75599f6112d5757113220599e90b)
08-16 15:49:11.688 30443 30443 F DEBUG : #54 pc 000000000058bbc4 /apex/com.android.art/lib64/libart.so (art::JValue art::InvokeWithVarArgs<_jmethodID*>(art::ScopedObjectAccessAlreadyRunnable const&, _jobject*, _jmethodID*, std::__va_list)+912) (BuildId: 289d75599f6112d5757113220599e90b)
08-16 15:49:11.688 30443 30443 F DEBUG : #55 pc 0000000000609af8 /apex/com.android.art/lib64/libart.so (art::JNI::CallStaticVoidMethodV(_JNIEnv*, _jclass*, _jmethodID*, std::__va_list)+172) (BuildId: 289d75599f6112d5757113220599e90b)
08-16 15:49:11.688 30443 30443 F DEBUG : #56 pc 00000000000c1c04 /system/lib64/libandroid_runtime.so (_JNIEnv::CallStaticVoidMethod(_jclass*, _jmethodID*, ...)+124) (BuildId: a34fb35e38cbccfd38d422e9a88ec8e8)
08-16 15:49:11.688 30443 30443 F DEBUG : #57 pc 00000000000ce470 /system/lib64/libandroid_runtime.so (android::AndroidRuntime::start(char const*, android::Vectorandroid::String8 const&, bool)+856) (BuildId: a34fb35e38cbccfd38d422e9a88ec8e8)
08-16 15:49:11.688 30443 30443 F DEBUG : #58 pc 0000000000002570 /system/bin/app_process64 (main+1304) (BuildId: df8ee709f77c2e3b9fca33b5a3ced970)
08-16 15:49:11.688 30443 30443 F DEBUG : #59 pc 000000000004b900 /apex/com.android.runtime/lib64/bionic/libc.so (__libc_init+100) (BuildId: 54071c506231d1ab2d3653b44eddcea5)
^C
请问这是什么问题呢?windows端loliProfile,手机是三星S22
引用网上的资料中的一句话: PSS中已经包含了Private Dirty和Private Clean,但是没包含swapped dirty,所以最终衡量你的进程对物理内存的占用应该是取PSS+Swapped Dirty。
但是看loli的源码中 折线图里面 nativeHeap读的是meminfo dump里的 private dirty 或者psstotal 反正代码应该是没计算 swapped dirty。
这里是否应该加上swapped dirty的值呢?
We need a console version to integrate loli into our automatic test pipeline.
framepointer模式
threshold设置成0byte
如此便有大量的cache文件
stop后 loadsymbol
发现merged callstack的tree里面的堆栈错乱,怀疑是不是由于record量较大导致引起了bug?
如题,我们这边可以修改uniyt引擎的源码,但是这个改动希望只对debug包生效,请问有什么办法吗?
改动:
// 修改文件: Tools/Bee/Bee.Toolchain.Android/AndroidNdkCompiler.cs
// if (Optimization != OptimizationLevel.None)
// {
// // important for performance. Frame pointer is only useful for profiling, but
// // introduces additional instructions into the prologue and epilogue of each function
// // and leaves one less usable register.
// yield return "-fomit-frame-pointer";
// }
yield return "-fno-omit-frame-pointer"; // <- 打开Framepointer选项
查看/data/local/tmp 已经有libloli.so 和 loli2.conf
我在用strict模式测试大型项目,内存申请频繁。
一般连接成功后用几分钟就会弹出:
Print("Connection lost ...");
Print("Kill your app or re-plug USB cable and try again.");
是否意味着我的程序内存申请过多,又为什么会导致断开连接。(这时我的程序没有退出,只是断开连接了)
如下代码 for 中 定义int i。 在嵌套的另一个for中又定义一个 int i。
c++ 这么写没有问题。
但不便于维护代码和后期修改。
void MainWindow::InterpretRecordLibrary(StackRecord& record, StacktraceData& data) {
auto it = callStackMap_.find(record.uuid_);
if (it == callStackMap_.end())
return;
auto& callStack = it.value();
for (int i = 0; i < callStack.size(); i++) {
auto& libName = callStack[i].first;
auto& funcAddr = callStack[i].second;
bool found = false;
for (int i = 0; i < sMapsCache_.size(); i++) {
const auto& cache = sMapsCache_[i];
Matrix for Android v1.0 updates:
Add Memory Hook. A native memory leak detection tool for Android.
Add Pthread Hook. A Java and native thread leak detection tool for Android.
Add Matrix Backtrace Component. A fast native backtrace unwind library based on quicken unwind tables.
It's way faster than libunwind, and if we support this method by default, the usability of loliprofiler will be enhanced.
如题,这边使用了unity3d c#写了一个可能内存泄露的地方,采用il2cpp编译,监控的so库是v8a的;
using System.Collections;
using System.Collections.Generic;
using UnityEngine;
public class Demo : MonoBehaviour
{
private static Sprite leakOne;
public Sprite testSprite;
// Start is called before the first frame update
void Start()
{
leakOne = testSprite;
}
// Update is called once per frame
void Update()
{
}
}
如题,之前提了两个issue指出了这个框架的局限性,指出了这个框架夸大了它的分析能力,建议作者修改readme文档,但是作者本跟不解释就直接关了issue,查了下作者还是腾讯比较高级的开发工程师!本人也是腾讯的工程师,这种态度实在不敢苟同
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.