8000 Loading large file with many lines sometimes hangs or crashes the editor · Issue #8864 · atom/atom · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
This repository was archived by the owner on Mar 3, 2023. It is now read-only.

Loading large file with many lines sometimes hangs or crashes the editor #8864

Closed
ohcrfpv opened this issue Sep 19, 2015 · 34 comments
Closed

Comments

@ohcrfpv
Copy link
ohcrfpv commented Sep 19, 2015

File that has 140000 lines can reproduce this issue.
Sublime Text 3 release version has no this problem.

@OmgImAlexis
Copy link

Duplicate #979

@winstliu
Copy link
Contributor

Thanks @OmgImAlexis.

@mnquintana
Copy link
Contributor

I'm actually not sure if this is a dupe of #979 – @fewspider mentions that this happens with a file with 140,000 lines, rather than a single really long line.

@fewspider Can you reproduce this by completely quitting Atom and restarting it in in safe mode? (atom --safe)

@ohcrfpv
Copy link
Author
ohcrfpv commented Sep 22, 2015

@mnquintana My atom version is 1.0.15, atom --safe is OK👌. My file is a sql file, the syntax highlighting is not working,when atom or atom --safe. Just a guess, the syntax highlighting problem happens in large file.

@centic9
Copy link
centic9 commented Oct 5, 2015

Sounds like being related to syntax highlighting and thus sounds like a duplicate of #6642

@mnquintana mnquintana changed the title load large file sometimes unresponsive Loading large file with many lines sometimes unresponsive Jan 19, 2016
@mnquintana mnquintana added the bug label Jun 29, 2016
@mnquintana mnquintana changed the title Loading large file with many lines sometimes unresponsive Loading large file with many lines sometimes hangs or crashes the editor Jun 29, 2016
@Ben3eeE
Copy link
Contributor
Ben3eeE commented Oct 13, 2016

@Undistraction I don't consider 2800 lines to be many. How big is the file? Are the lines very long?

@Undistraction
Copy link

@Ben3eeE Not long at all. File is an array of objects like this one:

{
    "name": "Aquatic warbler",
    "latinName": "Acrocephalus paludicola",
    "imageUrl": "https://www.example.com/example.jpg?width=800&crop=(0,188,900,694)",
    "imagePath": "./data/saved_images/jpg/example.jpg",
    "analysis": [
      {
        "ratio": 0.208655332302937,
        "cmyk": [
          "0",
          "10",
          "31",
          "28"
        ]
      },
      {
        "ratio": 0.198454404945904,
        "cmyk": [
          "0",
          "4",
          "14",
          "48"
        ]
      },
      {
        "ratio": 0.182586295723854,
        "cmyk": [
          "0",
          "2",
          "12",
          "30"
        ]
      },
      {
        "ratio": 0.165172591447707,
        "cmyk": [
          "0",
          "7",
          "28",
          "12"
        ]
      },
      {
        "ratio": 0.133333333333333,
        "cmyk": [
          "0",
          "3",
          "8",
          "67"
        ]
      },
      {
        "ratio": 0.111798042246265,
        "cmyk": [
          "0",
          "0",
          "2",
          "7"
        ]
      }
    ]
  },

@Ben3eeE
Copy link
Contributor
Ben3eeE commented Oct 13, 2016

@Undistraction I suggest you check if you can reproduce this issue in safe mode atom --safe. If you can reproduce it in safe mode file a new issue here and completely fill out the provided issue template. It would be great if you could also upload a copy of the file. If you don't want to upload it public you can send it in an email to atom@github.com with a link to the issue.

If you are unable to reproduce it in safe mode that indicates a problem with one of your installed community packages. In that case you can try disabling packages until the problem disappears and file an issue on that repository.

This issue is for files that are very large (several megabytes) or have many lines (>100000) and your file sounds like none of those.

@superjoefly
Copy link

