Status: New
Owner: ----

New issue 3735 by [email protected]: Debugging freezes on evaluation of an object
https://code.google.com/p/v8/issues/detail?id=3735

Steps to reproduce:
1) Please run the attached file in node in debugging mode:
   node debug main.js
It might be necessary to generate the required keys and certificate in advance via:
   openssl genrsa -out agent-key.pem 1024
   openssl req -new -key agent-key.pem -out agent-csr.pem
openssl x509 -req -in agent-csr.pem -signkey agent-key.pem -out agent-cert.pem
2) Submit a breakpoint on line 16:
   debug> sb(16)
3) Continue
   debug> cont
   and navigate to https://localhost:44301/ in the browser.
4) When suspended, try to get variable values:
   debug> repl
   > req._readableState
- this evaluates correctly and prints out the object properties and their values
   > req.connection._buffer
     - we get no answer and node process starts to consume 100% CPU.

This issue was discovered in an IDE, which uses V8 debugging protocol.
As a response of the lookup command to "connection", we get it's buffer property as:
{"name":"_buffer","propertyType":1,"ref":147}
When we issue lookup command for "_buffer", we get no answer and node process starts to consume 100% CPU. The lookup command request looks like:
{"arguments":{"handles":[147],"includeSource":false},"type":"request","seq":79,"command":"lookup"}

Attachments:
        main.js  463 bytes

--
You received this message because this project is configured to send all issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
--- You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to