[fpc-pascal] Live pascal

[Michael Van Canneyt]

On Mon, 23 Feb 2026, Tomas Hajny via fpc-pascal wrote:

> On 2026-02-23 16:58, Michael Van Canneyt wrote:
>> On Mon, 23 Feb 2026, Tomas Hajny via fpc-pascal wrote:
> .
> .
>>> I tried again now, the result is the same (64-bit Firefox running on MS 
>>> Windows at the moment). It already happened with the first example loaded 
>>> by default (i.e. "Hello World"), but I got the same when trying "String 
>>> operations" demo as well. Attached you'll find export from the browser 
>>> console - feel free to ask if there's anything else I could provide. I 
>>> tried reloading the page using F5 key -> no difference.
>> 
>> Well, it seems related to your browser:
>> 
>> "uncaught exception: out of memory 7"
>> 
>> Do you have some safety mechanisms in place ?
>
> Like? I use uBlock Origin extension, but it didn't block anything on that 
> page and I tried also reloading the page after disabling this extension. The 
> default browser on this machine is MS Edge and potential GPO enforced 
> security settings are more likely to be in place for that one - but it works 
> there (as I realized now). If I open the page in an anonymous window of 
> Firefox, it also shows the out of memory error in the browser console, but it 
> breaks even before getting to the point of enabling the buttons, i.e. I see 
> "Loading compiler..." and the buttons are disabled. I guess that there should 
> be some mechanism for the page to demand more memory from the browser and it 
> probably asks for less than what is necessary on both Firefox and Safari 
> (whereas it works in Chrome derived browsers apparently). Interestingly, it 
> works from Firefox running on a mobile phone (Android). So yes, it's likely 
> related to the browser, but that doesn't necessarily mean that I could or 
> should fix it on my side...

No, but without knowing the cause there is little I can do...

I use firefox only, and it has worked all through the development cycle.
I also use uBlock origin. I was on a linux, though I don't see how that would matter.

The good news is: I can reproduce the issue in Safari: it fails with a 'out of memory'
So I'll do some testing on safari. First web search is not making me
optimistic, seems safari and wasm are not a happy couple.


Michael.