Obsolete
Status Update
Comments
en...@google.com <en...@google.com>
cf...@google.com <cf...@google.com> #2
The G-suite documentation[1] provides this information, but I have submitted a feature request to make it clear on the Cloud DNS public documentation and the Cloud Console. However, I can't provide you with an ETA or guarantee the implementation of this feature, but rest assured that Google strives on improving its products and that your feedback helps us do just that.
Any future updates to this feature will be posted here.
[1]https://support.google.com/a/answer/173535
Any future updates to this feature will be posted here.
[1]
Description
steps to reproduce:
1.enable libc.debug.malloc 1 for all process throght the property seting as below
adb shell "echo libc.debug.malloc=1 >> /data/local.prop"
adb shell "chmod 644 /data/local.prop"
adb reboot
2.after phone reboot run monkey test or free test, sometimes deadlock occur, bactrace maybe as below: child process block on mutex
#00 pc 0000000000019c58 /system/lib64/libc.so (syscall+28)
#01 pc 00000000000201dc /system/lib64/libc.so (pthread_mutex_lock+148)
#02 pc 000000000000316c /system/lib64/libc_malloc_debug_leak.so
#03 pc 00000000000197d4 /system/lib64/libc.so (malloc+20)
expected:
system can run smoothly
Issue root cause:
malloc_debug_leak.cpp leak_malloc/leak_free get g_hash_table->lock in parent process then fork child process, due to mutex in lock state and can't release, so child process can't get the mutex and block forever.
Suggest fix method:
register pthread_atfork callback to sync the g_hash_table->lock.