jhnath / contexteditor

Automatically exported from code.google.com/p/contexteditor
0 stars 0 forks source link

Access violation when minimise-restore-close #45

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1.Open a file with ConTEXT
2.Minimise ConTEXT
3.Restore ConTEXT
4.Click on close
Nothing more.

What is the expected output?
The window closes.

What do you see instead?
A message error : "Access violation at address 0063BD2B in module 
'ConTEXT.exe'. Read of address 00000038."
Unable to close the window.

What version of the product are you using?
ConTEXT 0.98.6 (installed)

On what operating system?
Windows 7 (64 bits)

Please provide any additional information below.
The error does not always occur, but often.

Original issue reported on code.google.com by rroro...@gmail.com on 4 Nov 2010 at 8:45

GoogleCodeExporter commented 8 years ago
Thats strange, im using Windows 7 (64 bit) and dont have the issue.

Are you Minimising and Restoring the Main ConTEXT Program or the files opened?

Beanie

Original comment by info%con...@gtempaccount.com on 4 Nov 2010 at 9:15

GoogleCodeExporter commented 8 years ago
I minimise and restore the main window of ConTEXT, by clicking the button in 
the right-hand corner (something like 'reduce' or 'minimise' in english - I'm 
french - : the third button).

And whatever the file I open or create, when I click to close ConTEXT (the main 
window), I have often the error. And it seems to be linked with the 
minimise-restore the window. Because, only with the simple test indicated above 
(open-minimise-restore-close), I have the problem.

Some additional information :
   - Just before the error displays, all the syntaxic colors disappear. Whatever the type of files (CSS, Python, PHP, ...)
   - When I click on 'OK' of the error message box, I can always click in the ConTEXT interface (for example open a menu). But when I click on a button or if I type a character, the same error appears (with a different place in memory).

Sorry for my approximative english ...

Original comment by rroro...@gmail.com on 5 Nov 2010 at 6:24