Smalltalk › Instantiations

Failed to place FIXED memory at required address; creating PRIVATE

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

6 messages Options

Marten Feldtmann-2

Failed to place FIXED memory at required address; creating PRIVATE

Well, when starting lots of my IC'ed headless Seaside demo applications I noticed the following error in output of few (not all) of these processes:

...
Failed to place FIXED memory at required address; creating PRIVATE
...

I notice, that processes showing this error at the beginning consumes around 4 MB more memory than the normal system (16 MB instead of 12 MB).

What does this error means ?

--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To view this discussion on the web visit https://groups.google.com/d/msg/va-smalltalk/-/KoX7gEQUzD4J.
To post to this group, send email to [hidden email].
To unsubscribe from this group, send email to [hidden email].
For more options, visit this group at http://groups.google.com/group/va-smalltalk?hl=en.

John O'Keefe-3

Re: Failed to place FIXED memory at required address; creating PRIVATE

Marten -

This is something that has always happened -- we just never told anyone about it. In order to share memory between processes, the memory has to be allocated at the exact same memory address. If that is true, you will get PUBLIC memory; if not PRIVATE. Remember that the shared memory manager doesn't go away when you shutdown an image on Unix (1 es process is still running).

John

--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To view this discussion on the web visit https://groups.google.com/d/msg/va-smalltalk/-/OihY8MrydgEJ.
To post to this group, send email to [hidden email].
To unsubscribe from this group, send email to [hidden email].
For more options, visit this group at http://groups.google.com/group/va-smalltalk?hl=en.

Leonardo Cesario

Re: Failed to place FIXED memory at required address; creating PRIVATE

Hi,

I have the same problem with two images (AbtStackDumpStartUp) in 8.0.3.
This error didn't happen in VA 7.5.2.

One of the images, is a core able to run N instances of the other, and each one is connected to the core.

I tried to modify the configuration of abtnx.ini and some parameters (-mfXXXX), but nothing changes.

How can I solve this situation?

Thanks!

Leonardo

Wayne Johnston

Re: Failed to place FIXED memory at required address; creating PRIVATE

In reply to this post by John O'Keefe-3

John, I am not sure if you are saying this message is indicating a problem or not. I see it from our packaged client, now that I am using 8.5.1. However it seems like it only happens when I run two of our clients on the same machine (connected to a server but using different ports from each other). Everything seems to work great, but just curious if I should worry about this message. Thanks.

--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To view this discussion on the web visit https://groups.google.com/d/msg/va-smalltalk/-/p-KQWZAa9ZQJ.
To post to this group, send email to [hidden email].
To unsubscribe from this group, send email to [hidden email].
For more options, visit this group at http://groups.google.com/group/va-smalltalk?hl=en.

John O'Keefe-3

Re: Failed to place FIXED memory at required address; creating PRIVATE

Wayne -

I am saying that it is not something to worry about. It simply means that memory usage couldn't be completely optimized for the second image. The message should be conditioned on the -v command line option, but isn't -- I've opened a case to fix that.

John
On Wednesday, September 5, 2012 12:04:59 PM UTC-4, Wayne Johnston wrote:

John, I am not sure if you are saying this message is indicating a problem or not. I see it from our packaged client, now that I am using 8.5.1. However it seems like it only happens when I run two of our clients on the same machine (connected to a server but using different ports from each other). Everything seems to work great, but just curious if I should worry about this message. Thanks.

--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To view this discussion on the web visit https://groups.google.com/d/msg/va-smalltalk/-/vOaA5Zpjw7AJ.
To post to this group, send email to [hidden email].
To unsubscribe from this group, send email to [hidden email].
For more options, visit this group at http://groups.google.com/group/va-smalltalk?hl=en.

Marten Feldtmann-2

Re: Failed to place FIXED memory at required address; creating PRIVATE

In reply to this post by Marten Feldtmann-2

After playing with 8.5.2 and ICs I got errors

"2012-09-25 15:45:58,874 root DEBUG Trying to load component <win_zmqnetlog.ic>"
"2012-09-25 15:45:58,874 root DEBUG Before loading component <win_zmqnetlog.ic>"

EsMappedFileMap failed to map view of 'EsApi_ROM_SEG_SAS_d22b0f7f_00000007_d22b0f3e' at 0x00000000, errorCode = 0x000001e7
Memory allocation error: Failed to place PUBLIC IC ROM at required address
UIProcess reportError: Primitive failed in: EmSystemConfiguration>>#loadComponentPrimitive: due to Not enough memory

It was impossible to make that stable - out of 10 start attempts of that application perhaps 8 failed and only 2 were starting with success.

I searched in the Internet and found a posting around 2000/2001 in the old groups describing this problem. The solution seems to be to turn off sharing of ICs via the "-msd" switch at command line.

--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To view this discussion on the web visit https://groups.google.com/d/msg/va-smalltalk/-/iR81AgJe2RwJ.
To post to this group, send email to [hidden email].
To unsubscribe from this group, send email to [hidden email].
For more options, visit this group at http://groups.google.com/group/va-smalltalk?hl=en.