|
Replies:
21
-
Pages:
2
[
Previous |
1
2
]
-
Last Post:
24 Feb 26, 23:54
Last Post By: kilobravo
|
|
|
Posts:
179
Registered:
24-Feb-2010
|
|
|
|
Re: V39 Make Album Crashes (or is that Crashi? ;=))
Posted:
19 Feb 26, 13:49
in response to: davidekholm
|
|
|
|
Copy all on the AVIF format, David still learning here but the fact that Adobe has already added it to PS tells me there's a pretty good chance it's the next "real deal." I hope so since camera image filesizes are getting out of control. Heck, I just bought a little Fuji XE5 and it happily snaps 40mp images as fast as you can shoot them, each of which even in AVIF are about 40mb's each. I certainly feel for the multitude of forum admins around the Web who obviously have to deal with the storage issue all the time these days.
Anyway, the Older album is still uploading and my math says it will be about seventy minutes if the current rate doesn't change. However, while being impatient for the upload to finish, I pulled up the sys console and saw a bunch of warnings, these being the last few entries with everything before all regarding the :07 entry:
Feb 19, 2026 6:07:09 AM se.datadosen.jalbum.RemoteFSWorkers$RemoteCallable call
WARNING: Caught java.io.IOException: Session Timeout (3600 seconds): closing control connection on connection 2 while processing D:\JALBUM\GALLERY-OLDER\friends\eastern\slides\the-brown-family-1000w.avif
Feb 19, 2026 6:07:09 AM se.datadosen.jalbum.RemoteFSWorkers$RemoteCallable call
WARNING: Retrying
FTP put returned 'Couldn't create data socket. Retrying
Feb 19, 2026 6:19:30 AM se.datadosen.jalbum.RemoteFSWorkers$RemoteCallable call
WARNING: Caught java.io.IOException: com.enterprisedt.net.ftp.FTPException: 425 PASV: Address already in use on connection 13 while processing D:\JALBUM\GALLERY-OLDER\house\2133 whispering oak dr\2023\slides\house-pano_230527.avif
Feb 19, 2026 6:19:30 AM se.datadosen.jalbum.RemoteFSWorkers$RemoteCallable call
WARNING: Retrying
It seems to point to my hosting service (Hostinger) but I never ever have FTP issues with them, at least until now after checking which I no doubt should have done when this began.
Any thoughts and thanks..
|
|
|
Posts:
8,596
Registered:
31-Jan-2006
|
|
|
|
Re: V39 Make Album Crashes (or is that Crashi? ;=))
Posted:
19 Feb 26, 15:57
in response to: kilobravo
|
|
|
|
Several times in the past I've had strange uploading problems. Both times, it turned out not be down to a problem with jAlbum or with my web host. And being able to test uploading both to my own web host in Denver, and to the jAlbum hosting, helped solved the mysteries. When I saw the same problems on both hosts, and when using both the jAlbum uploader and FileZilla, I knew where else to start looking.
Once, it turned out to be a faulty cable modem. Swapping it out cured the trouble.
Once, it was a lot tougher to track down. Ultimately I discovered that a lightning strike in the yard had fried a bit of the insulation from the buried cable, where it emerged from the ground and entered the basement. In dry conditions, everything was fine, but if the mulch was damp, I was getting intermittent failures.
Once, I discovered that the Ethernet port on my aging PC had lost its mind. No problem with downloads, but uploads went haywire. I switched to using the WiFi card in the PC, instead, and the problem went away. I'm still limping along with that PC - the WiFi card is a generation too old, so I'm not getting full speed from my ISP (testing with my M2 Macbook Air confirms that with a newer WiFi card, all is well). But the PC is from 2018, so maybe it's time....
|
|
|
Posts:
4,028
Registered:
18-Oct-2002
|
|
|
|
Re: V39 Make Album Crashes (or is that Crashi? ;=))
Posted:
19 Feb 26, 22:04
in response to: JeffTucker
|
|
|
|
I've spotted and fixed one major memory leak during tests on a 6000 image gallery. I can't promise it's the same leak that caused problems for you, but it was introduced in v38, so if you remember that these memory problems started after v38, then this update will most likely fix it. Do a "Perform garbage collection" after a "Make album" to see the amount of used memory. It shouldn't bump up significantly between builds.
To apply the fix, open jAlbum 39.2, then select Tools->External tools->"jAlbum core update" and restart jAlbum when prompted. The splash screen should now read 39.2.2.
Looking forward to your comments!
|
|
|
Posts:
179
Registered:
24-Feb-2010
|
|
|
|
Re: V39 Make Album Crashes (or is that Crashi? ;=))
Posted:
21 Feb 26, 02:01
in response to: davidekholm
|
|
|
|
|
|
Unfortunately, I'm back to heap space errors on both albums and with the 39.2.2 core update and VM parms -Xms256M -Xmx24000M. This is downright maddening.
|
|
|
Posts:
4,028
Registered:
18-Oct-2002
|
|
|
|
Re: V39 Make Album Crashes (or is that Crashi? ;=))
Posted:
21 Feb 26, 13:11
in response to: kilobravo
|
|
|
Unfortunately, I'm back to heap space errors on both albums and with the 39.2.2 core update and VM parms -Xms256M -Xmx24000M. This is downright maddening.
I understand your frustration, and let me assure you that we're taking these reports seriously. If we're dealing with multiple leaks, then fixing one will not be enough. As for the other leak, two users have confirmed that they now have perfectly low memory usage.
I checked your settings, and they're actually quite extreme. You have image bounds set to "4000x1500" and a 3x Variant, this means that the largest image produced will be 12000x4500 pixels. Is this intentional? If you use multiple CPU cores, then the peak RAM usage can go up significantly even if you don't deal with a memory leak.
Try this:
- If possible, change the -Xmx2500M to -Xmx12000M in jAlbum.ini (or jAlbum.cfg on Mac)
- Remove the 3x Variant (at least)
- Lower max number of threads under Preferences->Advanced
And, here's another observation:
- You're producing both 4000x1500 JPEGs + huge AVIF files. If you want to use JPEG as a backup for those <5% that don't have modern web browsers, keep the size down. That will save RAM as well. Actually, when I switched output format from "JPEG" to "AVIF", the RAM usage went down significantly.
|
|
|
Posts:
179
Registered:
24-Feb-2010
|
|
|
|
Re: V39 Make Album Crashes (or is that Crashi? ;=))
Posted:
22 Feb 26, 15:41
in response to: davidekholm
|
|
|
|
|
Thank you SO much for that info, David! I thought I understood variants but obviously, not. And, for whatever reason, in my mind, I thought I had the max image size set to 1500x1500 and no idea when or why it got changed to 4000x1500.
With those two situations resolved, no more heap space memory errors, (at least not yet.)
But I have another problem and one that I've had before and been helped by Jeff before so my apologies to all for my failing memory and dumbo brain.
I have screwed up the upload by sending it to one directory higher than public_html. I have gone through Jeff's answer to the other user with the same issue, i.e., I have set the upload/manage to public_html and then assigned it as the web root of the site.
Keep in mind, I have two albums that are both hosted at the same domain.
(see attached image)
With my Newer album selected, when I go to Upload/Manage and click on Connect, I get the attached image showing the two albums below public_html. Even with the two albums, should I still select public_html as the web root?
The fact that I've been using JA for years and years, I realize I should know the answer and I think I do but when I select public_html as the web root, JA comes back with a dialog box saying "jAlbum can't access this site at http://kilobravo.com. Right click the folder that holds your site and select Mark as web root."
What am I missing? |
|
|
Posts:
179
Registered:
24-Feb-2010
|
|
|
|
Re: V39 Make Album Crashes (or is that Crashi? ;=))
Posted:
24 Feb 26, 23:54
in response to: kilobravo
|
|
|
|
All is well, operator error once again.
|
|
|
|
Legend
|
|
Forum admins
|
|
Helpful Answer
|
|
Correct Answer
|
|
