<- Back to Tasks

Linux native port / Windows startup time - Embedded browser

Hello,

Currently embedded chromium browser is unpacked (200+ MB) on each startup in some arbitrary location which lead to slower startup time + unexpected issues (antivirus, extra disk space, etc ). On Linux it goes to /tmp while on windows it goes into window user profile.

"At the first run JxBrowser extracts the binaries from appropriate JAR file into user’s temp directory on macOS and Linux, and AppData\Local\JxBrowser on Windows."

In order to avoid any startup delays and packaging I would propose to store "processed" version of  chromium browser within internal SQX directory structure.

It would fix used disk space variation, improve startup time, isolate some possible problems running from "some" location. That would also enable fluent packaging on Linux with native package manager. Stable distribution, consitent behavior.


Thank you.

Enyx.

Attachments
No attachments
  • Votes 0
  • Project StrategyQuant X
  • Type Feature
  • Status Moved
  • Priority Normal
  • Assignee None

History

DB
#1

Enyx

09.07.2020 08:30

Task created

TT
#2

Tamas

10.07.2020 15:01

Attachment image-0.png added

Thanks for the tip. We will consider to include the extracted binaries in SQX distribution.


"Currently embedded chromium browser is unpacked (200+ MB) on each startup in some arbitrary location which lead to slower startup time"
This is not true. I just checked it and the jar is extracted only at the first run as it is expected.

In my case it is under AppData/Local/JxBrowser
DB
#3

Enyx

10.07.2020 18:35

Attachment sq-2020-07-10_18-25.png added

Hello Tamas,


Thank you for your reply. That's correct but not complete story.


Each release containing different JXB adds to the footprint in the specified directory (see attached file) and this space is not released afterwards.


At the moment my directory on Windows is approx 795MB and growing. Older pre JXB 7.5 releases add approx 500KB each start. Newest ones behave as you described but there is still runtime check during startup and is still not formally part of SQX install folder.


On LNX build (unofficial) these files are stored in "/tmp" which causes access conflict running with different users which is the real problem.


Packaging within SQX build should resolve all these concerns.


Enyx

MF
#4

Mark Fric

16.07.2020 13:11
Task moved to project SQX Linux/Mac support, new link to task: https://sq.projectpanel.com/tasks/sqxlinmac_0001
Votes: 0

Drop files to upload

or

choose files

Max size: 5MB

Not allowed: exe, msi, application, reg, php, js, htaccess, htpasswd, gitignore

...
Wait please