Bug 47987 - Web Inspector: crash at remote debugging disconnect
Summary: Web Inspector: crash at remote debugging disconnect
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: Web Inspector (Deprecated) (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-20 07:03 PDT by Ilya Tikhonovsky
Modified: 2010-10-20 07:13 PDT (History)
10 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ilya Tikhonovsky 2010-10-20 07:03:56 PDT
1) run with remote-debugging-port flag
2) open a site
3) open http://localhost:9222 in another instance
4) select a page for debugging
5) navigate back to http://localhost:9222 

crash call stack
------------
[16159:23043:10513978127127:FATAL:/Users/Shared/loislo/Projects/chromium/src/base/ref_counted.cc(69)] Check failed: !in_dtor_. 
Backtrace:
	0   Chromium Framework                  0x00c64104 StackTrace::StackTrace() + 32
	1   Chromium Framework                  0x00c7b13d logging::LogMessage::~LogMessage() + 63
	2   Chromium Framework                  0x00ca95e9 base::subtle::RefCountedThreadSafeBase::AddRef() const + 177
	3   Chromium Framework                  0x01b4176d base::RefCountedThreadSafe<ListenSocket, base::DefaultRefCountedThreadSafeTraits<ListenSocket> >::AddRef() + 17
	4   Chromium Framework                  0x01b41b0b scoped_refptr<HttpListenSocket>::scoped_refptr(HttpListenSocket*) + 39
	5   Chromium Framework                  0x01b41b28 scoped_refptr<HttpListenSocket> make_scoped_refptr<HttpListenSocket>(HttpListenSocket*) + 27
	6   Chromium Framework                  0x01b3d290 DevToolsHttpProtocolHandler::OnClose(HttpListenSocket*) + 312
	7   Chromium Framework                  0x01b61d0f HttpListenSocket::DidClose(ListenSocket*) + 51
	8   Chromium Framework                  0x0136d240 ListenSocket::Close() + 58
	9   Chromium Framework                  0x01b63163 HttpListenSocket::Close() + 17
	10  Chromium Framework                  0x0136d99a ListenSocket::Read() + 218
	11  Chromium Framework                  0x0136d2fa ListenSocket::OnFileCanReadWithoutBlocking(int) + 84
	12  Chromium Framework                  0x00cec8ea base::MessagePumpLibevent::FileDescriptorWatcher::OnFileCanReadWithoutBlocking(int, base::MessagePumpLibevent*) + 48
	13  Chromium Framework                  0x00cec961 base::MessagePumpLibevent::OnLibeventNotification(int, short, void*) + 105
	14  Chromium Framework                  0x0103eccf event_process_active + 294
	15  Chromium Framework                  0x0103f012 event_base_loop + 373
	16  Chromium Framework                  0x00ced137 base::MessagePumpLibevent::Run(base::MessagePump::Delegate*) + 807
	17  Chromium Framework                  0x00c82cf8 MessageLoop::RunInternal() + 222
	18  Chromium Framework                  0x00c82d13 MessageLoop::RunHandler() + 17
	19  Chromium Framework                  0x00c82d77 MessageLoop::Run() + 35
	20  Chromium Framework                  0x00cc083d base::Thread::Run(MessageLoop*) + 17
	21  Chromium Framework                  0x00cc0d11 base::Thread::ThreadMain() + 337
	22  Chromium Framework                  0x00c9f5ac ThreadFunc(void*) + 30
	23  libSystem.B.dylib                   0x983b181d _pthread_start + 345
	24  libSystem.B.dylib                   0x983b16a2 thread_start + 34

------------
Comment 1 Pavel Feldman 2010-10-20 07:13:16 PDT
This is a pure Chrome issue.