NativeScript / NativeScript/android
The run-time takes 5+ seconds to respond to Debugger.enable
Nadie ha tomado este issue todavía.
- Lenguaje dominante
- C++
- Estrellas
- 563
- Forks
- 144
- Merge medio
- 10 h 46 min
- PR fusionados (30 d)
- 14
Descripción
Please, provide the details below:
Did you verify this is a real problem by searching Stack Overflow and the other open issues in this repo?
Yes
Tell us about the problem
The run-time takes 5+ seconds to respond to Debugger.enable
Please provide the following version numbers that your issue occurs with:
- CLI: 3.3.1
Please tell us how to recreate the issue in as much detail as possible.
This is reproducible with:
https://github.com/NativeScript/template-master-detail-ts
https://github.com/NativeScript/template-master-detail-ng
https://github.com/NativeScript/template-master-detail-kinvey
against an Android Pixel.
clone https://github.com/NativeScript/template-master-detail-ts
cd template-master-detail-ts
tns platform add android
tns debug android --start
After receiving the Debugger.enable request the run-time would trigger scriptParsed events for all sources in the project (500+ files) first and only then would respond to the Debugger.enable request.
Starting a debug session against any of the listed projects would time out as the JavaScript debugger (Microsoft implementation) in Visual Studio has a non-configurable 5 second timeout on all requests.
In {N} Sidekick the debug session would not timeout but it would still take more than 5 seconds to initialize.
Please note that after receiving a response to Debugger.enable the JavaScript debugger in Visual Studio would start sending Debugger.setBreakpointByUrl for all pre-set breakpoints (again 5s timeout) and if the run-time does not respond to a request the breakpoint would remain inactive.
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Línea de trabajo
Reproduce el retraso con los proyectos template-master-detail indicados en un Android Pixel usando tns debug android --start. Rastrea cómo el runtime gestiona Debugger.enable, scriptParsed y Debugger.setBreakpointByUrl; se considera terminado cuando la inicialización del depurador y los puntos de interrupción preestablecidos se completan sin el tiempo de espera de cinco segundos.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- android, javascript
- Área
- devtools, mobile-dev, performance
- Tipo de issue
- Error
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Estancado
- Claridad
- Necesita aclaración
- Aptitud para principiantes
- 32/100