Menu
▾
▴
[ jEdit-devel ] [ jedit-Plugin Bugs-3033210 ] Sidekick parsing issues
|
From: SourceForge.net <no...@so...> - 2010-10-07 01:07:05
|
Plugin Bugs item #3033210, was opened at 2010-07-22 13:47 Message generated for change (Comment added) made by daleanson You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=565475&aid=3033210&group_id=588 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Damien (kog13) Assigned to: Nobody/Anonymous (nobody) Summary: Sidekick parsing issues Initial Comment: Every now and then (rather frequently), Sidekick's ability to parse simply breaks. It will either parse continuously regardless of buffer or parser change (resulting in a continuous stream of messages in the activity log), or simply refuse to parse a new buffer, again ignoring both buffer and parser changes. The only way I've found to restore sidekick when this happens is to reload it or restart jEdit. This has happened on both java and xml files. ---------------------------------------------------------------------- >Comment By: Dale Anson (daleanson) Date: 2010-10-06 19:07 Message: Fixed by patch in tracker 3081956. ---------------------------------------------------------------------- Comment By: Damien (kog13) Date: 2010-10-06 15:36 Message: Yeah, I think it was the problem. Feel free to close this. ---------------------------------------------------------------------- Comment By: Dale Anson (daleanson) Date: 2010-10-06 14:41 Message: Damien, do you think your patch for tracker 3081956 fixes this? If so, I've applied that patch, so this one could be closed. ---------------------------------------------------------------------- Comment By: Damien (kog13) Date: 2010-07-23 09:16 Message: When it's constantly parsing, the activity log is just a continuous flow of "setting parsed data" debug messages and similar; I don't remember seeing any error messages, but if I can locate one, I'll post it. For the second problem of simply not resetting, nothing is added to the activity log as a result of switching buffers, parsers, and re-parsing. I'll look into the "exception thrown in edit bus handler" possibility. I know there have been some problems with JavaSideKick's edit bus handler regarding ProjectViewer (circularity errors), but I don't know if that would affect sidekick at all. I'll work on trying to reproduce it reliably and locating any useful information from the activity log. ---------------------------------------------------------------------- Comment By: Shlomy Reinstein (shlomy) Date: 2010-07-22 13:53 Message: Please attach your activity.log file when this happens. Do you occasionally minimize / close SideKick and then show it again, or does it always remain visible (so you always see the tree)? As far as I remember, sometimes a plugin (not necessarily SideKick) throws an exception while handling an edit bus message. Doing that, the edit bus message is aborted, and other plugins don't get it any more. So if any plugin throws an exception in the edit bus handler, it may cause other plugins and core parts to stop functioning correctly. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=565475&aid=3033210&group_id=588 |