[win32] really long initial startup times on Windows 7/8
This one almost certainly has to be fixed before we release.
To be quite honest, I am unsure of the cause. I did test this out on Windows XP and it worked perfectly well. I compiled on a Windows 8.1 x64 machine, and launched it on a Windows 7 machine. The console window appeared, as normal, but I wondered why it didn't go away. Interested, I launched it with not gdb, as would be recommended, but instead with Visual Studio (as it would have symbols for all of the Windows libraries). The long startup didn't cause any sort of trap, but the preferences.xml I had did. (the trap seems to happen when you launch with default prefs, iconify the Fill and Stroke dialog, close it normally, and restart it with gdb: https://bugs.launchpad.net/inkscape/+bug/1317700)
After I had stepped through every single one of the several hundred breakpoints, I could not find the issue (although mainly because the Microsoft devs refuse on releasing the details to their PDB format, and do not seem to support DWARF debug symbols in their debuggers).
I am unable to reproduce the exceptionally long startup time issue, as it went away immediately after the first startup. Possibly a registry key was set. However, the traps are a persistent issue and make my loading time about five seconds longer.
What I am envisioning right now is thousands of people downloading the update, launching Inkscape, and not seeing anything at all (compiled with -mwindows), despite the process showing in Task Manager and consuming many resources. We have also had at least one complaint about this before. (If I could put a bounty on this bug, I would!)
What is this madness?
Liam,
I see the same thing on my Mac OSX build.
Thanks, Partha
On Tue, May 13, 2014 at 5:11 PM, Liam White <inkscapebrony@...400...> wrote:
This one almost certainly has to be fixed before we release.
To be quite honest, I am unsure of the cause. I did test this out on Windows XP and it worked perfectly well. I compiled on a Windows 8.1 x64 machine, and launched it on a Windows 7 machine. The console window appeared, as normal, but I wondered why it didn't go away. Interested, I launched it with not gdb, as would be recommended, but instead with Visual Studio (as it would have symbols for all of the Windows libraries). The long startup didn't cause any sort of trap, but the preferences.xml I had did. (the trap seems to happen when you launch with default prefs, iconify the Fill and Stroke dialog, close it normally, and restart it with gdb: https://bugs.launchpad.net/inkscape/+bug/1317700)
After I had stepped through every single one of the several hundred breakpoints, I could not find the issue (although mainly because the Microsoft devs refuse on releasing the details to their PDB format, and do not seem to support DWARF debug symbols in their debuggers).
I am unable to reproduce the exceptionally long startup time issue, as it went away immediately after the first startup. Possibly a registry key was set. However, the traps are a persistent issue and make my loading time about five seconds longer.
What I am envisioning right now is thousands of people downloading the update, launching Inkscape, and not seeing anything at all (compiled with -mwindows), despite the process showing in Task Manager and consuming many resources. We have also had at least one complaint about this before. (If I could put a bounty on this bug, I would!)
What is this madness?
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Actually I was going to report the same thing for Windows XP SP 3.
In the (ugly) console I always see a starting: Unable to find: DialogGridArrange ** (inkscape.exe:2524): WARNING **: Unknown verb name: DialogGridArrange followed by a lot of: (inkscape.exe:2524): Pango-WARNING **: couldn't load font "<...>", falling back to "Sans 10", expect ugly output. which take a lot of time to scroll away one by one, but the biggest delay seems to happen before anything is written out.
Also, recently (last week) I'm experiencing a lot of crashes, usually while ungrouping objects: the document gets emergency-saved correctly but without the objects I was ungrouping which are completely lost. Today I've got a PDF file that when imported refuses to be zoomed in: at some point black bars appear and everything blows up. One of the many times I tried to open it, it took a huge amount of time to load and after that a "low system memory" dialog appeared then it got opened (and crashed after zooming as all other times). These may be unrelated issues but I started experiencing them almost in the same period as the big(ger) startup delay.
It looks like during the startup there is some heavy memory operation taking place. I suspect that something is not being allocated or released correctly so after the file is loaded you may happen to do some operation on that data triggering the crash. This is just an impression, anyway: I've not tried with gdb because on my Pentium IV it takes ages to start up and after that it's almost unusable for the unmanageable delays in the interface.
-- View this message in context: http://inkscape.13.x6.nabble.com/win32-really-long-initial-startup-times-on-... Sent from the Inkscape - Dev mailing list archive at Nabble.com.
LucaDC wrote
Actually I was going to report the same thing for Windows XP SP 3.
In the (ugly) console I always see a starting: Unable to find: DialogGridArrange ** (inkscape.exe:2524): WARNING **: Unknown verb name: DialogGridArrange
You need to delete %appdata%\inkscape\preferences.xml (or rename it) and restart it, and it should be more stable then.
-- View this message in context: http://inkscape.13.x6.nabble.com/win32-really-long-initial-startup-times-on-... Sent from the Inkscape - Dev mailing list archive at Nabble.com.
On 2014-05-14 15:56 +0100, liamw wrote:
LucaDC wrote
Actually I was going to report the same thing for Windows XP SP 3.
In the (ugly) console I always see a starting: Unable to find: DialogGridArrange ** (inkscape.exe:2524): WARNING **: Unknown verb name: DialogGridArrange
You need to delete %appdata%\inkscape\preferences.xml (or rename it) and restart it, and it should be more stable then.
The specific message ("Unknown verb name: DialogGridArrange") indicates that the keymap file which is loaded by the current inkscape trunk build is outdated and refers to a verb which was renamed to 'DialogArrange' in revision 13221.
On linux/OS X, the specific message normally stops after having run 'make install' once again to update the installed shared resource files. Or after checking the user keymap file in the preferences folder for outdated verbs ... (~/.config/inkscape/keys/default.xml)
Thank you for the hint and explanations. I don't want neither to delete my preferences nor my default file because they contain my settings which I don't want to lose. I'll do a compare with fresh ones and try to fix it by hand. Maybe I'll ask you some help if I can't figure out exactly what to touch.
-- View this message in context: http://inkscape.13.x6.nabble.com/win32-really-long-initial-startup-times-on-... Sent from the Inkscape - Dev mailing list archive at Nabble.com.
Thank you su_v for pointing me in the right direction: the problem was in my shortcuts file which is not 'default.xml' and so, of course, is not updated with trunk hence retained the old verb.
-- View this message in context: http://inkscape.13.x6.nabble.com/win32-really-long-initial-startup-times-on-... Sent from the Inkscape - Dev mailing list archive at Nabble.com.
participants (5)
-
Liam White -
liamw -
LucaDC -
Partha Bagchi -
su_v