Author Topic: Seamonkey and AOO4.1.6 problem  (Read 1831 times)

Pete

  • Hero Member
  • *****
  • Thank You
  • -Given: 1
  • -Receive: 36
  • Posts: 850
    • View Profile
Seamonkey and AOO4.1.6 problem
« on: January 24, 2019, 08:26:51 pm »
Hi All

Not sure if this has already been spotted by anyone...


I tried to start seamonkey - Mozilla/5.0 (OS/2; Warp 4.5; rv:45.0) Gecko/20100101 Firefox/45.0 SeaMonkey/2.42.9esr - which failed and did not even raise a blip on the cpu monitor

Checking with pmdll I see that the "nixy bits" nspr4, libc066, libcx0 and gcc1 are reported as "Dll initialization failed"  (or similar wording).

Interesting...

I have made no system changes and no reboots, not even a Desktop restart, since last using seamonkey a couple of hours earlier.

Since last using seamonkey I have used A004.1.6 to write a letter and started cupsd.exe in order to print the letter.

I have also run a couple of OS/2 games that do not use any of the "nixy bits".

So, the culprit is probably AOO4.1.6 as killing cupsd.exe has not helped.

I saved this text as Desktop\seamonkey.txt and closed the editor (e.exe)

Before rebooting I tried a Restart Desktop. That resulted in most of my Desktop disappearing.

I hit the power off button - no, I did not use shutdown as I wanted to force a chkdsk on reboot.

Having powered on the system booted to my nearly fully populated Desktop - just the recently saved seamonkey.txt missing and not found anywhere on the system so I had to recreate the above from memory.

So, was the seamonkey problem Desktop or AOO4.1.6 (or both) related?

I guess the answer is to run seamonkey for a little while then close it then run AOO4.1.6 and cupsd.exe to see what happens.

The answer is that after running AOO4.1.6 the system needs to be rebooted in order to run seamonkey - and possibly any other app that needs the "nixy bits".


Has anyone else made this discovery? - and is there a workaround to avoid the reboot?


Regards

Pete

« Last Edit: January 24, 2019, 08:43:10 pm by Pete »

Dave Yeo

  • Hero Member
  • *****
  • Thank You
  • -Given: 11
  • -Receive: 149
  • Posts: 2168
    • View Profile
Re: Seamonkey and AOO4.1.6 problem
« Reply #1 on: January 24, 2019, 09:08:59 pm »
Sounds like a memory/resource problem. Both SM and AOO use a lot of memory. This can be checked with Theseus if needed
Have you marked either or both DLLs to load high? If not, you're probably running short on lower shared memory. If so, it may be high memory or both. Note that memory fragmentation can also be the problem.

Suggestions, mark the SM DLLs, or at least xul.dll to load code high. I believe there is a utility to do the same with AOO. Then we run into the bug where the kernel does not release the high memory when unloading the DLLs, so use mozturbo (actually smturbo) to keep the Mozilla DLLs loaded and likewise for AOO which I believe includes a utillity to keep the DLLs loaded/preload them. Both should be started at boot up.

Pete

  • Hero Member
  • *****
  • Thank You
  • -Given: 1
  • -Receive: 36
  • Posts: 850
    • View Profile
Re: Seamonkey and AOO4.1.6 problem
« Reply #2 on: January 26, 2019, 02:13:20 am »
Hi Dave

Both Seamonkey and AOO dlls were marked to load code high and smturbo was already in use.

Adding the AOO Quickstart to the mix seems to have resolved the problem to my needs here - no problems with running both apps 6 times which is the most I am ever likely to use them in a 10 - 12 hour period.

In fact I only use AOO a few - maybe 7 - times a month so had never bothered with the Quickstart app with previous AOO releases.


Regards

Pete

Dave Yeo

  • Hero Member
  • *****
  • Thank You
  • -Given: 11
  • -Receive: 149
  • Posts: 2168
    • View Profile
Re: Seamonkey and AOO4.1.6 problem
« Reply #3 on: January 26, 2019, 07:58:29 am »
Good to hear. Another fix might have been to raise your VIRTUALADDRESSLIMIT, though that would have probably just delayed the inevitable.

