Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The linux device crashed if we do network provisioning twice #4269

Closed
yufengwangca opened this issue Dec 26, 2020 · 1 comment · Fixed by #4770
Closed

The linux device crashed if we do network provisioning twice #4269

yufengwangca opened this issue Dec 26, 2020 · 1 comment · Fixed by #4770
Assignees
Labels
crash linux p1 priority 1 work
Milestone

Comments

@yufengwangca
Copy link
Contributor

Problem

The linux device crashed if we do network provisioning twice:
chip::DeviceLayer::ConnectivityMgrImpl().StartWiFiManagement();
(wait)
chip::DeviceLayer::ConnectivityManagerImpl::ProvisionWiFiNetwork(ssid, passwd);
(wait)
chip::DeviceLayer::ConnectivityManagerImpl::ProvisionWiFiNetwork(ssid, passwd);

According to the backtrace, seems we have some kind of double free issue:

#0 0x0000fffff7a3000c in g_type_check_instance_is_fundamentally_a () at /lib/aarch64-linux-gnu/libgobject-2.0.so.0
#1 0x0000fffff7a139b8 in g_object_unref () at /lib/aarch64-linux-gnu/libgobject-2.0.so.0
#2 0x0000aaaaaaae46a4 in chip::DeviceLayer::ConnectivityManagerImpl::ProvisionWiFiNetwork(char const*, char const*)
(this=0xaaaaaab919b8 <chip::DeviceLayer::ConnectivityManagerImpl::sInstance>, ssid=0xffffffffe7d0 "Nest-T", key=0xffffffffe7f8 "Nesttesting")
at ../third_party/connectedhomeip/src/platform/Linux/ConnectivityManagerImpl.cpp:849

 #### Proposed Solution
<suggested fix, suggested enhancement>
@yufengwangca yufengwangca self-assigned this Dec 26, 2020
@woody-apple woody-apple added this to the V0.7 milestone Feb 2, 2021
@woody-apple woody-apple added the p1 priority 1 work label Feb 2, 2021
@woody-apple
Copy link
Contributor

@yufengwangca What are the next steps here? Looks like you have reliable repo-steps, and a stack trace?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
crash linux p1 priority 1 work
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants