Re: [Inkscape-devel] [Inkscape-user] Windows build crash?
I can confirm that with Win2k and latest build. Any switching to Selector tool from any other tool crashes, you don't even need to create a text. On XP it's ok, though.
Arnout, can you please download older builds and find out when this started?
On 10/12/06, Arnout Standaert <arnout.standaert@...1521...> wrote:
I'm experiencing a problem with the 0610072339 build, available from http://inkscape.modevia.com/win32/?M=D. I'm running it on a Windows 2000 system, but it also happens on a WinXP system at home.
Recipe:
- open Inkscape
- choose Text tool, click canvas, type text
- choose Arrow tool
Result: "Inkscape encountered an internal error and will close now. Automatic backups ..." and so on.
Could anyone please confirm this? I'm not sure if this is specific to my system or not... in any case, the 0610110200 build still shows the same problem.
Thanks a lot, Arnout
Yes, I can confirm it for 0609010403.7z at least. And I reported the same behaviour before that but people (including myself) were too busy to resolve it. I'll try and check up when I reported it first but it was months ago and I put a bug report in or at least confirmed an existing one. Erik
----- Original Message ----- From: "bulia byak" <buliabyak@...400...> To: "Inkscape User Community" inkscape-user@lists.sourceforge.net; "Inkscape Development Mailing List" inkscape-devel@lists.sourceforge.net Sent: Friday, October 13, 2006 11:09 AM Subject: Re: [Inkscape-devel] [Inkscape-user] Windows build crash?
I can confirm that with Win2k and latest build. Any switching to Selector tool from any other tool crashes, you don't even need to create a text. On XP it's ok, though.
Arnout, can you please download older builds and find out when this
started?
On 10/12/06, Arnout Standaert <arnout.standaert@...1521...>
wrote:
I'm experiencing a problem with the 0610072339 build, available from http://inkscape.modevia.com/win32/?M=D. I'm running it on a Windows
2000
system, but it also happens on a WinXP system at home.
Recipe:
- open Inkscape
- choose Text tool, click canvas, type text
- choose Arrow tool
Result: "Inkscape encountered an internal error and will close now. Automatic backups ..." and so on.
Could anyone please confirm this? I'm not sure if this is specific to my system or not... in any case, the 0610110200 build still shows the same problem.
Thanks a lot, Arnout
-- bulia byak Inkscape. Draw Freely. http://www.inkscape.org
Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job
easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&da... _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Bulia, a few things on this problem which I got on Win2k.
1. I believe this one goes back at least to build 0607281436.zip, because I was reporting this at the time. See my messages of around 30-31/7/06. I got error messages shown in my posts of this time. [Inkscape-devel] Windows Hassles HELP!. was " Updated PDF printingwith Cairo"
I tried to sort it out with Bob Jamison but had to let it go due to time pressures.
2. I gave up worrying about it when version 0.44.1-1.win32 came out. The problem is not there. This may be useful for Arnout to know.
3. I simply have not tried to get any nightly builds to work since then.
4. I have just confirmed that 0610072339.7z still shows this problem.
Erik
----- Original Message ----- From: "bulia byak" <buliabyak@...400...> To: "Inkscape User Community" inkscape-user@lists.sourceforge.net; "Inkscape Development Mailing List" inkscape-devel@lists.sourceforge.net Sent: Friday, October 13, 2006 11:09 AM Subject: Re: [Inkscape-devel] [Inkscape-user] Windows build crash?
I can confirm that with Win2k and latest build. Any switching to Selector tool from any other tool crashes, you don't even need to create a text. On XP it's ok, though.
Arnout, can you please download older builds and find out when this
started?
On 10/12/06, Arnout Standaert <arnout.standaert@...1521...>
wrote:
I'm experiencing a problem with the 0610072339 build, available from http://inkscape.modevia.com/win32/?M=D. I'm running it on a Windows
2000
system, but it also happens on a WinXP system at home.
Recipe:
- open Inkscape
- choose Text tool, click canvas, type text
- choose Arrow tool
Result: "Inkscape encountered an internal error and will close now. Automatic backups ..." and so on.
Could anyone please confirm this? I'm not sure if this is specific to my system or not... in any case, the 0610110200 build still shows the same problem.
Thanks a lot, Arnout
-- bulia byak Inkscape. Draw Freely. http://www.inkscape.org
That's a really bad bug. I'd like to request help from people who can build for windows: we need to test timed builds to figure out at what time this crept in. The web site only has a few recent builds, not very helpful. Anyone?
On 10/13/06, Erik Halbert <kaver@...68...> wrote:
Bulia, a few things on this problem which I got on Win2k.
- I believe this one goes back at least to build 0607281436.zip, because I
was reporting this at the time. See my messages of around 30-31/7/06. I got error messages shown in my posts of this time. [Inkscape-devel] Windows Hassles HELP!. was " Updated PDF printingwith Cairo"
I tried to sort it out with Bob Jamison but had to let it go due to time pressures.
- I gave up worrying about it when version 0.44.1-1.win32 came out. The
problem is not there. This may be useful for Arnout to know.
I simply have not tried to get any nightly builds to work since then.
I have just confirmed that 0610072339.7z still shows this problem.
Erik
----- Original Message ----- From: "bulia byak" <buliabyak@...400...> To: "Inkscape User Community" inkscape-user@lists.sourceforge.net; "Inkscape Development Mailing List" inkscape-devel@lists.sourceforge.net Sent: Friday, October 13, 2006 11:09 AM Subject: Re: [Inkscape-devel] [Inkscape-user] Windows build crash?
I can confirm that with Win2k and latest build. Any switching to Selector tool from any other tool crashes, you don't even need to create a text. On XP it's ok, though.
Arnout, can you please download older builds and find out when this
started?
On 10/12/06, Arnout Standaert <arnout.standaert@...1521...>
wrote:
I'm experiencing a problem with the 0610072339 build, available from http://inkscape.modevia.com/win32/?M=D. I'm running it on a Windows
2000
system, but it also happens on a WinXP system at home.
Recipe:
- open Inkscape
- choose Text tool, click canvas, type text
- choose Arrow tool
Result: "Inkscape encountered an internal error and will close now. Automatic backups ..." and so on.
Could anyone please confirm this? I'm not sure if this is specific to my system or not... in any case, the 0610110200 build still shows the same problem.
Thanks a lot, Arnout
-- bulia byak Inkscape. Draw Freely. http://www.inkscape.org
afraid i only have XP these days, so i cant reproduce it.
On 10/13/06, bulia byak <buliabyak@...400...> wrote:
That's a really bad bug. I'd like to request help from people who can build for windows: we need to test timed builds to figure out at what time this crept in. The web site only has a few recent builds, not very helpful. Anyone?
On 10/13/06, Erik Halbert <kaver@...68...> wrote:
Bulia, a few things on this problem which I got on Win2k.
- I believe this one goes back at least to build 0607281436.zip, because I
was reporting this at the time. See my messages of around 30-31/7/06. I got error messages shown in my posts of this time. [Inkscape-devel] Windows Hassles HELP!. was " Updated PDF printingwith Cairo"
I tried to sort it out with Bob Jamison but had to let it go due to time pressures.
- I gave up worrying about it when version 0.44.1-1.win32 came out. The
problem is not there. This may be useful for Arnout to know.
I simply have not tried to get any nightly builds to work since then.
I have just confirmed that 0610072339.7z still shows this problem.
Erik
----- Original Message ----- From: "bulia byak" <buliabyak@...400...> To: "Inkscape User Community" inkscape-user@lists.sourceforge.net; "Inkscape Development Mailing List" inkscape-devel@lists.sourceforge.net Sent: Friday, October 13, 2006 11:09 AM Subject: Re: [Inkscape-devel] [Inkscape-user] Windows build crash?
I can confirm that with Win2k and latest build. Any switching to Selector tool from any other tool crashes, you don't even need to create a text. On XP it's ok, though.
Arnout, can you please download older builds and find out when this
started?
On 10/12/06, Arnout Standaert <arnout.standaert@...1521...>
wrote:
I'm experiencing a problem with the 0610072339 build, available from http://inkscape.modevia.com/win32/?M=D. I'm running it on a Windows
2000
system, but it also happens on a WinXP system at home.
Recipe:
- open Inkscape
- choose Text tool, click canvas, type text
- choose Arrow tool
Result: "Inkscape encountered an internal error and will close now. Automatic backups ..." and so on.
Could anyone please confirm this? I'm not sure if this is specific to my system or not... in any case, the 0610110200 build still shows the same problem.
Thanks a lot, Arnout
-- bulia byak Inkscape. Draw Freely. http://www.inkscape.org
-- bulia byak Inkscape. Draw Freely. http://www.inkscape.org
Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&da... _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On Thu, 2006-10-12 at 21:09 -0400, bulia byak wrote:
I can confirm that with Win2k and latest build. Any switching to Selector tool from any other tool crashes, you don't even need to create a text. On XP it's ok, though.
I believe I filed a bug about this a while back actually -- it's not a Windows-specific problem; on Unix there are similar crashes with certain X servers (e.g. Xvnc).
To the best of my recollection, the problem appears to be some detail with inappropriate cleanup of the tool's cursor resource in src/event-context.cpp; possibly a GDK refcounting issue. Unfortunately I have not had time to investigate the relevant code in depth.
-mental
On 10/16/06, MenTaLguY <mental@...3...> wrote:
To the best of my recollection, the problem appears to be some detail with inappropriate cleanup of the tool's cursor resource in src/event-context.cpp; possibly a GDK refcounting issue. Unfortunately I have not had time to investigate the relevant code in depth.
So, do you think it likely that it was caused by
http://svn.sourceforge.net/viewvc/inkscape/inkscape/trunk/src/event-context....
and related changes? At least, it looks plausible time-wise, as this change was shortly after 0.44 and people report that 0.44 was ok and crashes started soon thereafter.
I will investigate if this is really the case. Scislac, please review the color cursors code for obvious errors. If this is indeed the culprit, and if you don't have a good idea of how to fix it, I'm afraid we will have to roll it back. As you remember, on the first attempt the color cursors also caused problems on win2k (white rects), and now these crashes... it's really not worth it to suffer all this trouble for what is basically superficial eye candy.
bulia byak wrote:
On 10/16/06, MenTaLguY <mental@...3...> wrote:
To the best of my recollection, the problem appears to be some detail with inappropriate cleanup of the tool's cursor resource in src/event-context.cpp; possibly a GDK refcounting issue. Unfortunately I have not had time to investigate the relevant code in depth.
So, do you think it likely that it was caused by
http://svn.sourceforge.net/viewvc/inkscape/inkscape/trunk/src/event-context....
and related changes? At least, it looks plausible time-wise, as this change was shortly after 0.44 and people report that 0.44 was ok and crashes started soon thereafter.
I will investigate if this is really the case. Scislac, please review the color cursors code for obvious errors. If this is indeed the culprit, and if you don't have a good idea of how to fix it, I'm afraid we will have to roll it back. As you remember, on the first attempt the color cursors also caused problems on win2k (white rects), and now these crashes... it's really not worth it to suffer all this trouble for what is basically superficial eye candy.
I will look into it. I do remember the win2k issues, and those got resolved... hopefully we can get this one resolved too. I definitely agree that it isn't worth it for something superficial.
-Josh
Josh wrote:
bulia byak wrote:
On 10/16/06, MenTaLguY <mental@...3...> wrote:
To the best of my recollection, the problem appears to be some detail with inappropriate cleanup of the tool's cursor resource in src/event-context.cpp; possibly a GDK refcounting issue. Unfortunately I have not had time to investigate the relevant code in depth.
So, do you think it likely that it was caused by
http://svn.sourceforge.net/viewvc/inkscape/inkscape/trunk/src/event-context....
and related changes? At least, it looks plausible time-wise, as this change was shortly after 0.44 and people report that 0.44 was ok and crashes started soon thereafter.
I will investigate if this is really the case. Scislac, please review the color cursors code for obvious errors. If this is indeed the culprit, and if you don't have a good idea of how to fix it, I'm afraid we will have to roll it back. As you remember, on the first attempt the color cursors also caused problems on win2k (white rects), and now these crashes... it's really not worth it to suffer all this trouble for what is basically superficial eye candy.
I will look into it. I do remember the win2k issues, and those got resolved... hopefully we can get this one resolved too. I definitely agree that it isn't worth it for something superficial.
-Josh
My reading of the above ( http://svn.sourceforge.net/viewvc/inkscape/inkscape/trunk/src/event-context.... suggests that you are looking at changes occurring between v11889 (may 21) and v12394 (jun 19). However, please note that the official version 0.44.1-1.win32 (sep 9), brought out three months later, DOES NOT have this problem. Why does that version work and nightly versions to date do not?
regards, Erik
On 10/16/06, Erik Halbert <kaver@...68...> wrote:
My reading of the above ( http://svn.sourceforge.net/viewvc/inkscape/inkscape/trunk/src/event-context.... suggests that you are looking at changes occurring between v11889 (may 21) and v12394 (jun 19). However, please note that the official version 0.44.1-1.win32 (sep 9), brought out three months later, DOES NOT have this problem. Why does that version work and nightly versions to date do not?
Because 0.44.1 was made from the 0.44 branch which was branched before this change was made to the trunk.
Anyway, Scislac: I just tested your build with this change reverted and it does not crash anymore on Windows 2000. So, unless you have an idea of what might be wrong-but-fixable in that code, let's revert it in the trunk (just commit after applying that patch that I sent you).
Special thanks to Mental for giving us a hint on what's going on :)
Lesson learned: Whenever you find out that SVN does not build or does not work on Windows, please ring the bell on the mailing list IMMEDIATELY. It is much easier to guess what might be wrong if the changes are fresh. In this case, I guess this was made worse by the cairo-pdf patch which made SVN uncompilable on Windows for months and nobody cared. Let's make sure this does not happen again.
bulia byak wrote:
On 10/16/06, Erik Halbert <kaver@...68...> wrote:
My reading of the above ( http://svn.sourceforge.net/viewvc/inkscape/inkscape/trunk/src/event-context.... suggests that you are looking at changes occurring between v11889 (may 21) and v12394 (jun 19). However, please note that the official version 0.44.1-1.win32 (sep 9), brought out three months later, DOES NOT have this problem. Why does that version work and nightly versions to date do not?
Because 0.44.1 was made from the 0.44 branch which was branched before this change was made to the trunk.
Anyway, Scislac: I just tested your build with this change reverted and it does not crash anymore on Windows 2000. So, unless you have an idea of what might be wrong-but-fixable in that code, let's revert it in the trunk (just commit after applying that patch that I sent you).
Committed. Unfortunately, on a single pass over the code I wasn't able to see anything that looked outright wrong-but-fixable. I figure people would appreciate my time being spent on adding more tutorials rather than fixing something superficial which gives no real benefit, so backing out that change was the way to go for now.
-Josh
Josh/Bulia wrote on 20/10/06
Anyway, Scislac: I just tested your build with this change reverted and it does not crash anymore on Windows 2000. So, unless you have an idea of what might be wrong-but-fixable in that code, let's revert it in the trunk (just commit after applying that patch that I sent you).
Committed. Unfortunately, on a single pass over the code I wasn't able to see anything that looked outright wrong-but-fixable. I figure people would appreciate my time being spent on adding more tutorials rather than fixing something superficial which gives no real benefit, so backing out that change was the way to go for now.
-Josh
I have just tested Build 0610211000.7z, (the most recent that I can find) which I had hoped would now work with Win2000. It does not. Inkscape still crashes and the same message as before comes up. This appears to be the same message that was reported at least as long ago as May 12. Can someone get a more recent build out for win users? and when should the fix mentioned above filter through? regards, Erik
On 10/25/06, Erik Halbert <kaver@...68...> wrote:
I have just tested Build 0610211000.7z, (the most recent that I can find) which I had hoped would now work with Win2000. It does not. Inkscape still crashes and the same message as before comes up.
Actually this thread discussed a different bug. What got fixed was the crash when switching to Selector. The "freeaddrinfo" problem is different and still needs fixing.
Speaking of which, does anyone have an idea of a workaround with the freeaddrinfo issue? Ishmal, you did the commit which broke this, so please don't drop the ball.
Erik Halbert wrote:
Josh/Bulia wrote on 20/10/06
Anyway, Scislac: I just tested your build with this change reverted and it does not crash anymore on Windows 2000. So, unless you have an idea of what might be wrong-but-fixable in that code, let's revert it in the trunk (just commit after applying that patch that I sent you).
Committed. Unfortunately, on a single pass over the code I wasn't able to see anything that looked outright wrong-but-fixable. I figure people would appreciate my time being spent on adding more tutorials rather than fixing something superficial which gives no real benefit, so backing out that change was the way to go for now.
-Josh
I have just tested Build 0610211000.7z, (the most recent that I can find) which I had hoped would now work with Win2000. It does not. Inkscape still crashes and the same message as before comes up. This appears to be the same message that was reported at least as long ago as May 12. Can someone get a more recent build out for win users? and when should the fix mentioned above filter through? regards, Erik
From that screenshot it looks like you are running Inkscape directly out
of the zip archive. If you are, you can't do that. Inkscape will be completely unable to locate the libraries it needs unless you extract the archive first.
Aaron Spike
Aaron wrote:
From that screenshot it looks like you are running Inkscape directly out
of the zip archive. If you are, you can't do that. Inkscape will be completely unable to locate the libraries it needs unless you extract the archive first.
Have a look at attached screen shot. That was taken in folder with extracted archive. regards, Erik
On Tue, 2006-10-17 at 09:56 +1000, Erik Halbert wrote:
My reading of the above ( http://svn.sourceforge.net/viewvc/inkscape/inkscape/trunk/src/event-context.... suggests that you are looking at changes occurring between v11889 (may 21) and v12394 (jun 19). However, please note that the official version 0.44.1-1.win32 (sep 9), brought out three months later, DOES NOT have this problem. Why does that version work and nightly versions to date do not?
Because 0.44.1 is based on 0.44(.0), NOT september 9th's trunk (which will eventually become an ancestor of 0.45).
-mental
participants (6)
-
Aaron Spike -
bulia byak -
Erik Halbert -
john cliff -
Joshua A. Andler -
MenTaLguY