Pete

  • Hero Member
  • *****
  • Thank You
  • -Given: 1
  • -Receive: 36
  • Posts: 850
    • View Profile
Re: Seamonkey and AOO4.1.6 problem
« Reply #4 on: January 27, 2019, 01:25:31 am »
Hi Dave

It looks like the main culprit is AOO4.1.6

Having moved smturbo and the AOO Quickstart objects out of my Startup folder I rebooted.
Once booted I ran AOO writer.
After exiting AOO writer I cannot run any apps that require any of these dlls: nspr4, libc066, libcx0, gcc1

Should I report this to bitwise?


Regards

Pete

Andreas Schnellbacher

  • Sr. Member
  • ****
  • Thank You
  • -Given: 1
  • -Receive: 24
  • Posts: 440
    • View Profile
Re: Seamonkey and AOO4.1.6 problem
« Reply #5 on: January 27, 2019, 02:20:16 am »
Should I report this to bitwise?
Rather to Arca Noae.

Ian Manners

  • Global Moderator
  • Sr. Member
  • *****
  • Thank You
  • -Given: 37
  • -Receive: 26
  • Posts: 323
  • I am the computer, it is me.
    • View Profile
    • ComKal Networks Australia
Re: Seamonkey and AOO4.1.6 problem
« Reply #6 on: January 27, 2019, 04:40:49 am »
I open PMMail and Firefox (DLL's marked to load code high, other support DLL's also marked to load code high) when I start my computer, I use AOO (code and data marked to load) quite a bit during the evenings as I'm doing a uni summer school unit (last year, several units each semester). AOO's text document and spreadsheet's are opened and closed several times when switching between different documents and spreadsheets, all with no problems. I do not preload any of the programs but I do turn the computer off at the end of each day. Firefox and AOO both get good workouts when I have to write reports, a lot of switching between different websites at uni, library's and other scholarly sites with cut n pasting data etc.
« Last Edit: January 27, 2019, 04:01:43 pm by Ian Manners »
Cheers
Ian B Manners

Pete

  • Hero Member
  • *****
  • Thank You
  • -Given: 1
  • -Receive: 36
  • Posts: 850
    • View Profile
Re: Seamonkey and AOO4.1.6 problem
« Reply #7 on: January 27, 2019, 05:50:58 am »
Hi Andreas

Why Arca Noae rather than bitwise?


Regards

Pete

Andreas Schnellbacher

  • Sr. Member
  • ****
  • Thank You
  • -Given: 1
  • -Receive: 24
  • Posts: 440
    • View Profile
Re: Seamonkey and AOO4.1.6 problem
« Reply #8 on: January 27, 2019, 05:55:24 pm »
Why Arca Noae rather than bitwise?

I can't find Dave's original thread (searching on os2world.com gives only outdated results). But see the text on Steve's page, right column, mozturbo.

So, it looks like a kernel problem.

Edit: It's the mozturbo thread.
« Last Edit: February 01, 2019, 09:20:36 pm by Andreas Schnellbacher »

Dave Yeo

  • Hero Member
  • *****
  • Thank You
  • -Given: 11
  • -Receive: 149
  • Posts: 2168
    • View Profile
Re: Seamonkey and AOO4.1.6 problem
« Reply #9 on: January 27, 2019, 06:37:58 pm »
While there are kernel problems with releasing high memory, Pete's problem sounds more severe and I don't think Arca Noae can fix it. They are aware of the kernel problems.
Pete, what do you have VIRTUALADDRESSLIMIT set at? Also are you running any rpm packages from the experimental repository? And do you have theseus4? If not could you download it from Hobbes?

Pete

  • Hero Member
  • *****
  • Thank You
  • -Given: 1
  • -Receive: 36
  • Posts: 850
    • View Profile
Re: Seamonkey and AOO4.1.6 problem
« Reply #10 on: January 27, 2019, 10:31:32 pm »
Hi Dave

i have VIRTUALADDRESSLIMIT=3072 - I seem to recall it is set this high to enable Virtualbox to run.

I also seem to recall that AOO4.1.6 and Seamonkey needed rpm packages from the experimental repository so, Yes - although I could not name them... possibly libcx amongst others.

I ran ANPM to see if I could spot any experimental repository packages. Not really.
Out of interest I RMB clicked on libcx and selected information.
That tells me that there is a later libcx available in netlabs-exp - I have v0.6.3 installed and 0.6.4 available.

However, the ANPM interface has not marked the Installed libcx as having an update available and it does not show in the Available packages either. It seems an updated libc066 is also available in netlabs-exp.

In fact none of the Installed packages show any updates available - which does not seem right - and Available packages look a lot less than I remember from last run of ANPM several weeks ago.

There does not seem to be a setting in ANPM to turn off the Updated Package Available icon.

I am now wondering if there are some updates required that I am unaware of.

ANPM is set to search "All matching packages" plus "All repositories" and netlabs-exp is included.


I do have Thesus4 installed - and could probably follow comprehensive instructions on using it to try to help analyise the problem should it turn out to be more than an outdated support library or several.


Regards

Pete

Dave Yeo

  • Hero Member
  • *****
  • Thank You
  • -Given: 11
  • -Receive: 149
  • Posts: 2168
    • View Profile
Re: Seamonkey and AOO4.1.6 problem
« Reply #11 on: January 28, 2019, 02:09:00 am »
OK, some ideas, starting out with easy long shots. Double check that all repositories are enabled by going to Manage-->Repositories in ANPM. The install CD/DVD ones should be disabled.
Try reinstalling the NSS and NSPR files, then the LIBC and LIBCX, reboot and retest.
Try lowering your VIRTUALADDRESSLIMIT, perhaps to 2560 or even 2048, reboot and retest.
If you're still getting the same problem, try using Theseus to check how much shared memory is free.
Open Theseus on a freshly booted system, without smturbo and the OO preloader loaded. Hilight a process, which doesn't matter. Go to Process-->Shared Object Summary and click that, scroll to the bottom of the tall window, they'll be an area like,
Code: [Select]
Analysis of 'Free' areas:
There are 27 free blocks which total 58459000 (1446244K or 1412.348M)
The largest 10 free areas are:
 address      size
4C400000  468D0000 (1155904K or 1128.813M)
06580000  10090000 (262720K or 256.563M)
1C010000  01210000 (18496K or 18.063M)
16C80000  006C0000 (6912K or 6.750M)
17C80000  00180000 (1536K or 1.500M)
...
Note the 2 largest free areas, usually the top one is high memory (above 1fffffff) and the other is lower shared memory.
Start AOO writer, under the Shared Object Summary Window, go to Misc-->Contents Update-->Refresh now and compare the figures to see how much free memory you have left. Close AOO and repeat the refresh thing to see if and how much memory got recovered. Hopefully the numbers, especially the low memory block are reasonably large (over perhaps a 100MBs).
You can examine the Shared Object Summary Window also to see what is using a lot of memory.
Hopefully this will tell us something. If not I guess an issue will need to be opened where ever AOO's readme says.

roberto

  • Sr. Member
  • ****
  • Thank You
  • -Given: 16
  • -Receive: 10
  • Posts: 472
    • View Profile
Re: Seamonkey and AOO4.1.6 problem
« Reply #12 on: January 28, 2019, 01:11:01 pm »
Well for me the problem is that if I open vbox with w7, then SM, and try to open the AOO, on a few occasions I get an error SYS0147 that is correct. But in other cases it hangs system without giving me any error, and that is worse. Of approximately 10 attempts, such only twice has the SYS0147 come out.

Doug Bissett

  • Hero Member
  • *****
  • Thank You
  • -Given: 1
  • -Receive: 46
  • Posts: 1251
    • View Profile
Re: Seamonkey and AOO4.1.6 problem
« Reply #13 on: January 28, 2019, 08:13:59 pm »
Quote
Well for me the problem is that if I open vbox with w7, then SM, and try to open the AOO, on a few occasions I get an error SYS0147 that is correct. But in other cases it hangs system without giving me any error, and that is worse. Of approximately 10 attempts, such only twice has the SYS0147 come out.

VBox uses huge amounts of shared memory space (mostly low shared space, from what I have seen). If you load something, and it runs out of shared memory space, the system needs to be able to get enough shared memory to be able to tell you about it (SYS0147). If it can't get enough shared memory space, it hangs, waiting for it to become available, and that rarely happens.

The only known answer, is to load as much as possible into high shared memory, leaving more room in lower shared memory, so you don't run into the problem. AOO can be set to load code, and data, in high shared memory, but it still uses some lower shared memory, and you do need to prevent it from unloading, to avoid the kernel problems when you do unload it. QuickStart does that. FF, SM, and TB, now have the firefox-highmem package, that sets FF to use high memory (I expect that also helps with SM and TB). Now, we also have MOZTURBO, to keep those things from unloading, and triggering the kernel problem. You probably also need to expand the amount of upper shared memory space, that is available. Use VIRTUALADDRESSLIMIT=2560, in CONFIG.SYS, to do that. The max is 3072, but I find that many systems have problems using the max, so 2560 is a good compromise.

Unfortunately, those things only help, they don't fix the problems, so eventually you will have problems.

Pete

  • Hero Member
  • *****
  • Thank You
  • -Given: 1
  • -Receive: 36
  • Posts: 850
    • View Profile
Re: Seamonkey and AOO4.1.6 problem
« Reply #14 on: January 28, 2019, 09:32:32 pm »
Hi Dave

Rebooted, smturbo and Quickstart not started.

Ran Thesus4 - pmshell highlighted

Analysis of 'Free' areas:
There are 9 free blocks which total 9F3C0000 (2608896K or 2547.750M)
The largest 9 free areas are:
 address      size
34000000  89DE0000 (2258816K or 2205.875M)
04300000  12DC0000 (308992K or 301.750M)
1C010000  01EF0000 (31680K or 30.938M)
175B0000  00820000 (8320K or 8.125M)
1E160000  00090000 (576K or 0.563M)
18260000  00040000 (256K or 0.250M)
18080000  00020000 (128K or 0.125M)
1DF10000  00010000 (64K or 0.063M)
1FFF0000  00010000 (64K or 0.063M)



Started AOO4.1.6 writer and Refreshed above results:-

Analysis of 'Free' areas:
There are 75 free blocks which total 98E0E000 (2504760K or 2446.055M)
The largest 10 free areas are:
 address      size
34000000  86E00000 (2209792K or 2158.000M)
04300000  11AA0000 (289408K or 282.625M)
16190000  002F0000 (3008K or 2.938M)
1FFF0000  00010000 (64K or 0.063M)
BC081000  0000F000 (60K or 0.059M)
BCCC1000  0000F000 (60K or 0.059M)
BB002000  0000E000 (56K or 0.055M)
BB142000  0000E000 (56K or 0.055M)
BB252000  0000E000 (56K or 0.055M)
BBC52000  0000E000 (56K or 0.055M)



Closed AOO4.1.6 writer and Refreshed results:-

Analysis of 'Free' areas:
There are 83 free blocks which total 9C56E000 (2561464K or 2501.430M)
The largest 10 free areas are:
 address      size
34000000  86E00000 (2209792K or 2158.000M)
04300000  11E70000 (293312K or 286.438M)
1C010000  01E80000 (31232K or 30.500M)
175B0000  00730000 (7360K or 7.188M)
16190000  00670000 (6592K or 6.438M)
16830000  00480000 (4608K or 4.500M)
16D80000  00340000 (3328K or 3.250M)
BC118000  00208000 (2080K or 2.031M)
1E160000  00050000 (320K or 0.313M)
1E1D0000  00020000 (128K or 0.125M)


While it looks like AOO4.1.6 does not release all memory surely there should be plenty available to run Seamonkey - and AOO again?


Regards

Pete