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

[BUG] Crash(SIGSEGV) seen in minimal mdns code during repeated commissioning and unpair attempts #26091

Open
mukulag8293 opened this issue Apr 13, 2023 · 1 comment
Labels
stale Stale issue or PR

Comments

@mukulag8293
Copy link

mukulag8293 commented Apr 13, 2023

Reproduction steps

  1. Commission a thread device
  2. Unpair the device
  3. Reboot the commissioner device
  4. Repeat step 1 to step 3 25 times
  5. Delay between consecutive commands 70-80 secs
Result: Following crash is seen with a SIGSEGV
03-30 18:58:54.849  3464  3464 F libc    : Fatal signal 11 (SIGSEGV), code 1, fault addr 0xa in tid 3464
03-30 18:58:54.930  3472  3472 F DEBUG   : backtrace:
03-30 18:58:54.930  3472  3472 F DEBUG   :     #00 pc 001a2dc4  /system/lib/libace_chip_client.so (_ZNK4mdns7Minimal14ResourceRecord6AppendERNS0_9HeaderRefENS0_12ResourceTypeERNS0_12RecordWriterE+215)
03-30 18:58:54.930  3472  3472 F DEBUG   :     #01 pc 001a1709  /system/lib/libace_chip_client.so
03-30 18:58:54.930  3472  3472 F DEBUG   :     #02 pc 001a1689  /system/lib/libace_chip_client.so (_ZN4mdns7Minimal14ResponseSender11AddResponseERKNS0_14ResourceRecordE+48)
03-30 18:58:54.930  3472  3472 F DEBUG   :     #03 pc 001a2c77  /system/lib/libace_chip_client.so (_ZN4mdns7Minimal13IPv6Responder15AddAllResponsesEPKN4chip4Inet12IPPacketInfoEPNS0_17ResponderDelegateERKNS0_21ResponseConfigurationE+158)
03-30 18:58:54.930  3472  3472 F DEBUG   :     #04 pc 001a13bb  /system/lib/libace_chip_client.so (_ZN4mdns7Minimal14ResponseSender7RespondEjRKNS0_9QueryDataEPKN4chip4Inet12IPPacketInfoERKNS0_21ResponseConfigurationE+378)
03-30 18:58:54.931  3472  3472 F DEBUG   :     #05 pc 0019dbb1  /system/lib/libace_chip_client.so
03-30 18:58:54.931  3472  3472 F DEBUG   :     #06 pc 0019cf21  /system/lib/libace_chip_client.so
03-30 18:58:54.931  3472  3472 F DEBUG   :     #07 pc 00188fbf  /system/lib/libace_chip_client.so (_ZN4chip3app11DnssdServer20AdvertiseOperationalEv+362)
03-30 18:58:54.931  3472  3472 F DEBUG   :     #08 pc 0018b66b  /system/lib/libace_chip_client.so (_ZN4chip10Controller16DeviceController4InitENS0_20ControllerInitParamsE+198)
03-30 18:58:54.931  3472  3472 F DEBUG   :     #09 pc 0018c50f  /system/lib/libace_chip_client.so (_ZN4chip10Controller18DeviceCommissioner4InitENS0_22CommissionerInitParamsE+46)
03-30 18:58:54.931  3472  3472 F DEBUG   :     #10 pc 001928ff  /system/lib/libace_chip_client.so (_ZN4chip10Controller23DeviceControllerFactory17SetupCommissionerENS0_11SetupParamsERNS0_18DeviceCommissionerE+106)
03-30 18:58:54.931  3472  3472 F DEBUG   :     #11 pc 00169ec5  /system/lib/libace_chip_client.so (aceChip_commissionerInit+1216)

Bug prevalence

This was seen during stress testing

GitHub hash of the SDK that was being used

4088a77

Platform

core

Platform Version(s)

No response

Anything else?

addr2line -C -f -e libace_chip_client.so 001a2dc4 001a1709 001a1689 001a2c77 001a13b 0019dbb1 0019cf21 00188fbf 0018b66b 0018c50f 001928ff 00169ec5
nlIOGetUnaligned16(void const*)
/proc/self/cwd/vendor/csa-iot/connectedhomeip/external/nlio/repo/include/nlio-base.h:151
mdns::Minimal::ResponseBuilder::AddRecord(mdns::Minimal::ResourceType, mdns::Minimal::ResourceRecord const&)
/proc/self/cwd/vendor/csa-iot/connectedhomeip/src/lib/dnssd/minimal_mdns/ResponseBuilder.h:92
mdns::Minimal::ResponseSender::AddResponse(mdns::Minimal::ResourceRecord const&)
/proc/self/cwd/vendor/csa-iot/connectedhomeip/src/lib/dnssd/minimal_mdns/ResponseSender.cpp:251 (discriminator 1)
mdns::Minimal::IPv6Responder::AddAllResponses(chip::Inet::IPPacketInfo const*, mdns::Minimal::ResponderDelegate*, mdns::Minimal::ResponseConfiguration const&)
/proc/self/cwd/vendor/csa-iot/connectedhomeip/src/lib/dnssd/minimal_mdns/responders/IP.cpp:69
mdns::Minimal::ResponseSender::Respond(unsigned int, mdns::Minimal::QueryData const&, chip::Inet::IPPacketInfo const*, mdns::Minimal::ResponseConfiguration const&)
/proc/self/cwd/vendor/csa-iot/connectedhomeip/src/lib/dnssd/minimal_mdns/ResponseSender.cpp:179 (discriminator 1)
chip::Dnssd::(anonymous namespace)::AdvertiserMinMdns::AdvertiseRecords(chip::Dnssd::(anonymous namespace)::BroadcastAdvertiseType)
/proc/self/cwd/vendor/csa-iot/connectedhomeip/src/lib/dnssd/Advertiser_ImplMinimalMdns.cpp:936
chip::Dnssd::(anonymous namespace)::AdvertiserMinMdns::Advertise(chip::Dnssd::OperationalAdvertisingParameters const&)
/proc/self/cwd/vendor/csa-iot/connectedhomeip/src/lib/dnssd/Advertiser_ImplMinimalMdns.cpp:540
chip::app::DnssdServer::AdvertiseOperational()
/proc/self/cwd/vendor/csa-iot/connectedhomeip/src/app/server/Dnssd.cpp:175 (discriminator 1)
chip::Controller::DeviceController::Init(chip::Controller::ControllerInitParams)
/proc/self/cwd/vendor/csa-iot/connectedhomeip/src/controller/CHIPDeviceController.cpp:139 (discriminator 1)
chip::Controller::DeviceCommissioner::Init(chip::Controller::CommissionerInitParams)
/proc/self/cwd/vendor/csa-iot/connectedhomeip/src/controller/CHIPDeviceController.cpp:405 (discriminator 4)
chip::Controller::DeviceControllerFactory::SetupCommissioner(chip::Controller::SetupParams, chip::Controller::DeviceCommissioner&)
/proc/self/cwd/vendor/csa-iot/connectedhomeip/src/controller/CHIPDeviceControllerFactory.cpp:324 (discriminator 2)
aceChip_commissionerInit
@mukulag8293 mukulag8293 changed the title [BUG] [BUG] Crash(SIGSEGV) seen in minimal mdns code during repeated commissioning and unpair attempts Apr 13, 2023
@stale
Copy link

stale bot commented Oct 15, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@stale stale bot added the stale Stale issue or PR label Oct 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale Stale issue or PR
Projects
None yet
Development

No branches or pull requests

1 participant