Laravel app.js file crashing Atom. This is a large .js file... I tried safe mode, but got the same result. File opens fine in other text editors. This is the output from the terminal after using
atom --safe:
/usr/bin/atom: line 130: 23586 Segmentation fault (core dumped) nohup "$ATOM_PATH" --executed-from="$(pwd)" --pid=$$ "$@" > "$ATOM_HOME/nohup.out" 2>&1
Failed to get crash dump id.
Report Id:

atom --v:
Atom : 1.14.2
Electron: 1.3.13
Chrome : 52.0.2743.82
Node : 6.5.0

I'm running Ubuntu 16.04 LTS

@rsese
Copy link
Contributor
rsese commented Feb 27, 2017

Laravel app.js file crashing Atom. This is a large .js file.

Is this a minified file @superjoefly? If so, I think this is a duplicate of #979.

@superjoefly
Copy link

@rsese Yes...it's minified. I see the issue has been around for a while. It seems that it may be fixed in Atom 1.15.0-beta3. I guess I'll give it a try :-) Thank you for the reference :-)

@chriszrc
Copy link

I'm on 1.15.0-beta3 and I still can't open a 35MB json file :'(

@superjoefly
Copy link
superjoefly commented Mar 1, 2017

I can confirm that I was able to open the Laravel app.js file in Atom 1.15.0-beta3 with no problem. Thank you Team Atom! :-)

@chriszrc Are you sure you used Atom 1.15.0-beta3? It runs along side of your previous version of Atom, so make sure you chose the right one. I hope this helps :-)

@gusbemacbe
Copy link

Hey people! Larger files don't work on Atom, both stable and beta and can't be syntax-highlighted. Only smaller and separated files work on Atom.

Firstly work with smaller and separated files on Atom, and when you want to unify all small and separated files into one and to load larger files, with syntax highlighting, use Sublime Text.

@wogandavid
Copy link

I build economic models and the listing files that GAMS produces can be quite large >25MB. It would be convenient to open these in Atom, since I do some GAMS development in Atom (and the text editor in GAMS is rather basic).

@oli
8000
vermt
Copy link
olivermt commented Mar 7, 2017

I am getting hangs on a file with 5000 lines, problem still persisting in newest beta.

Starting with --safe does absolutely nothing.

I dont care if I dont get syntax hilight etc. The problem is that if you have opened that file once, re-opening atom in that folder will keep your atom editor locked forever.

Solution is to kill all atom data and reinstall.

@olivermt
Copy link
olivermt commented Mar 7, 2017

Actually, in newest beta, deleting the file kills the deadlock.. so there's that!

@Ben3eeE
Copy link
Contributor
Ben3eeE commented Mar 7, 2017

@olivermt Are you on Windows with spell-check enabled? We have an open issue for spell-check causing performance issues on Windows atom/spell-check#190

@olivermt
Copy link
olivermt commented Mar 7, 2017

@Ben3eeE indeed that test locks up my editor!

Shouldnt atom --safe have disabled that though?

@Ben3eeE
Copy link
Contributor < 8000 /div>
Ben3eeE commented Mar 7, 2017

@olivermt atom --safe only disables community packages. spell-check is a core package that is bundled with Atom.

@olivermt
Copy link
olivermt commented Mar 7, 2017

Wish I knew about that bug before spending 2-3 hours disabling all kinds of weird stuff, reinstalling, tracing here and there blablabla :)

Anyways, that fixes the issue completely for me. Greatly appreciated @Ben3eeE 🥇

@pke
Copy link
pke commented Mar 24, 2017

Disabling spell-check does not improve at all on JSON load performance. Where in Sublime (2 or 3 doesnt matter) the file opens instantly, atom displays a "Wait for atom" message after loading the file some seconds and then taking another many seconds to finally load the file. 2.7MB one line file.

@winstliu
Copy link
Contributor

@pke there are many different reasons for slow performance - there is not a single "catch-all" silver bullet for these types of issues. In your case, please make sure you are running at least Atom 1.15.0, which contains many performance improvements for large files.

@lock
Copy link
lock bot commented Apr 2, 2018

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!

@lock lock bot locked and limited conversation to collaborators Apr 2, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

0