Re: [Github-comments] [geany/geany-plugins] [markdown] Long init times on Win10 (#519)

2021-04-16 Thread Royi
@elextr , I'm sorry. I was under the impression I'm under the [Discussions forum of Geany](https://github.com/geany/geany/discussions). I guess I wrote in the wrong path. P. S. I can't find any binaries on the site only a recipe for Chocolatey. -- You are receiving this because you are

Re: [Github-comments] [geany/geany-plugins] [markdown] Long init times on Win10 (#519)

2021-04-16 Thread elextr
@RoyiAvital it is extremely rude to ask irrelevant questions on but issues, like interrupting a conversation. Look on the Geany website. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub:

Re: [Github-comments] [geany/geany-plugins] [markdown] Long init times on Win10 (#519)

2021-04-16 Thread Royi
Is there a direct download link to Windows binaries of Geany? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany-plugins/issues/519#issuecomment-821076947

Re: [Github-comments] [geany/geany-plugins] [markdown] Long init times on Win10 (#519)

2018-10-04 Thread VictorelPetrovich
Windows 7, geany 1.33 : activating markdown for Ist time caused Geany to be "Not responding" (freeze). Had to wait > 1 minute till it finished it's job (almost thought it's useless and a bug). But after that, (re) activating markdown does not cause any freezes. -- You are receiving this

Re: [Github-comments] [geany/geany-plugins] [markdown] Long init times on Win10 (#519)

2017-07-18 Thread CeruleanSky
I upgraded yesterday and took that opportunity to track down which plugin it was. I tested it with 1.30 and 1.31 before I went to sleep. I searched for the issue today and saw another person had an issue with markdown, tried to reproduce the stall, but today it was working fine. I'll add a

Re: [Github-comments] [geany/geany-plugins] [markdown] Long init times on Win10 (#519)

2017-07-18 Thread Enrico Tröger
Are you sure you experienced the slowiness on 1.31 ever? For me, the 1.31 binaries started quite quickly, much faster than before. Though I didn't test and debug this issue in particular. Anyway, this is(or has been) most probably a problem in one of the bundled libraries and not in our control.

Re: [Github-comments] [geany/geany-plugins] [markdown] Long init times on Win10 (#519)

2017-07-18 Thread CeruleanSky
Markdown was causing issues identical to what was mentioned above for me. I used ProcessHacker to look at the thread and frame stack causing the delay. I noticed that when the problem occurs the program is also iterating through the fonts in the system very very slow locking up geany for

Re: [Github-comments] [geany/geany-plugins] [markdown] Long init times on Win10 (#519)

2017-03-01 Thread Enrico Tröger
I could not find any reference to included debugging symbols or anything like that. But with just built up2date Windows binaries, startup with Webkit plugins enabled feels a bit faster. If anyone is curious to try: http://lists.geany.org/devel/2017-March/010203.html -- You are receiving this

Re: [Github-comments] [geany/geany-plugins] [markdown] Long init times on Win10 (#519)

2017-01-25 Thread gigadude
My very brief experiment was that loading/unloading was fast after the first time. Restarting Geany went back to slow. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub:

Re: [Github-comments] [geany/geany-plugins] [markdown] Long init times on Win10 (#519)

2017-01-25 Thread Matthew Brush
> But never debugged it, just assuming it is related that loading all the > rather huge WebKitGTK libraries (and dependencies like libicu) just needs > some time. If this is the case, I would expect it to only be slow loading the first webkit-using plugin. What happens if you disable all

Re: [Github-comments] [geany/geany-plugins] [markdown] Long init times on Win10 (#519)

2017-01-25 Thread gigadude
I've tried to repro a bunch of times on 1.28, haven't hit it. It happens 100% of the time on 1.29 (with the caveat that that's on a different machine). I'll try upgrading the 1.28 machine. FWIW I only started noticing this when I upgraded my work machine to 1.29. -- You are receiving this

Re: [Github-comments] [geany/geany-plugins] [markdown] Long init times on Win10 (#519)

2017-01-25 Thread Enrico Tröger
FTR: this is not specific to the Markdown plugin but rather for all plugins which use WebKitGTK on Windows. The same loading delay can be observed with the DevHelp plugin. And it happens when the plugin is autoloaded at Geany startup as well as when the plugin is loaded initially in the Plugin

Re: [Github-comments] [geany/geany-plugins] [markdown] Long init times on Win10 (#519)

2017-01-24 Thread Matthew Brush
Does it take ~10 seconds if you start Geany without the plugin loaded and then using the Plugin Manager dialog enable it? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub:

Re: [Github-comments] [geany/geany-plugins] [markdown] Long init times on Win10 (#519)

2017-01-24 Thread gigadude
After startup too, but only the first time (and apparently only for 1.29, 1.28 seems to be fine) -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany-plugins/issues/519#issuecomment-275002643

Re: [Github-comments] [geany/geany-plugins] [markdown] Long init times on Win10 (#519)

2017-01-24 Thread Matthew Brush
Is only only when Geany starts, or also when the plugin is enabled after startup too? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany-plugins/issues/519#issuecomment-274991505

[Github-comments] [geany/geany-plugins] [markdown] Long init times on Win10 (#519)

2017-01-24 Thread gigadude
Markdown freezes geany for about 10s on my Win10 system when starting up. I've verified that disabling/enabling markdown is what's causing the delay. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: