| 2015-07-30 13:25:43 |
Carson Wilson |
bug |
|
|
added bug |
| 2015-07-30 13:27:27 |
Carson Wilson |
description |
If started Inkscape maximized without an initial file, it runs erratically, and quietly dies if I move my mouse to the right or top of the screen.
If and only if started with no initial file and Default Window Size set to "Maximized," both the 32 and 64 bit versions of Inkscape 0.91 exhibit this issue.
Under Windows 7 64 bit, both the 32 and the 64 bit releases of Inkscape 0.91 exhibit this issue with my 1440 x 2560 resolution screen. My screen is oriented vertically, so 1440 is horizontal and 2560 is vertical resolution.
I strongly suspect this is related to screen resolution, because both versions start OK if I configure their window size to "Large" instead of "Maximized" (preference setting Interface->Windows->Default Window Size->Large). I suspect memory overflow due to my screen's unusually high resolution, or possibly its unusually high vertical resolution.
Other symptoms:
1. drop down menus appear sized and positioned normally, but only as their right and bottom borders.
2. drop down menus actually work if I click my mouse in the correct region
3. alt-key combinations work - e.g., alt-f-o brings up the open file menu
4. Windows alt-tab can be used to change focus from and to Inkscape's window
5. In this erratic state, if I open a file, a new, smaller Inkscape window appears. Controls are operative, but screen updates are incomplete in a way similar to the original Inkscape window, making the new window unusable.
6. If I start Inkscape by opening a file with it, thereafter it runs reliably even with its window "maximized."
Nothing related to this failure is being recorded in Windows Event Viewer. I will attempt to gather more diagnostics via windbg or similar.
Environment:
OS Name Microsoft Windows 7 Professional
Version 6.1.7601 Service Pack 1 Build 7601
System Type x64-based PC
Processor Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz, 2933 Mhz, 2 Core(s), 2 Logical Processor(s)
BIOS Version/Date Hewlett-Packard 786G7 v01.04, 03/04/10
SMBIOS Version 2.6
Time Zone Central Daylight Time
Installed Physical Memory (RAM) 8.00 GB
Total Physical Memory 8.00 GB
Available Physical Memory 4.72 GB
Total Virtual Memory 16.0 GB
Available Virtual Memory 10.1 GB
Page File Space 8.00 GB |
If started maximized without an initial file, Inkscape runs erratically, and quietly dies if I move my mouse to the right or top of the screen.
If and only if started with no initial file and Default Window Size set to "Maximized," both the 32 and 64 bit versions of Inkscape 0.91 exhibit this issue.
This us under Windows 7 64 bit with my 1440 x 2560 resolution screen. My screen is oriented vertically, so 1440 is horizontal and 2560 is vertical resolution.
I strongly suspect this is related to screen resolution, because both versions start OK if I configure their window size to "Large" instead of "Maximized" (preference setting Interface->Windows->Default Window Size->Large). I suspect memory overflow due to my screen's unusually high resolution, or possibly its unusually high vertical resolution.
Other symptoms:
1. drop down menus appear sized and positioned normally, but only as their right and bottom borders.
2. drop down menus actually work if I click my mouse in the correct region
3. alt-key combinations work - e.g., alt-f-o brings up the open file menu
4. Windows alt-tab can be used to change focus from and to Inkscape's window
5. In this erratic state, if I open a file, a new, smaller Inkscape window appears. Controls are operative, but screen updates are incomplete in a way similar to the original Inkscape window, making the new window unusable.
6. If I start Inkscape by opening a file with it, thereafter it runs reliably even with its window "maximized."
Nothing related to this failure is being recorded in Windows Event Viewer. I will attempt to gather more diagnostics via windbg or similar.
Environment:
OS Name Microsoft Windows 7 Professional
Version 6.1.7601 Service Pack 1 Build 7601
System Type x64-based PC
Processor Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz, 2933 Mhz, 2 Core(s), 2 Logical Processor(s)
BIOS Version/Date Hewlett-Packard 786G7 v01.04, 03/04/10
SMBIOS Version 2.6
Time Zone Central Daylight Time
Installed Physical Memory (RAM) 8.00 GB
Total Physical Memory 8.00 GB
Available Physical Memory 4.72 GB
Total Virtual Memory 16.0 GB
Available Virtual Memory 10.1 GB
Page File Space 8.00 GB |
|
| 2015-07-30 13:39:51 |
su_v |
tags |
|
ui win32 |
|
| 2015-07-30 17:30:59 |
Carson Wilson |
description |
If started maximized without an initial file, Inkscape runs erratically, and quietly dies if I move my mouse to the right or top of the screen.
If and only if started with no initial file and Default Window Size set to "Maximized," both the 32 and 64 bit versions of Inkscape 0.91 exhibit this issue.
This us under Windows 7 64 bit with my 1440 x 2560 resolution screen. My screen is oriented vertically, so 1440 is horizontal and 2560 is vertical resolution.
I strongly suspect this is related to screen resolution, because both versions start OK if I configure their window size to "Large" instead of "Maximized" (preference setting Interface->Windows->Default Window Size->Large). I suspect memory overflow due to my screen's unusually high resolution, or possibly its unusually high vertical resolution.
Other symptoms:
1. drop down menus appear sized and positioned normally, but only as their right and bottom borders.
2. drop down menus actually work if I click my mouse in the correct region
3. alt-key combinations work - e.g., alt-f-o brings up the open file menu
4. Windows alt-tab can be used to change focus from and to Inkscape's window
5. In this erratic state, if I open a file, a new, smaller Inkscape window appears. Controls are operative, but screen updates are incomplete in a way similar to the original Inkscape window, making the new window unusable.
6. If I start Inkscape by opening a file with it, thereafter it runs reliably even with its window "maximized."
Nothing related to this failure is being recorded in Windows Event Viewer. I will attempt to gather more diagnostics via windbg or similar.
Environment:
OS Name Microsoft Windows 7 Professional
Version 6.1.7601 Service Pack 1 Build 7601
System Type x64-based PC
Processor Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz, 2933 Mhz, 2 Core(s), 2 Logical Processor(s)
BIOS Version/Date Hewlett-Packard 786G7 v01.04, 03/04/10
SMBIOS Version 2.6
Time Zone Central Daylight Time
Installed Physical Memory (RAM) 8.00 GB
Total Physical Memory 8.00 GB
Available Physical Memory 4.72 GB
Total Virtual Memory 16.0 GB
Available Virtual Memory 10.1 GB
Page File Space 8.00 GB |
If started maximized without an initial file, Inkscape runs erratically, and quietly dies if I move my mouse over the window control buttons (the minimize [_], minimize-down, or close [x] icons at the upper right) or to the right edge of the maximized window.
If and only if started with no initial file and Default Window Size set to "Maximized," both the 32 and 64 bit versions of Inkscape 0.91 exhibit this issue.
This us under Windows 7 64 bit with my 1440 x 2560 resolution screen. My screen is oriented vertically, so 1440 is horizontal and 2560 is vertical resolution.
I suspect this is related to screen resolution, because both versions start OK if I configure their window size to "Large" instead of "Maximized" (preference setting Interface->Windows->Default Window Size->Large). I suspect memory overflow due to my screen's unusually high resolution, or possibly its unusually high vertical resolution.
Other symptoms:
1. drop down menus appear sized and positioned normally, but only as their right and bottom borders.
2. drop down menus actually work if I click my mouse in the correct region
3. alt-key combinations work - e.g., alt-f-o brings up the open file menu
4. Windows alt-tab can be used to change focus from and to Inkscape's window
5. In this erratic state, if I open a file, a new, smaller Inkscape window appears. Controls are operative, but screen updates are incomplete in a way similar to the original Inkscape window, making the new window unusable.
6. If I start Inkscape by opening a file with it, thereafter it runs reliably even with its window "maximized."
Nothing related to this failure is being recorded in Windows Event Viewer. I will attempt to gather more diagnostics via windbg or similar.
Environment:
OS Name Microsoft Windows 7 Professional
Version 6.1.7601 Service Pack 1 Build 7601
System Type x64-based PC
Processor Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz, 2933 Mhz, 2 Core(s), 2 Logical Processor(s)
BIOS Version/Date Hewlett-Packard 786G7 v01.04, 03/04/10
SMBIOS Version 2.6
Time Zone Central Daylight Time
Installed Physical Memory (RAM) 8.00 GB
Total Physical Memory 8.00 GB
Available Physical Memory 4.72 GB
Total Virtual Memory 16.0 GB
Available Virtual Memory 10.1 GB
Page File Space 8.00 GB |
|
| 2015-07-30 18:11:43 |
Carson Wilson |
description |
If started maximized without an initial file, Inkscape runs erratically, and quietly dies if I move my mouse over the window control buttons (the minimize [_], minimize-down, or close [x] icons at the upper right) or to the right edge of the maximized window.
If and only if started with no initial file and Default Window Size set to "Maximized," both the 32 and 64 bit versions of Inkscape 0.91 exhibit this issue.
This us under Windows 7 64 bit with my 1440 x 2560 resolution screen. My screen is oriented vertically, so 1440 is horizontal and 2560 is vertical resolution.
I suspect this is related to screen resolution, because both versions start OK if I configure their window size to "Large" instead of "Maximized" (preference setting Interface->Windows->Default Window Size->Large). I suspect memory overflow due to my screen's unusually high resolution, or possibly its unusually high vertical resolution.
Other symptoms:
1. drop down menus appear sized and positioned normally, but only as their right and bottom borders.
2. drop down menus actually work if I click my mouse in the correct region
3. alt-key combinations work - e.g., alt-f-o brings up the open file menu
4. Windows alt-tab can be used to change focus from and to Inkscape's window
5. In this erratic state, if I open a file, a new, smaller Inkscape window appears. Controls are operative, but screen updates are incomplete in a way similar to the original Inkscape window, making the new window unusable.
6. If I start Inkscape by opening a file with it, thereafter it runs reliably even with its window "maximized."
Nothing related to this failure is being recorded in Windows Event Viewer. I will attempt to gather more diagnostics via windbg or similar.
Environment:
OS Name Microsoft Windows 7 Professional
Version 6.1.7601 Service Pack 1 Build 7601
System Type x64-based PC
Processor Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz, 2933 Mhz, 2 Core(s), 2 Logical Processor(s)
BIOS Version/Date Hewlett-Packard 786G7 v01.04, 03/04/10
SMBIOS Version 2.6
Time Zone Central Daylight Time
Installed Physical Memory (RAM) 8.00 GB
Total Physical Memory 8.00 GB
Available Physical Memory 4.72 GB
Total Virtual Memory 16.0 GB
Available Virtual Memory 10.1 GB
Page File Space 8.00 GB |
If started maximized without an initial file, Inkscape runs erratically, and quietly dies if I move my mouse over the rightmost portion of its maximized window.
If and only if started with no initial file and Default Window Size set to "Maximized," both the 32 and 64 bit versions of Inkscape 0.91 exhibit this issue.
This us under Windows 7 64 bit with my 1440 x 2560 resolution screen. My screen is oriented vertically, so 1440 is horizontal and 2560 is vertical resolution.
I suspect this is related to screen resolution, because both versions start OK if I configure their window size to "Large" instead of "Maximized" (preference setting Interface->Windows->Default Window Size->Large). I suspect memory overflow due to my screen's unusually high resolution, or possibly its unusually high vertical resolution.
Other symptoms:
1. drop down menus appear sized and positioned normally, but only as their right and bottom borders.
2. drop down menus actually work if I click my mouse in the correct region
3. alt-key combinations work - e.g., alt-f-o brings up the open file menu
4. Windows alt-tab can be used to change focus from and to Inkscape's window
5. In this erratic state, if I open a file, a new, smaller Inkscape window appears. Controls are operative, but screen updates are incomplete in a way similar to the original Inkscape window, making the new window unusable.
6. If I start Inkscape by opening a file with it, thereafter it runs reliably even with its window "maximized."
Nothing related to this failure is being recorded in Windows Event Viewer. I will attempt to gather more diagnostics via windbg or similar.
Environment:
OS Name Microsoft Windows 7 Professional
Version 6.1.7601 Service Pack 1 Build 7601
System Type x64-based PC
Processor Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz, 2933 Mhz, 2 Core(s), 2 Logical Processor(s)
BIOS Version/Date Hewlett-Packard 786G7 v01.04, 03/04/10
SMBIOS Version 2.6
Time Zone Central Daylight Time
Installed Physical Memory (RAM) 8.00 GB
Total Physical Memory 8.00 GB
Available Physical Memory 4.72 GB
Total Virtual Memory 16.0 GB
Available Virtual Memory 10.1 GB
Page File Space 8.00 GB
Diagnostics from Inkscape's main (maximized) window captured using Microsoft "Accessible Event Watcher." Notice OBJ_DESTROY occurs just after Location reaches a horizontal value of 50F. I suspect 60 is the threshold value which triggers the failure:
OBJ_LOCATIONCHANGE Event=800B HWND=0000000000000000 idObject=FFFFFFFFFFFFFFF7 idChild=0 ThreadID=D20 Event Time=4F4FF4 Window Class=(none) Module Name=(none) WM_GETOBJECT=[not a window] Location={50B, 4ED, 1, 1}
OBJ_LOCATIONCHANGE Event=800B HWND=0000000000000000 idObject=FFFFFFFFFFFFFFF7 idChild=0 ThreadID=D20 Event Time=4F511D Window Class=(none) Module Name=(none) WM_GETOBJECT=[not a window] Location={50C, 4ED, 1, 1}
OBJ_LOCATIONCHANGE Event=800B HWND=0000000000000000 idObject=FFFFFFFFFFFFFFF7 idChild=0 ThreadID=D20 Event Time=4F51A9 Window Class=(none) Module Name=(none) WM_GETOBJECT=[not a window] Location={50D, 4ED, 1, 1}
OBJ_LOCATIONCHANGE Event=800B HWND=0000000000000000 idObject=FFFFFFFFFFFFFFF7 idChild=0 ThreadID=D20 Event Time=4F51C8 Window Class=(none) Module Name=(none) WM_GETOBJECT=[not a window] Location={50E, 4ED, 1, 1}
OBJ_LOCATIONCHANGE Event=800B HWND=0000000000000000 idObject=FFFFFFFFFFFFFFF7 idChild=0 ThreadID=D20 Event Time=4F5310 Window Class=(none) Module Name=(none) WM_GETOBJECT=[not a window] Location={50F, 4ED, 1, 1}
OBJ_DESTROY (hidden) Event=8001 HWND=00000000003600D4 idObject=0 idChild=0 ThreadID=D20 Event Time=4F54B5 Window Class="" Module Name="" WM_GETOBJECT=0(proxy)
OBJ_HIDE (hidden) Event=8003 HWND=00000000001A0288 idObject=0 idChild=0 ThreadID=D20 Event Time=4F54B5 Window Class="" Module Name="" WM_GETOBJECT=0(proxy) [Error: getting object: hr=0xFFFFFFFF80070057 - The parameter is incorrect.] |
|
| 2015-07-30 18:13:59 |
Carson Wilson |
description |
If started maximized without an initial file, Inkscape runs erratically, and quietly dies if I move my mouse over the rightmost portion of its maximized window.
If and only if started with no initial file and Default Window Size set to "Maximized," both the 32 and 64 bit versions of Inkscape 0.91 exhibit this issue.
This us under Windows 7 64 bit with my 1440 x 2560 resolution screen. My screen is oriented vertically, so 1440 is horizontal and 2560 is vertical resolution.
I suspect this is related to screen resolution, because both versions start OK if I configure their window size to "Large" instead of "Maximized" (preference setting Interface->Windows->Default Window Size->Large). I suspect memory overflow due to my screen's unusually high resolution, or possibly its unusually high vertical resolution.
Other symptoms:
1. drop down menus appear sized and positioned normally, but only as their right and bottom borders.
2. drop down menus actually work if I click my mouse in the correct region
3. alt-key combinations work - e.g., alt-f-o brings up the open file menu
4. Windows alt-tab can be used to change focus from and to Inkscape's window
5. In this erratic state, if I open a file, a new, smaller Inkscape window appears. Controls are operative, but screen updates are incomplete in a way similar to the original Inkscape window, making the new window unusable.
6. If I start Inkscape by opening a file with it, thereafter it runs reliably even with its window "maximized."
Nothing related to this failure is being recorded in Windows Event Viewer. I will attempt to gather more diagnostics via windbg or similar.
Environment:
OS Name Microsoft Windows 7 Professional
Version 6.1.7601 Service Pack 1 Build 7601
System Type x64-based PC
Processor Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz, 2933 Mhz, 2 Core(s), 2 Logical Processor(s)
BIOS Version/Date Hewlett-Packard 786G7 v01.04, 03/04/10
SMBIOS Version 2.6
Time Zone Central Daylight Time
Installed Physical Memory (RAM) 8.00 GB
Total Physical Memory 8.00 GB
Available Physical Memory 4.72 GB
Total Virtual Memory 16.0 GB
Available Virtual Memory 10.1 GB
Page File Space 8.00 GB
Diagnostics from Inkscape's main (maximized) window captured using Microsoft "Accessible Event Watcher." Notice OBJ_DESTROY occurs just after Location reaches a horizontal value of 50F. I suspect 60 is the threshold value which triggers the failure:
OBJ_LOCATIONCHANGE Event=800B HWND=0000000000000000 idObject=FFFFFFFFFFFFFFF7 idChild=0 ThreadID=D20 Event Time=4F4FF4 Window Class=(none) Module Name=(none) WM_GETOBJECT=[not a window] Location={50B, 4ED, 1, 1}
OBJ_LOCATIONCHANGE Event=800B HWND=0000000000000000 idObject=FFFFFFFFFFFFFFF7 idChild=0 ThreadID=D20 Event Time=4F511D Window Class=(none) Module Name=(none) WM_GETOBJECT=[not a window] Location={50C, 4ED, 1, 1}
OBJ_LOCATIONCHANGE Event=800B HWND=0000000000000000 idObject=FFFFFFFFFFFFFFF7 idChild=0 ThreadID=D20 Event Time=4F51A9 Window Class=(none) Module Name=(none) WM_GETOBJECT=[not a window] Location={50D, 4ED, 1, 1}
OBJ_LOCATIONCHANGE Event=800B HWND=0000000000000000 idObject=FFFFFFFFFFFFFFF7 idChild=0 ThreadID=D20 Event Time=4F51C8 Window Class=(none) Module Name=(none) WM_GETOBJECT=[not a window] Location={50E, 4ED, 1, 1}
OBJ_LOCATIONCHANGE Event=800B HWND=0000000000000000 idObject=FFFFFFFFFFFFFFF7 idChild=0 ThreadID=D20 Event Time=4F5310 Window Class=(none) Module Name=(none) WM_GETOBJECT=[not a window] Location={50F, 4ED, 1, 1}
OBJ_DESTROY (hidden) Event=8001 HWND=00000000003600D4 idObject=0 idChild=0 ThreadID=D20 Event Time=4F54B5 Window Class="" Module Name="" WM_GETOBJECT=0(proxy)
OBJ_HIDE (hidden) Event=8003 HWND=00000000001A0288 idObject=0 idChild=0 ThreadID=D20 Event Time=4F54B5 Window Class="" Module Name="" WM_GETOBJECT=0(proxy) [Error: getting object: hr=0xFFFFFFFF80070057 - The parameter is incorrect.] |
If started maximized without an initial file, Inkscape runs erratically, and quietly dies if I move my mouse over the rightmost portion of its maximized window.
If and only if started with no initial file and Default Window Size set to "Maximized," both the 32 and 64 bit versions of Inkscape 0.91 exhibit this issue.
This is under Windows 7 64 bit with my 1440 x 2560 resolution screen. My screen is oriented vertically, so 1440 is horizontal and 2560 is vertical resolution.
I suspect this is related to screen resolution, because both versions start OK if I configure their window size to "Large" instead of "Maximized" (preference setting Interface->Windows->Default Window Size->Large). I suspect memory overflow due to my screen's unusually high resolution, or possibly its unusually high vertical resolution.
Other symptoms:
1. drop down menus appear sized and positioned normally, but only as their right and bottom borders.
2. drop down menus actually work if I click my mouse in the correct region
3. alt-key combinations work - e.g., alt-f-o brings up the open file menu
4. Windows alt-tab can be used to change focus from and to Inkscape's window
5. In this erratic state, if I open a file, a new, smaller Inkscape window appears. Controls are operative, but screen updates are incomplete in a way similar to the original Inkscape window, making the new window unusable.
6. If I start Inkscape by opening a file with it, thereafter it runs reliably even with its window "maximized."
Nothing related to this failure is being recorded in Windows Event Viewer. I will attempt to gather more diagnostics via windbg or similar.
Environment:
OS Name Microsoft Windows 7 Professional
Version 6.1.7601 Service Pack 1 Build 7601
System Type x64-based PC
Processor Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz, 2933 Mhz, 2 Core(s), 2 Logical Processor(s)
BIOS Version/Date Hewlett-Packard 786G7 v01.04, 03/04/10
SMBIOS Version 2.6
Time Zone Central Daylight Time
Installed Physical Memory (RAM) 8.00 GB
Total Physical Memory 8.00 GB
Available Physical Memory 4.72 GB
Total Virtual Memory 16.0 GB
Available Virtual Memory 10.1 GB
Page File Space 8.00 GB
Diagnostics from Inkscape's main (maximized) window captured using Microsoft "Accessible Event Watcher." Notice OBJ_DESTROY occurs just after Location reaches a horizontal value of 50F. I suspect 60 is the threshold value which triggers the failure. When it is reached my mouse pointer is about 90% of the way toward the right edge of my screen:
OBJ_LOCATIONCHANGE Event=800B HWND=0000000000000000 idObject=FFFFFFFFFFFFFFF7 idChild=0 ThreadID=D20 Event Time=4F4FF4 Window Class=(none) Module Name=(none) WM_GETOBJECT=[not a window] Location={50B, 4ED, 1, 1}
OBJ_LOCATIONCHANGE Event=800B HWND=0000000000000000 idObject=FFFFFFFFFFFFFFF7 idChild=0 ThreadID=D20 Event Time=4F511D Window Class=(none) Module Name=(none) WM_GETOBJECT=[not a window] Location={50C, 4ED, 1, 1}
OBJ_LOCATIONCHANGE Event=800B HWND=0000000000000000 idObject=FFFFFFFFFFFFFFF7 idChild=0 ThreadID=D20 Event Time=4F51A9 Window Class=(none) Module Name=(none) WM_GETOBJECT=[not a window] Location={50D, 4ED, 1, 1}
OBJ_LOCATIONCHANGE Event=800B HWND=0000000000000000 idObject=FFFFFFFFFFFFFFF7 idChild=0 ThreadID=D20 Event Time=4F51C8 Window Class=(none) Module Name=(none) WM_GETOBJECT=[not a window] Location={50E, 4ED, 1, 1}
OBJ_LOCATIONCHANGE Event=800B HWND=0000000000000000 idObject=FFFFFFFFFFFFFFF7 idChild=0 ThreadID=D20 Event Time=4F5310 Window Class=(none) Module Name=(none) WM_GETOBJECT=[not a window] Location={50F, 4ED, 1, 1}
OBJ_DESTROY (hidden) Event=8001 HWND=00000000003600D4 idObject=0 idChild=0 ThreadID=D20 Event Time=4F54B5 Window Class="" Module Name="" WM_GETOBJECT=0(proxy)
OBJ_HIDE (hidden) Event=8003 HWND=00000000001A0288 idObject=0 idChild=0 ThreadID=D20 Event Time=4F54B5 Window Class="" Module Name="" WM_GETOBJECT=0(proxy) [Error: getting object: hr=0xFFFFFFFF80070057 - The parameter is incorrect.] |
|
| 2015-07-30 18:43:21 |
Carson Wilson |
attachment added |
|
screenshot https://bugs.launchpad.net/inkscape/+bug/1479802/+attachment/4436384/+files/InkscapeBug1.png |
|
| 2015-07-30 18:45:07 |
Carson Wilson |
description |
If started maximized without an initial file, Inkscape runs erratically, and quietly dies if I move my mouse over the rightmost portion of its maximized window.
If and only if started with no initial file and Default Window Size set to "Maximized," both the 32 and 64 bit versions of Inkscape 0.91 exhibit this issue.
This is under Windows 7 64 bit with my 1440 x 2560 resolution screen. My screen is oriented vertically, so 1440 is horizontal and 2560 is vertical resolution.
I suspect this is related to screen resolution, because both versions start OK if I configure their window size to "Large" instead of "Maximized" (preference setting Interface->Windows->Default Window Size->Large). I suspect memory overflow due to my screen's unusually high resolution, or possibly its unusually high vertical resolution.
Other symptoms:
1. drop down menus appear sized and positioned normally, but only as their right and bottom borders.
2. drop down menus actually work if I click my mouse in the correct region
3. alt-key combinations work - e.g., alt-f-o brings up the open file menu
4. Windows alt-tab can be used to change focus from and to Inkscape's window
5. In this erratic state, if I open a file, a new, smaller Inkscape window appears. Controls are operative, but screen updates are incomplete in a way similar to the original Inkscape window, making the new window unusable.
6. If I start Inkscape by opening a file with it, thereafter it runs reliably even with its window "maximized."
Nothing related to this failure is being recorded in Windows Event Viewer. I will attempt to gather more diagnostics via windbg or similar.
Environment:
OS Name Microsoft Windows 7 Professional
Version 6.1.7601 Service Pack 1 Build 7601
System Type x64-based PC
Processor Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz, 2933 Mhz, 2 Core(s), 2 Logical Processor(s)
BIOS Version/Date Hewlett-Packard 786G7 v01.04, 03/04/10
SMBIOS Version 2.6
Time Zone Central Daylight Time
Installed Physical Memory (RAM) 8.00 GB
Total Physical Memory 8.00 GB
Available Physical Memory 4.72 GB
Total Virtual Memory 16.0 GB
Available Virtual Memory 10.1 GB
Page File Space 8.00 GB
Diagnostics from Inkscape's main (maximized) window captured using Microsoft "Accessible Event Watcher." Notice OBJ_DESTROY occurs just after Location reaches a horizontal value of 50F. I suspect 60 is the threshold value which triggers the failure. When it is reached my mouse pointer is about 90% of the way toward the right edge of my screen:
OBJ_LOCATIONCHANGE Event=800B HWND=0000000000000000 idObject=FFFFFFFFFFFFFFF7 idChild=0 ThreadID=D20 Event Time=4F4FF4 Window Class=(none) Module Name=(none) WM_GETOBJECT=[not a window] Location={50B, 4ED, 1, 1}
OBJ_LOCATIONCHANGE Event=800B HWND=0000000000000000 idObject=FFFFFFFFFFFFFFF7 idChild=0 ThreadID=D20 Event Time=4F511D Window Class=(none) Module Name=(none) WM_GETOBJECT=[not a window] Location={50C, 4ED, 1, 1}
OBJ_LOCATIONCHANGE Event=800B HWND=0000000000000000 idObject=FFFFFFFFFFFFFFF7 idChild=0 ThreadID=D20 Event Time=4F51A9 Window Class=(none) Module Name=(none) WM_GETOBJECT=[not a window] Location={50D, 4ED, 1, 1}
OBJ_LOCATIONCHANGE Event=800B HWND=0000000000000000 idObject=FFFFFFFFFFFFFFF7 idChild=0 ThreadID=D20 Event Time=4F51C8 Window Class=(none) Module Name=(none) WM_GETOBJECT=[not a window] Location={50E, 4ED, 1, 1}
OBJ_LOCATIONCHANGE Event=800B HWND=0000000000000000 idObject=FFFFFFFFFFFFFFF7 idChild=0 ThreadID=D20 Event Time=4F5310 Window Class=(none) Module Name=(none) WM_GETOBJECT=[not a window] Location={50F, 4ED, 1, 1}
OBJ_DESTROY (hidden) Event=8001 HWND=00000000003600D4 idObject=0 idChild=0 ThreadID=D20 Event Time=4F54B5 Window Class="" Module Name="" WM_GETOBJECT=0(proxy)
OBJ_HIDE (hidden) Event=8003 HWND=00000000001A0288 idObject=0 idChild=0 ThreadID=D20 Event Time=4F54B5 Window Class="" Module Name="" WM_GETOBJECT=0(proxy) [Error: getting object: hr=0xFFFFFFFF80070057 - The parameter is incorrect.] |
If started maximized without an initial file, Inkscape runs erratically, and quietly dies if I move my mouse over the rightmost portion of its maximized window.
If and only if started with no initial file and Default Window Size set to "Maximized," both the 32 and 64 bit versions of Inkscape 0.91 exhibit this issue.
This is under Windows 7 64 bit with my 1440 x 2560 resolution screen. My screen is oriented vertically, so 1440 is horizontal and 2560 is vertical resolution.
I suspect this is related to screen resolution, because both versions start OK if I configure their window size to "Large" instead of "Maximized" (preference setting Interface->Windows->Default Window Size->Large). I suspect memory overflow due to my screen's unusually high resolution, or possibly its unusually high vertical resolution.
Other symptoms:
1. drop down menus appear sized and positioned normally, but only as their right and bottom borders.
2. drop down menus actually work if I click my mouse in the correct region
3. alt-key combinations work - e.g., alt-f-o brings up the open file menu
4. Windows alt-tab can be used to change focus from and to Inkscape's window
5. In this erratic state, if I open a file, a new, smaller Inkscape window appears. Controls are operative, but screen updates are incomplete in a way similar to the original Inkscape window, making the new window unusable.
6. If I start Inkscape by opening a file with it, thereafter it runs reliably even with its window "maximized."
Nothing related to this failure is being recorded in Windows Event Viewer. I will attempt to gather more diagnostics via windbg or similar.
Environment:
OS Name Microsoft Windows 7 Professional
Version 6.1.7601 Service Pack 1 Build 7601
System Type x64-based PC
Processor Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz, 2933 Mhz, 2 Core(s), 2 Logical Processor(s)
BIOS Version/Date Hewlett-Packard 786G7 v01.04, 03/04/10
SMBIOS Version 2.6
Time Zone Central Daylight Time
Installed Physical Memory (RAM) 8.00 GB
Total Physical Memory 8.00 GB
Available Physical Memory 4.72 GB
Total Virtual Memory 16.0 GB
Available Virtual Memory 10.1 GB
Page File Space 8.00 GB
Diagnostics from Inkscape's main (maximized) window captured using Microsoft "Accessible Event Watcher." Notice OBJ_DESTROY occurs just after Location reaches a horizontal value of 50F. I suspect 60 is the threshold value which triggers the failure. When it is reached my mouse pointer is about 90% of the way toward the right edge of my screen. That corresponds to the edge of the page border, see attached screenshot.
OBJ_LOCATIONCHANGE Event=800B HWND=0000000000000000 idObject=FFFFFFFFFFFFFFF7 idChild=0 ThreadID=D20 Event Time=4F4FF4 Window Class=(none) Module Name=(none) WM_GETOBJECT=[not a window] Location={50B, 4ED, 1, 1}
OBJ_LOCATIONCHANGE Event=800B HWND=0000000000000000 idObject=FFFFFFFFFFFFFFF7 idChild=0 ThreadID=D20 Event Time=4F511D Window Class=(none) Module Name=(none) WM_GETOBJECT=[not a window] Location={50C, 4ED, 1, 1}
OBJ_LOCATIONCHANGE Event=800B HWND=0000000000000000 idObject=FFFFFFFFFFFFFFF7 idChild=0 ThreadID=D20 Event Time=4F51A9 Window Class=(none) Module Name=(none) WM_GETOBJECT=[not a window] Location={50D, 4ED, 1, 1}
OBJ_LOCATIONCHANGE Event=800B HWND=0000000000000000 idObject=FFFFFFFFFFFFFFF7 idChild=0 ThreadID=D20 Event Time=4F51C8 Window Class=(none) Module Name=(none) WM_GETOBJECT=[not a window] Location={50E, 4ED, 1, 1}
OBJ_LOCATIONCHANGE Event=800B HWND=0000000000000000 idObject=FFFFFFFFFFFFFFF7 idChild=0 ThreadID=D20 Event Time=4F5310 Window Class=(none) Module Name=(none) WM_GETOBJECT=[not a window] Location={50F, 4ED, 1, 1}
OBJ_DESTROY (hidden) Event=8001 HWND=00000000003600D4 idObject=0 idChild=0 ThreadID=D20 Event Time=4F54B5 Window Class="" Module Name="" WM_GETOBJECT=0(proxy)
OBJ_HIDE (hidden) Event=8003 HWND=00000000001A0288 idObject=0 idChild=0 ThreadID=D20 Event Time=4F54B5 Window Class="" Module Name="" WM_GETOBJECT=0(proxy) [Error: getting object: hr=0xFFFFFFFF80070057 - The parameter is incorrect.] |
|
| 2017-10-27 21:23:14 |
Patrick Storz |
marked as duplicate |
|
1196761 |
|
