Atom Causes Disk Corruption

[aidanharris]

Description

Atom causes my partition to corrupt when running resulting in my filesystem being mounted read-only and occurs both running normally and when starting in safe mode (atom --safe).

The problem appears to be with an unknown file (or files) in .atom/storage, deleting anything in this folder with rm -rf ~/.atom/storage/* and starting atom (after first repairing the damage to the partition with fsck) appears to fix the issue.

After further testing the problem also occurs even if I completely delete the .atom folder and let Atom recreate a new one.

Output from dmesg confirming the corruption can be found below:

[   54.443923] EXT4-fs error (device sda4): ext4_ext_check_inode:495: inode #128152: comm atom: pblk 0 bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)
[   54.444001] Aborting journal on device sda4-8.
[   54.444047] EXT4-fs (sda4): Remounting filesystem read-only
[   55.344797] EXT4-fs error (device sda4): ext4_ext_check_inode:495: inode #361065: comm atom: pblk 0 bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)
[   67.915158] atom[3688]: segfault at 208 ip 0000000000b277b4 sp 00007ffd02bba3a0 error 4 in atom[400000+a86000]

System Info

Device: 15" MacBook Pro Retina Display - Late 2013
OS: Ubuntu GNOME 15.04 64bit
Kernel: Linux 3.19.0-25-generic
DE: GNOME Shell 3.16.3

Does anyone have any ideas how I can debug this further to find out exactly why this is occurring?

[lock]

This issue has been automatically locked since there has not been any recent activity after it was closed. If you can still reproduce this issue in Safe Mode then please open a new issue and fill out the entire issue template to ensure that we have enough information to address your issue. Thanks!