You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I cannot say that the problem appeared after update Atom.jl...
Just started crashing at the rush time when I needed to produce some plots for the upcoming meeting :(
julia> ┌ Error: Error in the keymap
│ exception =
│ InterruptException:
│ Stacktrace:
│ [1] iolock_end at .\libuv.jl:49 [inlined]
│ [2] displaysize(::Base.TTY) at .\stream.jl:481
│ [3] displaysize(::REPL.Terminals.TTYTerminal) at D:\buildbot\worker\package_win64\build\usr\share\julia\stdlib\v1.3\REPL\src\Terminals.jl:153
│ [4] width(::REPL.Terminals.TTYTerminal) at D:\buildbot\worker\package_win64\build\usr\share\julia\stdlib\v1.3\REPL\src\Terminals.jl:79
│ [5] edit_insert(::REPL.LineEdit.PromptState, ::Any) at D:\buildbot\worker\package_win64\build\usr\share\julia\stdlib\v1.3\REPL\src\LineEdit.jl:715
│ [6] edit_insert(::REPL.LineEdit.MIState, ::Any) at D:\buildbot\worker\package_win64\build\usr\share\julia\stdlib\v1.3\REPL\src\LineEdit.jl:215
│ [7] (::REPL.LineEdit.var"#131#183")(::Any, ::Any, ::Any) at D:\buildbot\worker\package_win64\build\usr\share\julia\stdlib\v1.3\REPL\src\LineEdit.jl:2087
│ [8] #invokelatest#1 at .\essentials.jl:709 [inlined]
│ [9] invokelatest at .\essentials.jl:708 [inlined]
│ [10] (::REPL.LineEdit.var"#27#28"{REPL.LineEdit.var"#131#183",String})(::Any, ::Any) at D:\buildbot\worker\package_win64\build\usr\share\julia\stdlib\v1.3\REPL\src\LineEdit.jl:1356
│ [11] prompt!(::REPL.Terminals.TextTerminal, ::REPL.LineEdit.ModalInterface, ::REPL.LineEdit.MIState) at D:\buildbot\worker\package_win64\build\usr\share\julia\stdlib\v1.3\REPL\src\LineEdit.jl:2398
│ [12] run_interface(::REPL.Terminals.TextTerminal, ::REPL.LineEdit.ModalInterface, ::REPL.LineEdit.MIState) at D:\buildbot\worker\package_win64\build\usr\share\julia\stdlib\v1.3\REPL\src\LineEdit.jl:2301
│ [13] run_frontend(::REPL.LineEditREPL, ::REPL.REPLBackendRef) at D:\buildbot\worker\package_win64\build\usr\share\julia\stdlib\v1.3\REPL\src\REPL.jl:1045
│ [14] run_repl(::REPL.AbstractREPL, ::Any) at D:\buildbot\worker\package_win64\build\usr\share\julia\stdlib\v1.3\REPL\src\REPL.jl:201
│ [15] (::Base.var"#770#772"{Bool,Bool,Bool,Bool})(::Module) at .\client.jl:382
│ [16] #invokelatest#1 at .\essentials.jl:709 [inlined]
│ [17] invokelatest at .\essentials.jl:708 [inlined]
│ [18] run_main_repl(::Bool, ::Bool, ::Bool, ::Bool, ::Bool) at .\client.jl:366
│ [19] exec_options(::Base.JLOptions) at .\client.jl:304
The text was updated successfully, but these errors were encountered:
mmikhasenko
changed the title
[BUG?] julia session crashes after execution of a few commends
[BUG?] julia session crashes after the execution of a few commands
Mar 13, 2020
I have a feeling that it is some allergic reaction to Plots.jl, because it is always included
together with a few other modules
using LhcbUIIvelo # my module#using LaTeXStrings
using DelimitedFiles
#using DataFrames
using Query
#using Statistics
using Parameters
using Plots
using StatsPlots
Also:
the error does not happen if I run the same scripts in the terminal
# example 1using Plots, LaTeXStrings
histogram(rand(10), lab=L"\sigma") # workshistogram(rand(10), lab=L"\sigma\sigma") # works# now, with incorrect latex expressoion histogram(rand(10), lab=L"\sss") # InterruptException, julia crash## example 2using Plots, LaTeXStrings
# now, with incorrect latex expressoion histogram(rand(10), lab=L"\sss") # works, without label, and with the warning, latex: failed to create a dvi file# again, different incorrect latex expressoion histogram(rand(10), lab=L"\ssss") # ERROR: InterruptException: julia crashes
It fails with atom interactive session when evaluated line by line.
Julia crashed on the second try of producing a plot with incorrect latex expression.
I cannot say that the problem appeared after update
Atom.jl
...Just started crashing at the rush time when I needed to produce some plots for the upcoming meeting :(
I have tried:
Any ideas what could be the problem? Coronavirus?
The debug info follows:
The text was updated successfully, but these errors were encountered: