Proton BASIC Community

I get this error after a compile on Windows10

Hello,

I also get the same error on a win 10 machine.
This is when I compile code that was originally written in PDS.

Thanks

Paul

private wallpaper

W7 x64

This happens on returning from a compile or on starting a compile?
Cancel  that, I can see it here.
Found it - will get a new install out asap

When the compilation is finished.
Hex file is produced, that's okay.

THere should be a log file in Documents - InstallDebugData.log
Could you send me a copy You'll find the link under Help, Studio Support

I sent it as a PM from the forum.

Fixed thank you very much

Has this been fixed already? That's amazing.
Where can I get the fix from or the newer version?

Thank you

Paul

Quote from: Dogboy on Mar 27, 2021, 08:11 PMHas this been fixed already? That's amazing.
Where can I get the fix from or the newer version?

Thank you

Paul

Post #10 in this thread https://protoncompiler.com/index.php/topic,229.0.html

Thank you for sorting this problem out so quickly.

error in w7

@Pepe

Quote from: JohnB on Mar 27, 2021, 06:25 PMThanks, I have just uploaded a new version which should not access violate.
I'll update the links in a later issue.

To All please download the updated version

Judging by the timing this is a new occurrence.  Can you describe what you were doing at the time of the access violation. Were you opening from recently used or a fresh of from a restart
Also is the PC a 32 or 64 bit machine?

Okey Dokey I have another access violation, not sure why, but I am running the compiler manual and data sheet manual in the ide and it becomes sluggish with both loaded, no idea if that's related to the violation.I was scrolling though the datasheet when it threw the error.  Windows10 64 bit

Fun Fact: If it can be broken, I can break it.   

Error in w7 32bits with new version when I open a project show  acces violation next
 I view then program and can compile it

@Garry Scott
How were you scrolling through the data sheet? I have found that scrolling works well with the mouse wheel but not dragging the scroll button.  It appears that dragging the scroll button causes the viewer to queue up successive repaints which eventually brings things down to a halt. The PDF viewer is a 3rd party application which I have very limited control of, I have reported a number of bugs to the developers with only partial success.

@Pepe
After the access violation does everything perform normally? 
I will try and reproduce the error here on a virtual machine, I don't have any 32bit PCs and only have Windows 10 running on real  64bit machines.

Hi John

Same problem, seems all to be all 32bit P.C. systems, the error occurs when opening a file even a new file.
Correction opening or closing any page including pdf.
Dave

OS Name Microsoft Windows 10 Pro
Version 10.0.14393 Build 14393
System Type X86-based PC


Dave

@DaveS I am coming to that conclusion.
I am running up my 32bit Win7 VM to see if I can repeat it here.

Well I have just run up a 32bit VM (Win7), installed Positron Studio and Proton.  Ran up Positron Studio and imported the demo project provided with the installation (C:\Users\<UserName>\AppData\Positron Studio\PRTOS24_Demo.pspkg).  Project opened up perfectly. Sods law!

My suspicion is that the problem is associated with the docking system.  All screens in studio are docked windows, when you open or close a page a new dock window is created or destroyed respectively. By default when a document is closed the tab jumps back to the first document which is not what you would expect when closing tabs so I added some code in to select the first tab to the left of the deleted tab. This has frequently been the cause of access violations due to what seem to be race conditions between the underlying doc management and loading in the new page.

Anyway, I would like to try removing this routine which chooses the adjacent tab.  Would anyone with a win32 PC care to email me on Support@PositronStudio.co.uk and I will send them a link to a new 32bit executable with the the above code removed.