#1784 JEdit freezes when css3Sidekick error

None
closed-fixed
Dale Anson
5
2014-04-30
2014-04-26
Jojaba
No

To reproduce the issue :
1) Edit the style-jedit-issue.css attached file
2) Try to type something in this file
3) Cursor deasappears cpu usage grows.
4) No error message (in the right bottom corner), error in log file (see txt attachment) before freezing
5) After a while cursor apperas again

@media Error detected by sidekick shouldn't be errors (see screenshot in attachment), I don't know if this is the cause of the issue.

jEdit version : 5.1.0
Sidekick version : 1.6
XML version : 2.8.7

3 Attachments

Discussion

1 2 > >> (Page 1 of 2)
  • Dale Anson
    Dale Anson
    2014-04-26

    • assigned_to: Dale Anson
    • Group: -->
     
  • Dale Anson
    Dale Anson
    2014-04-28

    • status: open --> closed-works-for-me
     
  • Dale Anson
    Dale Anson
    2014-04-28

    I am unable to reproduce this freezing issue. However, I did go ahead and update the CSS parser so that it properly handles the CSS 3 media queries. Previously, it was only handling CSS 2.1 media queries.

     
  • Dale Anson
    Dale Anson
    2014-04-28

    Please feel free to reopen if you can find better steps to help me reproduce the freezing problem.

     
  • Jojaba
    Jojaba
    2014-04-29

    Thanks Dale!
    I try again to reproduce the issue, following the steps I wrote in my previous message. The cursor disappears after typing 2 or 3 characters, then comes again up after a while. I removed the lines concerning @media, the issue is still coming up. Maybe a conflict with another plugin...
    I attachment a list of the installed plugins...
    I will try to deactivate each plugin one by one to see if I can find something...

     
    Attachments
  • Dale Anson
    Dale Anson
    2014-04-29

    Do you happen to have some javascript files open? If so, would you check in the Plugin Options for Sidekick, what parser do you have selected for javascript? The ecmascript parser has a known problem with some javascript files that causes the symptoms you're describing, and the ecmascript parser is part of the XML plugin. Maybe try switching to the javascript parser and see if that helps.

     
    • Jojaba
      Jojaba
      2014-04-29

      I closed all files and opened only the css file. Still have the issue...
      As I said earlier, I tried to desactivate several plugins. First I desactivate almost all plugins, and kept just XML, sidekick, errorlist. Still had the issue. But when I desactivated the XML plugin, no issue anymore. I reanabled all my plugins except XML Plugin, no issue. I disabled all plugins and activated just xml plugin (with te dependencies common controls, Eclips icons, Error List, Sidekick, Xerces), no issue !!! So it must be a conflict problem. Now I try to reanable each plugin one by one to see witch one is conflcting....

       
  • Dale Anson
    Dale Anson
    2014-04-29

    • status: closed-works-for-me --> open
     
  • Dale Anson
    Dale Anson
    2014-04-29

    Re-opening since this is still under discussion.

     
  • Jojaba
    Jojaba
    2014-04-29

    Correction: when enabling only xml plugin, still get the issue when telling sidekick to parse with css parser (was set to none, when I reactivated xml plugin in my test before).
    I think it is the css parser that cause the issue. How can I test if this is the case?

     
1 2 > >> (Page 1 of 2)