You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Operating System: Linux
ESP32-MPY-Jama Version: 1.2 (Compiled from source)
The problem occurs when I attempt rapid printing using the Jama serial connection terminal. The application struggles to keep up with the rapid output, resulting in lag and delayed printing. Additionally, the CPU usage increases significantly, reaching 100% and eventually causing the application to crash.
I have noticed that when using other terminal programs like picocom or the commonly known puTTY, rapid printing runs smoothly without any issues. This leads me to wonder if the developer has implemented a different communication mechanism in the Jama app, which could be causing the performance discrepancy.
Please let me know if there are any specific logs, error messages, or steps to reproduce the issue that would be helpful in diagnosing and addressing the problem.
The text was updated successfully, but these errors were encountered:
Operating System: Linux
ESP32-MPY-Jama Version: 1.2 (Compiled from source)
The problem occurs when I attempt rapid printing using the Jama serial connection terminal. The application struggles to keep up with the rapid output, resulting in lag and delayed printing. Additionally, the CPU usage increases significantly, reaching 100% and eventually causing the application to crash.
I have noticed that when using other terminal programs like
picocom
or the commonly knownpuTTY
, rapid printing runs smoothly without any issues. This leads me to wonder if the developer has implemented a different communication mechanism in the Jama app, which could be causing the performance discrepancy.Please let me know if there are any specific logs, error messages, or steps to reproduce the issue that would be helpful in diagnosing and addressing the problem.
The text was updated successfully, but these errors were encountered: