Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A java script error occurred in the main process #882

Closed
sandyUni opened this issue Sep 4, 2017 · 9 comments
Closed

A java script error occurred in the main process #882

sandyUni opened this issue Sep 4, 2017 · 9 comments

Comments

@sandyUni
Copy link

sandyUni commented Sep 4, 2017

image

I can't provide the file which occurs this fault, cause it is corrupt by this app.

system: windows 10 64bit.
typora version: 0.9.36 beta

@sandyUni
Copy link
Author

sandyUni commented Sep 4, 2017

BTW, I suggest you the provider add some disclaimer in your application, to inform user that this app may corrupt thier precious data.

@abnerlee
Copy link
Contributor

abnerlee commented Sep 4, 2017

Only open that file will trigger this bug, or will open other files, create new file trigger this bug?

Does Typora has access permit on C:\Users{your user}\AppDate\Roaming\Typora ?

And how to reproduce this bug, what did you do before this dialog show up?

And could you send typora.log in C:\Users{your user}\AppDate\Roaming\Typora to us ([email protected]) ?

@abnerlee
Copy link
Contributor

abnerlee commented Sep 4, 2017

relates typicode/lowdb#157

@abnerlee
Copy link
Contributor

abnerlee commented Sep 4, 2017

I can't provide the file which occurs this fault, cause it is corrupt by this app.
please check http://support.typora.io/Version-Control/

By "corrupt", you mean your markdown file is empty now?

@sandyUni
Copy link
Author

sandyUni commented Sep 4, 2017

Only open that file will trigger this bug, or will open other files, create new file trigger this bug?

This error just appears twice, both of which are at opening this file. However, after that, this error just disappears whichever file is opened. So I can't determine whether it is that file causes this error.

Does Typora has access permit on C:\Users{your user}\AppDate\Roaming\Typora ?

I am not sure. it works just fine after appearing error twice.

And how to reproduce this bug, what did you do before this dialog show up?

I am not sure. I can't reproduce this bug.

And could you send typora.log in C:\Users{your user}\AppDate\Roaming\Typora to us ([email protected]) ?

I have sent my log file via [email protected]

By "corrupt", you mean your markdown file is empty now?

Yes.

hope to be helpful

@abnerlee
Copy link
Contributor

abnerlee commented Sep 4, 2017

@lj8385174 I see, thanks for your time.

And this may help -> http://support.typora.io/Version-Control/

@sandyUni
Copy link
Author

sandyUni commented Sep 5, 2017

That really helps a lot, thx.

@abnerlee
Copy link
Contributor

relates typicode/lowdb#157

@vladimiry
Copy link

I just pointed to a probable cause of the error here typicode/lowdb#157 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants