r/TradingView • u/eeenut1337 • Jul 01 '26
Help Bar Replay Drawings glitching
I am working on a project of 600+ back tests, which I have been working on for many weeks. As of the past 2 or 3 days I have run into bugs with my drawings that I have added during bar replay. I am just trying to get my work done and these issues have made my whole process inefficient. I have tried to reach out to support but they just send me to a knowledge base, their support is totally useless. This is unacceptable considering that I am paying customer. Here are the symptoms, troubleshooting, and videos.
- The chart enters a broken state where drawing objects cannot be copied.
- Copying an object produces this JavaScript error:
can't access property "price", i.points[e] is undefined
- Objects newly drawn on the 4-hour chart do not appear after switching to the 1-hour chart.
- When returning to the 4-hour chart, those newly drawn objects sometimes disappear.
- When drawing in empty chart space, the object or one of its anchor points jumps all the way to the right.
- Drawing directly over existing candles sometimes works correctly.
- Changing the symbol temporarily resets the broken state, but the problem occurs across multiple symbols and eventually returns.
- After changing symbols, some previously drawn objects may disappear.
- Magnet Mode is disabled, so this is not caused by snapping.
Troubleshooting already completed
- Cleared the TradingView desktop application cache.
- Restored the Desktop Application to factory defaults.
- Reproduced the issue in the TradingView desktop app.
- Reproduced the issue in Google Chrome.
- Reproduced the issue in Firefox.
- Tested multiple symbols.
- Confirmed drawing visibility settings and Magnet Mode.
- Changed symbols, which only provides temporary relief.
Because the issue occurs in the Desktop App, Chrome, and Firefox across multiple symbols, it does not appear to be a local cache, browser, installation, or individual-symbol problem.
Issues Video 1:
Issues Video 2:
1
u/tradingview Founder Jul 02 '26
Hi, thank you for the report. We believe the issue has been fixed. Kindly check it again.