D 7.1.24 Crashes when creating an exe for deployment (if seaside loaded in image)

[Sanjay Minni]

I am facing with D 7.1.24 (win11) crashing when trying to generate a deployment exe.

here is my observations:
In each case i tried to generate an exe for "Notepad" from the MVP samples

1. Fresh image - generates exe using default settings (...ok)
2. Fresh image with GitHub, ReStore, SQLite3 - generates exe using default settings (...ok)
3. Fresh Image with GitHub, Seaside - (Crashes!!!)
error thrown is "Invalid access to Memory Location ..."
tried with default settings and also after deselecting all options during deployment exe generation

what is it that needs to be done ?
regards
Sanjay

[john.a...@gmail.com]

Hi Sanjay - I'm able to deploy the Notepad example in a fresh image with GitHub and Seaside installed provided I first stop the HTTP Server:

WAHttpServerAdaptor stop.

Without this I get errors near the end of deployment:

HttpServer does not understand #onImageSaveStarting
ThreadPool does not understand #isPoolTooSmall

...but no Invalid Access errors.

Does this help?

[Sanjay Minni]

Hi John,
Thanks ... here is where i progressed with your message and some questions below

Starting with a fresh image with
1. Seaside loaded ... then
WAHttpServerAdaptor stop
Deployment exe generated with default option -> compiles and notepad runs fine

2. Now to also start a seaside server at runtime
added the line WAHttpServer startOn: 8080 in NotepadSessionManager
Generated deployment exe after deselecting all options except RemoveClassBuilder
(Has to deselect all options as I was was otherwise getting an "Internal error" on the browser webpage and a popup
"unidentified object does not understand #evaluatePendingAction" when pointing to localhost:8080)
Ran exe -> notepad started, also Seaside server came up when pointed browser to it

3. Loaded MaterialDesignLite also - but no matter whatever i did i could not get it to compile /work - Deployment exe crashes / does not work at various stages
It shows 2 server adaptors albeit 1 stopped
I tried using WAServerManager startup / shutdown also

Questions
1. Is there a GUI tool to see the adaptors and stop (I remember pharo had one)
2. is the command above "WAServerManager startup/shutdown the correct way to stop multiple adaptors or what is to stop and start ?

pls advice on getting both Seaside and MaterialDL to get into deployment

thanks
Sanjay

[john.a...@gmail.com]

Hi - I haven't deployed an app using MDL so can't advise on that.

However I have a deployed app using Seaside+Bootstrap and have a line in the build script to move WAResponse class>>#initializeStatusMessages into the 'must not strip' method category. Maybe this will help?

John

[Sanjay Minni]

Hi

For the time being i solved by starting with a fresh image and loading MaterialDesignLite (which in turn loaded seaside), there seems to be only one entry for the adaptor and deploy exe generates just fine.

To restart the adaptor in the image (after WAHttpServerAdaptor stop) - i do: WAHttpServerAdaptor startOn: 8080 <== is that a good way ?

thanks
Sanjay