New issue
Advanced search Search tips

Issue 721668 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug

Blocked on:
issue 718814



Sign in to add a comment

Find the root cause of Chrome Crash when entering 5/6/7 characters in 'Password' text box of any wi-Fi network

Project Member Reported by hashimoto@chromium.org, May 12 2017

Issue description

(Continued from  issue 718814 )

Chrome Version: 60.0.3086.3/9517.1.0  dev-channel Candy,Daisy and Minnie
OS: Chrome

What steps will reproduce the problem?
(1)Sign into User -> Click on Uber Tray
(2)Now select Network option ->Try to click on any new network -> Enter 5/6/7  characters in 'Password' text box and click on 'Connect button
(3)Now observe Chrome Crash (Please refer video)

Expected: No Crash should be seen on entering 5/6/7 characters in 'Password' text box. It should try to connect to network and if Password is wrong 'Network Connection Error' Notification should be seen

Actual: Instead Chrome crash is seen

This is Regression issue as same is working fine in 59.0.3071.33/9460.20.0 dev-channel Candy

@tbuckley : please confirm the Issue

Below is the Crash id:
6eb10923b0000000

Stack Trace:
Thread 4 CRASHED [SIGABRT @ 0x000003e8000008ad ] MAGIC SIGNATURE THREAD
Stack Quality
100%Show frame trust levels
0x00007ef041165eb2
(libc-2.23.so -raise.c:54)
raise
0x00007ef041167cd5
(libc-2.23.so -abort.c:89)
abort
0x00005a87e5737064
(chrome+ 0x02c3e064)
base::debug::BreakDebugger()
0x00005a87e574a42c
(chrome+ 0x02c5142c)
logging::LogMessage::~LogMessage()
0x00005a87e61a1be3
(chrome+ 0x036a8be3)
dbus::Bus::OnConnectionDisconnectedFilter(DBusConnection*, DBusMessage*, void*)
0x00007ef04273e445
(libdbus-1.so.3.14.8 -dbus-connection.c:4709)
dbus_connection_dispatch
0x00005a87e61a2898
(chrome+ 0x036a9898)
dbus::Bus::ProcessAllIncomingDataIfAny()
0x00005a87e3a3fbb6
(chrome+ 0x00f46bb6)
base::debug::TaskAnnotator::RunTask(char const*, base::PendingTask*)
0x00005a87e3a323c2
(chrome+ 0x00f393c2)
base::MessageLoop::RunTask(base::PendingTask*)
0x00005a87e3a335a8
(chrome+ 0x00f3a5a8)
base::MessageLoop::DoWork()
0x00005a87e3a33dcb
(chrome+ 0x00f3adcb)
base::MessagePumpLibevent::Run(base::MessagePump::Delegate*)
0x00005a87e576e1af
(chrome+ 0x02c751af)
base::RunLoop::Run()
0x00005a87e578e907
(chrome+ 0x02c95907)
base::Thread::ThreadMain()
0x00005a87e5789d0c
(chrome+ 0x02c90d0c)
base::(anonymous namespace)::ThreadFunc(void*)
0x00007ef0424e7557
(libpthread-2.23.so -pthread_create.c:333)
start_thread
0x00007ef04122908c
(libc-2.23.so+ 0x000f708c)
clone
 
Crash bug described in  issue 718814  was fixed by removing "--disable-check" build option from dbus.
The possible root cause of the crash was invalid values (e.g. empty object paths, non-UTF-8 strings) sent over D-Bus.
With --disable-check, it can result in dbus daemon misbehaving and causing chrome crash.
Now we have removed --disable-check, and dbus daemon should just sanely reject invalid values when they are sent.

To avoid repeating this, we should find the actual code which is sending invalid values.
Components: UI>Shell>Networking
Labels: -Pri-2 Pri-3
Status: Assigned (was: Available)

Sign in to add a comment