Since the last update I have been getting an information message box with 'Access Violation (0)' when exiting from full screen preview (pressing Esc). If I click the OK box then it goes away and things return to normal. If I hit 'Enter' however, PS shutsdown immediately.
This is happening on both my Desktop & Laptop - both are running Windows 7 64 bit.
Access Violation (0) when closing full screen preview
Access Violation (0) when closing full screen preview
Ian
Home build - AMD 8 core 4.0 GHz, 16GB RAM, Windows 10. Photo Supreme 64 bit, Adobe Photo CC
Home build - AMD 8 core 4.0 GHz, 16GB RAM, Windows 10. Photo Supreme 64 bit, Adobe Photo CC
Re: Access Violation (0)
Please submit a ticket in the bugtracker at http://mantis.idimager.com/view_all_bug_page.php
Gr.
Dirk.
Gr.
Dirk.
Problems searching the forum? Try Google Site Search by adding 'site:forum.idimager.com' to a standard Google search.
Re: Access Violation (0)
I opened an issue a couple of days ago already. Several people have commented but Hert has not acknowledged it yet.
Tom Stoddard
Re: Access Violation (0)
Ah, yes. I had actually seen it, but did not realise it was the same issue.tstoddard wrote:I opened an issue a couple of days ago already. Several people have commented but Hert has not acknowledged it yet.
Gr.
Dirk.
Problems searching the forum? Try Google Site Search by adding 'site:forum.idimager.com' to a standard Google search.
-
andrew.heard
- Posts: 232
- Joined: 15 Jun 10 23:36
Re: Access Violation (0) when closing full screen preview
Is this the bug reported as http://mantis.idimager.com/view.php?id=2769? I see this bug exactly as reported by WIanB in latest PSU but I see that #2769 (reported by Tom) status is "resolved". Not resolved for me. And somewhat different description Mantis - doesn't happen every time I open image in full screen, just occasionally.
-
andrew.heard
- Posts: 232
- Joined: 15 Jun 10 23:36
Re: Access Violation (0) when closing full screen preview
No further comments on this bug in this forum or Mantis since a month ago? Yet it still occurs for me. Simple bug - preview > Esc > Access Violation (0) > annoyance. Given mantis #2769 is now closed I have reported this bug as http://mantis.idimager.com/view.php?id=3023. Some subtle differences although the summary is the same.
Re: Access Violation (0) when closing full screen preview
Here is what I did to try to reproduce this:
1. Select an image thumbnail
2. Click Preview
3. Click Full Screen
4. Tap the Esc Key
5. Returns to standard view of the UI
Appears to be working fine for me. Build 2075, Windows 10, 64 bit.
Andrew, if you are using different steps, what are they?
--P
1. Select an image thumbnail
2. Click Preview
3. Click Full Screen
4. Tap the Esc Key
5. Returns to standard view of the UI
Appears to be working fine for me. Build 2075, Windows 10, 64 bit.
Andrew, if you are using different steps, what are they?
--P
Preston Birdwell
Columbia, CA
Photo Supreme on Puget Systems Obsidian: Win 10-64 bit Intel i5Quad Core 3.3Ghz 32GB RAM, and Puget Systems Traverse Laptop. Chamonix 4x5 and Nikon D-7100.
Please visit my web site at www.gildedmoon.com
Columbia, CA
Photo Supreme on Puget Systems Obsidian: Win 10-64 bit Intel i5Quad Core 3.3Ghz 32GB RAM, and Puget Systems Traverse Laptop. Chamonix 4x5 and Nikon D-7100.
Please visit my web site at www.gildedmoon.com
-
andrew.heard
- Posts: 232
- Joined: 15 Jun 10 23:36
Re: Access Violation (0) when closing full screen preview
Thanks for the interest Preston. Same platform here. My steps are
1. Select an image thumbnail
2. press ctrl+Enter
4. press the Esc Key
5. Returns to standard view of the UI & Access Violation (0) is sometimes displayed
I can't find any pattern on how to reproduce this. It doesn't occur every time I press Esc; maybe only 1 in 20 times. Certainly it is a relatively recent bug.
1. Select an image thumbnail
2. press ctrl+Enter
4. press the Esc Key
5. Returns to standard view of the UI & Access Violation (0) is sometimes displayed
I can't find any pattern on how to reproduce this. It doesn't occur every time I press Esc; maybe only 1 in 20 times. Certainly it is a relatively recent bug.