ByteDance’s VS Code Fork Trae: A Resource-Hungry Tool That Invades Your Privacy

ByteDance’s VS Code Fork Trae: A Resource-Hungry Tool That Invades Your Privacy
Image via Kevin Ku from Pexels

Microsoft’s Visual Studio and AI-Driven Upgrades

Recent reports indicate that Microsoft is gearing up for a significant overhaul of its flagship integrated development environment (IDE), Visual Studio, with a focus on integrating artificial intelligence. Alongside Visual Studio, Microsoft also offers Visual Studio Code (VS Code), a lightweight code editor that has garnered popularity due to its open-source components. This openness allows developers to customize and enhance the platform, leading to various forks, including Anysphere’s Cursor and ByteDance’s Trae IDE.

Concerns Raised About Trae IDE’s Performance

However, a recent analysis conducted by the GitHub user segmentationf4u1t shed light on some concerning aspects of Trae. Prior to the rollout of version 2.0.2, findings revealed that Trae was consuming 6.3 times the memory of the baseline VS Code while operating nearly four times as many processes. For perspective, VS Code typically runs 9 processes utilizing 0.9 GB of RAM. Cursor manages 11 processes at 1.9 GB, whereas Trae had a staggering 33 processes consuming approximately 5.7 GB of memory.

ByteDance’s Acknowledgment and Revisions

In response to these findings, ByteDance acknowledged the reported issues and released version 2.0.2, which included some performance improvements. Nevertheless, the updated version still operates with 13 processes while consuming around 2.5 GB of RAM, highlighting ongoing efficiency concerns.

Data Transmission and Privacy Issues

Another critical issue identified during testing was Trae’s tendency to establish persistent outbound connections to ByteDance servers. Even with telemetry features turned off, the IDE maintains these connections, leading to extensive data transmission. The analysis revealed that Trae made more than 500 server calls within just 7 minutes, sending approximately 26 MB of data.

Analysis of Data Sent Despite Telemetry Disabled

Even with telemetry disabled, the information transmitted by Trae includes:

  • System Information: Hardware specifications, operating system details, and architecture.
  • Usage Patterns: Insights into active time, session duration, and feature usage.
  • Performance Metrics: Data on response times and resource utilization.
  • Unique Identifiers: Machine ID, user ID, and device fingerprints.
  • Workspace Details: Project information and obfuscated file paths.

Community Reactions and Ongoing Debate

Concerns raised by segmentationf4u1t on Trae’s Discord server were met with significant backlash, leading to immediate sanctions like temporary mutes for discussing tracking-related topics. This environment of suppression has sparked a vigorous debate on platforms such as Hacker News, where opinions vary on the credibility of the analysis. As of now, ByteDance has not publicly addressed these allegations, leaving many to wonder about the implications for user privacy and software integrity.

Source & Images

Leave a Reply

Your email address will not be published. Required fields are marked *