Info on implementation limits

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
13 messages Options
Reply | Threaded
Open this post in threaded view
|

Info on implementation limits

GLASS mailing list

Hi,

 

are there any information about implementation limits of Gemstone Smalltalk?

 

Concrete issue:

I try to input a source file (2.1. MB – can this work?).

Topaz dies (Windows reports that Topaz is not working anymore…)

Last thing in the log file is a method with 743 literals – is this an issue?

My naïve theory: Gemstone (Topaz?) cannot compile the method, but dies without error.

 

Any ideas?

 

Thanks,

                Christian

 


_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass
Reply | Threaded
Open this post in threaded view
|

Re: Info on implementation limits

GLASS mailing list

Hello Christian,

well, the size of such a file is not a problem. In one of our projects, the source code file of my automatically generated model has a size of around 8.7 MByte.


Marten


_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass
Reply | Threaded
Open this post in threaded view
|

Re: Info on implementation limits

GLASS mailing list
In reply to this post by GLASS mailing list

Christian,

Could you send me the full topaz log file? We need that to understand what might be going on ...

Thanks,

Dale


On 7/11/17 1:07 AM, Christian Haider via Glass wrote:

Hi,

 

are there any information about implementation limits of Gemstone Smalltalk?

 

Concrete issue:

I try to input a source file (2.1. MB – can this work?).

Topaz dies (Windows reports that Topaz is not working anymore…)

Last thing in the log file is a method with 743 literals – is this an issue?

My naïve theory: Gemstone (Topaz?) cannot compile the method, but dies without error.

 

Any ideas?

 

Thanks,

                Christian

 



_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass


_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass
Reply | Threaded
Open this post in threaded view
|

WG: Info on implementation limits

GLASS mailing list

(resent, because Google blocked the attachment)

 

Von: Christian Haider [mailto:[hidden email]]
Gesendet: Mittwoch, 12. Juli 2017 09:53
An: '[hidden email]' <[hidden email]>
Cc: 'Dale Henrichs' <[hidden email]>
Betreff: AW: [Glass] Info on implementation limits

 

From replies off list, I heard, that big input files are not a problem. Good to know, thank you.

 

For the crash on the big method, I investigated and created an input file which reproduces the problem (attached as bigMethod.gs). The log is attached as well.

My theory was wrong. It seems not to be a problem with many literals in a method, but something else.

When I input the file in a Topaz shell (on windows), it works seamless and the method can be called.

Steps:

  1. Login to topaz
  2. enter ‘output push c:\image\bigMethod.log’[CR]
  3. enter ‘input c:\image\bigMethod.gs’[CR]
  4. all fine!

 

But if I do the same with a batch file which uses the script loadBigMethod.tpz (attached),

The Topaz window opens, it stays there for about 10 seconds (the step 3 above took no time) and the crashes (Windows pops up with “the program does not work anymore…” or something like that (I have a German version).

 

Any idea?

Thanks

 

 

Config data (running on Windows 10):

|    PROGRAM: topaz, Linear GemStone Interface (Remote Session)               |

|    VERSION: 3.3.5, Thu May  4 11:44:37 2017                                 |

|      BUILD: gss64_3_3_x_branch-41643                                        |

|  BUILT FOR: x86-64/Windows7                                                 |

|       MODE: 64 bit                                                          |

| RUNNING ON: 4-CPU haider-pc: Unknown CPU, Windows NT 6.2 build 9200         |

 

 

Von: Glass [[hidden email]] Im Auftrag von Dale Henrichs via Glass
Gesendet: Dienstag, 11. Juli 2017 18:20
An: [hidden email]
Betreff: Re: [Glass] Info on implementation limits

 

Christian,

Could you send me the full topaz log file? We need that to understand what might be going on ...

Thanks,

Dale

 

On 7/11/17 1:07 AM, Christian Haider via Glass wrote:

Hi,

 

are there any information about implementation limits of Gemstone Smalltalk?

 

Concrete issue:

I try to input a source file (2.1. MB – can this work?).

Topaz dies (Windows reports that Topaz is not working anymore…)

Last thing in the log file is a method with 743 literals – is this an issue?

My naïve theory: Gemstone (Topaz?) cannot compile the method, but dies without error.

 

Any ideas?

 

Thanks,

                Christian

 



_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass

 


_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass

bigMethod.zip (10K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: WG: Info on implementation limits

GLASS mailing list

Found another one (sudden death):

A method returning a literal 78 KB String.

What is the limit on the method source size?

Or, is there a limit for strings inside a method?

 

Cheers,

                Christian

 

Von: Glass [mailto:[hidden email]] Im Auftrag von Christian Haider via Glass
Gesendet: Mittwoch, 12. Juli 2017 11:37
An: [hidden email]
Betreff: [Glass] WG: Info on implementation limits

 

(resent, because Google blocked the attachment)

 

Von: Christian Haider [[hidden email]]
Gesendet: Mittwoch, 12. Juli 2017 09:53
An: '[hidden email]' <[hidden email]>
Cc: 'Dale Henrichs' <[hidden email]>
Betreff: AW: [Glass] Info on implementation limits

 

From replies off list, I heard, that big input files are not a problem. Good to know, thank you.

 

For the crash on the big method, I investigated and created an input file which reproduces the problem (attached as bigMethod.gs). The log is attached as well.

My theory was wrong. It seems not to be a problem with many literals in a method, but something else.

When I input the file in a Topaz shell (on windows), it works seamless and the method can be called.

Steps:

  1. Login to topaz
  2. enter ‘output push c:\image\bigMethod.log’[CR]
  3. enter ‘input c:\image\bigMethod.gs’[CR]
  4. all fine!

 

But if I do the same with a batch file which uses the script loadBigMethod.tpz (attached),

The Topaz window opens, it stays there for about 10 seconds (the step 3 above took no time) and the crashes (Windows pops up with “the program does not work anymore…” or something like that (I have a German version).

 

Any idea?

Thanks

 

 

Config data (running on Windows 10):

|    PROGRAM: topaz, Linear GemStone Interface (Remote Session)               |

|    VERSION: 3.3.5, Thu May  4 11:44:37 2017                                 |

|      BUILD: gss64_3_3_x_branch-41643                                        |

|  BUILT FOR: x86-64/Windows7                                                 |

|       MODE: 64 bit                                                          |

| RUNNING ON: 4-CPU haider-pc: Unknown CPU, Windows NT 6.2 build 9200         |

 

 

Von: Glass [[hidden email]] Im Auftrag von Dale Henrichs via Glass
Gesendet: Dienstag, 11. Juli 2017 18:20
An: [hidden email]
Betreff: Re: [Glass] Info on implementation limits

 

Christian,

Could you send me the full topaz log file? We need that to understand what might be going on ...

Thanks,

Dale

 

On 7/11/17 1:07 AM, Christian Haider via Glass wrote:

Hi,

 

are there any information about implementation limits of Gemstone Smalltalk?

 

Concrete issue:

I try to input a source file (2.1. MB – can this work?).

Topaz dies (Windows reports that Topaz is not working anymore…)

Last thing in the log file is a method with 743 literals – is this an issue?

My naïve theory: Gemstone (Topaz?) cannot compile the method, but dies without error.

 

Any ideas?

 

Thanks,

                Christian

 

 

_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass

 


_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass
Reply | Threaded
Open this post in threaded view
|

Re: WG: Info on implementation limits

GLASS mailing list
In reply to this post by GLASS mailing list

Thanks Christian. We'll let you know what we find out ...

Dale


On 7/12/17 2:37 AM, Christian Haider wrote:

(resent, because Google blocked the attachment)

 

Von: Christian Haider [[hidden email]]
Gesendet: Mittwoch, 12. Juli 2017 09:53
An: '[hidden email]' [hidden email]
Cc: 'Dale Henrichs' [hidden email]
Betreff: AW: [Glass] Info on implementation limits

 

From replies off list, I heard, that big input files are not a problem. Good to know, thank you.

 

For the crash on the big method, I investigated and created an input file which reproduces the problem (attached as bigMethod.gs). The log is attached as well.

My theory was wrong. It seems not to be a problem with many literals in a method, but something else.

When I input the file in a Topaz shell (on windows), it works seamless and the method can be called.

Steps:

  1. Login to topaz
  2. enter ‘output push c:\image\bigMethod.log’[CR]
  3. enter ‘input c:\image\bigMethod.gs’[CR]
  4. all fine!

 

But if I do the same with a batch file which uses the script loadBigMethod.tpz (attached),

The Topaz window opens, it stays there for about 10 seconds (the step 3 above took no time) and the crashes (Windows pops up with “the program does not work anymore…” or something like that (I have a German version).

 

Any idea?

Thanks

 

 

Config data (running on Windows 10):

|    PROGRAM: topaz, Linear GemStone Interface (Remote Session)               |

|    VERSION: 3.3.5, Thu May  4 11:44:37 2017                                 |

|      BUILD: gss64_3_3_x_branch-41643                                        |

|  BUILT FOR: x86-64/Windows7                                                 |

|       MODE: 64 bit                                                          |

| RUNNING ON: 4-CPU haider-pc: Unknown CPU, Windows NT 6.2 build 9200         |

 

 

Von: Glass [[hidden email]] Im Auftrag von Dale Henrichs via Glass
Gesendet: Dienstag, 11. Juli 2017 18:20
An: [hidden email]
Betreff: Re: [Glass] Info on implementation limits

 

Christian,

Could you send me the full topaz log file? We need that to understand what might be going on ...

Thanks,

Dale

 

On 7/11/17 1:07 AM, Christian Haider via Glass wrote:

Hi,

 

are there any information about implementation limits of Gemstone Smalltalk?

 

Concrete issue:

I try to input a source file (2.1. MB – can this work?).

Topaz dies (Windows reports that Topaz is not working anymore…)

Last thing in the log file is a method with 743 literals – is this an issue?

My naïve theory: Gemstone (Topaz?) cannot compile the method, but dies without error.

 

Any ideas?

 

Thanks,

                Christian

 



_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass

 



_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass
Reply | Threaded
Open this post in threaded view
|

Re: WG: Info on implementation limits

GLASS mailing list
In reply to this post by GLASS mailing list

Christian,

Can you provide more details, so we can try to check this one out? Log file, method source, etc.

Thanks,

Dale


On 7/12/17 6:18 AM, Christian Haider wrote:

Found another one (sudden death):

A method returning a literal 78 KB String.

What is the limit on the method source size?

Or, is there a limit for strings inside a method?

 

Cheers,

                Christian

 

Von: Glass [[hidden email]] Im Auftrag von Christian Haider via Glass
Gesendet: Mittwoch, 12. Juli 2017 11:37
An: [hidden email]
Betreff: [Glass] WG: Info on implementation limits

 

(resent, because Google blocked the attachment)

 

Von: Christian Haider [[hidden email]]
Gesendet: Mittwoch, 12. Juli 2017 09:53
An: '[hidden email]' <[hidden email]>
Cc: 'Dale Henrichs' <[hidden email]>
Betreff: AW: [Glass] Info on implementation limits

 

From replies off list, I heard, that big input files are not a problem. Good to know, thank you.

 

For the crash on the big method, I investigated and created an input file which reproduces the problem (attached as bigMethod.gs). The log is attached as well.

My theory was wrong. It seems not to be a problem with many literals in a method, but something else.

When I input the file in a Topaz shell (on windows), it works seamless and the method can be called.

Steps:

  1. Login to topaz
  2. enter ‘output push c:\image\bigMethod.log’[CR]
  3. enter ‘input c:\image\bigMethod.gs’[CR]
  4. all fine!

 

But if I do the same with a batch file which uses the script loadBigMethod.tpz (attached),

The Topaz window opens, it stays there for about 10 seconds (the step 3 above took no time) and the crashes (Windows pops up with “the program does not work anymore…” or something like that (I have a German version).

 

Any idea?

Thanks

 

 

Config data (running on Windows 10):

|    PROGRAM: topaz, Linear GemStone Interface (Remote Session)               |

|    VERSION: 3.3.5, Thu May  4 11:44:37 2017                                 |

|      BUILD: gss64_3_3_x_branch-41643                                        |

|  BUILT FOR: x86-64/Windows7                                                 |

|       MODE: 64 bit                                                          |

| RUNNING ON: 4-CPU haider-pc: Unknown CPU, Windows NT 6.2 build 9200         |

 

 

Von: Glass [[hidden email]] Im Auftrag von Dale Henrichs via Glass
Gesendet: Dienstag, 11. Juli 2017 18:20
An: [hidden email]
Betreff: Re: [Glass] Info on implementation limits

 

Christian,

Could you send me the full topaz log file? We need that to understand what might be going on ...

Thanks,

Dale

 

On 7/11/17 1:07 AM, Christian Haider via Glass wrote:

Hi,

 

are there any information about implementation limits of Gemstone Smalltalk?

 

Concrete issue:

I try to input a source file (2.1. MB – can this work?).

Topaz dies (Windows reports that Topaz is not working anymore…)

Last thing in the log file is a method with 743 literals – is this an issue?

My naïve theory: Gemstone (Topaz?) cannot compile the method, but dies without error.

 

Any ideas?

 

Thanks,

                Christian

 

 

_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass

 



_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass
Reply | Threaded
Open this post in threaded view
|

Re: WG: Info on implementation limits

GLASS mailing list

Dale,

 

attached is the source method from VW – I found a much smaller one (4022 Byte literal string) with the same problem.

The setup is identical with the prior problem.

 

So, there are no simple answers to the limits questions?

 

Cheers,

                Christian

 

Von: Dale Henrichs [mailto:[hidden email]]
Gesendet: Mittwoch, 12. Juli 2017 15:50
An: Christian Haider <[hidden email]>; [hidden email]
Betreff: Re: AW: [Glass] WG: Info on implementation limits

 

Christian,

Can you provide more details, so we can try to check this one out? Log file, method source, etc.

Thanks,

Dale

 

On 7/12/17 6:18 AM, Christian Haider wrote:

Found another one (sudden death):

A method returning a literal 78 KB String.

What is the limit on the method source size?

Or, is there a limit for strings inside a method?

 

Cheers,

                Christian

 

Von: Glass [[hidden email]] Im Auftrag von Christian Haider via Glass
Gesendet: Mittwoch, 12. Juli 2017 11:37
An: [hidden email]
Betreff: [Glass] WG: Info on implementation limits

 

(resent, because Google blocked the attachment)

 

Von: Christian Haider [[hidden email]]
Gesendet: Mittwoch, 12. Juli 2017 09:53
An: '[hidden email]' <[hidden email]>
Cc: 'Dale Henrichs' <[hidden email]>
Betreff: AW: [Glass] Info on implementation limits

 

From replies off list, I heard, that big input files are not a problem. Good to know, thank you.

 

For the crash on the big method, I investigated and created an input file which reproduces the problem (attached as bigMethod.gs). The log is attached as well.

My theory was wrong. It seems not to be a problem with many literals in a method, but something else.

When I input the file in a Topaz shell (on windows), it works seamless and the method can be called.

Steps:

  1. Login to topaz
  2. enter ‘output push c:\image\bigMethod.log’[CR]
  3. enter ‘input c:\image\bigMethod.gs’[CR]
  4. all fine!

 

But if I do the same with a batch file which uses the script loadBigMethod.tpz (attached),

The Topaz window opens, it stays there for about 10 seconds (the step 3 above took no time) and the crashes (Windows pops up with “the program does not work anymore…” or something like that (I have a German version).

 

Any idea?

Thanks

 

 

Config data (running on Windows 10):

|    PROGRAM: topaz, Linear GemStone Interface (Remote Session)               |

|    VERSION: 3.3.5, Thu May  4 11:44:37 2017                                 |

|      BUILD: gss64_3_3_x_branch-41643                                        |

|  BUILT FOR: x86-64/Windows7                                                 |

|       MODE: 64 bit                                                          |

| RUNNING ON: 4-CPU haider-pc: Unknown CPU, Windows NT 6.2 build 9200         |

 

 

Von: Glass [[hidden email]] Im Auftrag von Dale Henrichs via Glass
Gesendet: Dienstag, 11. Juli 2017 18:20
An: [hidden email]
Betreff: Re: [Glass] Info on implementation limits

 

Christian,

Could you send me the full topaz log file? We need that to understand what might be going on ...

Thanks,

Dale

 

On 7/11/17 1:07 AM, Christian Haider via Glass wrote:

Hi,

 

are there any information about implementation limits of Gemstone Smalltalk?

 

Concrete issue:

I try to input a source file (2.1. MB – can this work?).

Topaz dies (Windows reports that Topaz is not working anymore…)

Last thing in the log file is a method with 743 literals – is this an issue?

My naïve theory: Gemstone (Topaz?) cannot compile the method, but dies without error.

 

Any ideas?

 

Thanks,

                Christian

 

 

_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass

 

 


_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass

PostScriptFontBody class-adobeZapfdingbatsTxt.st (4K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: WG: Info on implementation limits

GLASS mailing list



On 07/12/2017 07:11 AM, Christian Haider wrote:

Dale,

 

attached is the source method from VW – I found a much smaller one (4022 Byte literal string) with the same problem.

The setup is identical with the prior problem.

Thanks for the source ...

 

So, there are no simple answers to the limits questions?

I don't have the specific limits memorized and I have passed your questions along to folks who know where to look, however, they are more focused on trying to understand why the sessions disappeared without a trace ... I would have expected that you'd have gotten an error message if you exceeded any limits ...

Dale

 

Cheers,

                Christian

 

Von: Dale Henrichs [[hidden email]]
Gesendet: Mittwoch, 12. Juli 2017 15:50
An: Christian Haider [hidden email]; [hidden email]
Betreff: Re: AW: [Glass] WG: Info on implementation limits

 

Christian,

Can you provide more details, so we can try to check this one out? Log file, method source, etc.

Thanks,

Dale

 

On 7/12/17 6:18 AM, Christian Haider wrote:

Found another one (sudden death):

A method returning a literal 78 KB String.

What is the limit on the method source size?

Or, is there a limit for strings inside a method?

 

Cheers,

                Christian

 

Von: Glass [[hidden email]] Im Auftrag von Christian Haider via Glass
Gesendet: Mittwoch, 12. Juli 2017 11:37
An: [hidden email]
Betreff: [Glass] WG: Info on implementation limits

 

(resent, because Google blocked the attachment)

 

Von: Christian Haider [[hidden email]]
Gesendet: Mittwoch, 12. Juli 2017 09:53
An: '[hidden email]' <[hidden email]>
Cc: 'Dale Henrichs' <[hidden email]>
Betreff: AW: [Glass] Info on implementation limits

 

From replies off list, I heard, that big input files are not a problem. Good to know, thank you.

 

For the crash on the big method, I investigated and created an input file which reproduces the problem (attached as bigMethod.gs). The log is attached as well.

My theory was wrong. It seems not to be a problem with many literals in a method, but something else.

When I input the file in a Topaz shell (on windows), it works seamless and the method can be called.

Steps:

  1. Login to topaz
  2. enter ‘output push c:\image\bigMethod.log’[CR]
  3. enter ‘input c:\image\bigMethod.gs’[CR]
  4. all fine!

 

But if I do the same with a batch file which uses the script loadBigMethod.tpz (attached),

The Topaz window opens, it stays there for about 10 seconds (the step 3 above took no time) and the crashes (Windows pops up with “the program does not work anymore…” or something like that (I have a German version).

 

Any idea?

Thanks

 

 

Config data (running on Windows 10):

|    PROGRAM: topaz, Linear GemStone Interface (Remote Session)               |

|    VERSION: 3.3.5, Thu May  4 11:44:37 2017                                 |

|      BUILD: gss64_3_3_x_branch-41643                                        |

|  BUILT FOR: x86-64/Windows7                                                 |

|       MODE: 64 bit                                                          |

| RUNNING ON: 4-CPU haider-pc: Unknown CPU, Windows NT 6.2 build 9200         |

 

 

Von: Glass [[hidden email]] Im Auftrag von Dale Henrichs via Glass
Gesendet: Dienstag, 11. Juli 2017 18:20
An: [hidden email]
Betreff: Re: [Glass] Info on implementation limits

 

Christian,

Could you send me the full topaz log file? We need that to understand what might be going on ...

Thanks,

Dale

 

On 7/11/17 1:07 AM, Christian Haider via Glass wrote:

Hi,

 

are there any information about implementation limits of Gemstone Smalltalk?

 

Concrete issue:

I try to input a source file (2.1. MB – can this work?).

Topaz dies (Windows reports that Topaz is not working anymore…)

Last thing in the log file is a method with 743 literals – is this an issue?

My naïve theory: Gemstone (Topaz?) cannot compile the method, but dies without error.

 

Any ideas?

 

Thanks,

                Christian

 

 

_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass

 

 



_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass
Reply | Threaded
Open this post in threaded view
|

Re: WG: Info on implementation limits

GLASS mailing list
In reply to this post by GLASS mailing list

Christian,

From engineering:

   I suspect that topaz echo of output
  to stdout , when stdout is to a terminal is messing up the terminal
  when non-ascii characters are involved.  Workaround should be
  to use linux topaz  or  topaz input file and 
  output push only 
  to a log file (the useage style which he observes works correctly).

Dale


On 07/12/2017 07:11 AM, Christian Haider wrote:

Dale,

 

attached is the source method from VW – I found a much smaller one (4022 Byte literal string) with the same problem.

The setup is identical with the prior problem.

 

So, there are no simple answers to the limits questions?

 

Cheers,

                Christian

 

Von: Dale Henrichs [[hidden email]]
Gesendet: Mittwoch, 12. Juli 2017 15:50
An: Christian Haider [hidden email]; [hidden email]
Betreff: Re: AW: [Glass] WG: Info on implementation limits

 

Christian,

Can you provide more details, so we can try to check this one out? Log file, method source, etc.

Thanks,

Dale

 

On 7/12/17 6:18 AM, Christian Haider wrote:

Found another one (sudden death):

A method returning a literal 78 KB String.

What is the limit on the method source size?

Or, is there a limit for strings inside a method?

 

Cheers,

                Christian

 

Von: Glass [[hidden email]] Im Auftrag von Christian Haider via Glass
Gesendet: Mittwoch, 12. Juli 2017 11:37
An: [hidden email]
Betreff: [Glass] WG: Info on implementation limits

 

(resent, because Google blocked the attachment)

 

Von: Christian Haider [[hidden email]]
Gesendet: Mittwoch, 12. Juli 2017 09:53
An: '[hidden email]' <[hidden email]>
Cc: 'Dale Henrichs' <[hidden email]>
Betreff: AW: [Glass] Info on implementation limits

 

From replies off list, I heard, that big input files are not a problem. Good to know, thank you.

 

For the crash on the big method, I investigated and created an input file which reproduces the problem (attached as bigMethod.gs). The log is attached as well.

My theory was wrong. It seems not to be a problem with many literals in a method, but something else.

When I input the file in a Topaz shell (on windows), it works seamless and the method can be called.

Steps:

  1. Login to topaz
  2. enter ‘output push c:\image\bigMethod.log’[CR]
  3. enter ‘input c:\image\bigMethod.gs’[CR]
  4. all fine!

 

But if I do the same with a batch file which uses the script loadBigMethod.tpz (attached),

The Topaz window opens, it stays there for about 10 seconds (the step 3 above took no time) and the crashes (Windows pops up with “the program does not work anymore…” or something like that (I have a German version).

 

Any idea?

Thanks

 

 

Config data (running on Windows 10):

|    PROGRAM: topaz, Linear GemStone Interface (Remote Session)               |

|    VERSION: 3.3.5, Thu May  4 11:44:37 2017                                 |

|      BUILD: gss64_3_3_x_branch-41643                                        |

|  BUILT FOR: x86-64/Windows7                                                 |

|       MODE: 64 bit                                                          |

| RUNNING ON: 4-CPU haider-pc: Unknown CPU, Windows NT 6.2 build 9200         |

 

 

Von: Glass [[hidden email]] Im Auftrag von Dale Henrichs via Glass
Gesendet: Dienstag, 11. Juli 2017 18:20
An: [hidden email]
Betreff: Re: [Glass] Info on implementation limits

 

Christian,

Could you send me the full topaz log file? We need that to understand what might be going on ...

Thanks,

Dale

 

On 7/11/17 1:07 AM, Christian Haider via Glass wrote:

Hi,

 

are there any information about implementation limits of Gemstone Smalltalk?

 

Concrete issue:

I try to input a source file (2.1. MB – can this work?).

Topaz dies (Windows reports that Topaz is not working anymore…)

Last thing in the log file is a method with 743 literals – is this an issue?

My naïve theory: Gemstone (Topaz?) cannot compile the method, but dies without error.

 

Any ideas?

 

Thanks,

                Christian

 

 

_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass

 

 



_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass
Reply | Threaded
Open this post in threaded view
|

Re: WG: Info on implementation limits

GLASS mailing list
In reply to this post by GLASS mailing list



On 07/12/2017 07:11 AM, Christian Haider wrote:

Dale,

 

attached is the source method from VW – I found a much smaller one (4022 Byte literal string) with the same problem.

The setup is identical with the prior problem.

 

So, there are no simple answers to the limits questions?

From engineering:

  A string literal is limited to 5.2MB in 3.3.x .
  An array literal is limited to 10000 elements.

  compiled methods are limited by offset fields of branch
  bytecodes which cannot handle a branch displacement > +- 2e9 bytes.

Dale

_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass
Reply | Threaded
Open this post in threaded view
|

Re: WG: Info on implementation limits

GLASS mailing list
In reply to this post by GLASS mailing list

Thank you Dale!

 

I will try to run the input on the server.

For now, I deferred the issue, since I find it difficult to use topaz on the server with the devkit installation:

  • there is a startTopaz script in devkit, but it uses its own initialization file, i.e. I cannot use my own with -I
  • when I call topaz directly, it complains about missing libraries (probably some paths/variables required)

In the moment, I don’t have the patience to chase up the shell programming issues – I will come back to that later…

 

Thanks,

                Christian

 

Von: Dale Henrichs [mailto:[hidden email]]
Gesendet: Mittwoch, 12. Juli 2017 20:56
An: Christian Haider <[hidden email]>
Cc: [hidden email]
Betreff: Re: AW: AW: [Glass] WG: Info on implementation limits

 

Christian,

From engineering:

   I suspect that topaz echo of output

  to stdout , when stdout is to a terminal is messing up the terminal

  when non-ascii characters are involved.  Workaround should be

  to use linux topaz  or  topaz input file and 

  output push only 

  to a log file (the useage style which he observes works correctly).

 

Dale

 

On 07/12/2017 07:11 AM, Christian Haider wrote:

Dale,

 

attached is the source method from VW – I found a much smaller one (4022 Byte literal string) with the same problem.

The setup is identical with the prior problem.

 

So, there are no simple answers to the limits questions?

 

Cheers,

                Christian

 

Von: Dale Henrichs [[hidden email]]
Gesendet: Mittwoch, 12. Juli 2017 15:50
An: Christian Haider [hidden email]; [hidden email]
Betreff: Re: AW: [Glass] WG: Info on implementation limits

 

Christian,

Can you provide more details, so we can try to check this one out? Log file, method source, etc.

Thanks,

Dale

 

On 7/12/17 6:18 AM, Christian Haider wrote:

Found another one (sudden death):

A method returning a literal 78 KB String.

What is the limit on the method source size?

Or, is there a limit for strings inside a method?

 

Cheers,

                Christian

 

Von: Glass [[hidden email]] Im Auftrag von Christian Haider via Glass
Gesendet: Mittwoch, 12. Juli 2017 11:37
An: [hidden email]
Betreff: [Glass] WG: Info on implementation limits

 

(resent, because Google blocked the attachment)

 

Von: Christian Haider [[hidden email]]
Gesendet: Mittwoch, 12. Juli 2017 09:53
An: '[hidden email]' <[hidden email]>
Cc: 'Dale Henrichs' <[hidden email]>
Betreff: AW: [Glass] Info on implementation limits

 

From replies off list, I heard, that big input files are not a problem. Good to know, thank you.

 

For the crash on the big method, I investigated and created an input file which reproduces the problem (attached as bigMethod.gs). The log is attached as well.

My theory was wrong. It seems not to be a problem with many literals in a method, but something else.

When I input the file in a Topaz shell (on windows), it works seamless and the method can be called.

Steps:

  1. Login to topaz
  2. enter ‘output push c:\image\bigMethod.log’[CR]
  3. enter ‘input c:\image\bigMethod.gs’[CR]
  4. all fine!

 

But if I do the same with a batch file which uses the script loadBigMethod.tpz (attached),

The Topaz window opens, it stays there for about 10 seconds (the step 3 above took no time) and the crashes (Windows pops up with “the program does not work anymore…” or something like that (I have a German version).

 

Any idea?

Thanks

 

 

Config data (running on Windows 10):

|    PROGRAM: topaz, Linear GemStone Interface (Remote Session)               |

|    VERSION: 3.3.5, Thu May  4 11:44:37 2017                                 |

|      BUILD: gss64_3_3_x_branch-41643                                        |

|  BUILT FOR: x86-64/Windows7                                                 |

|       MODE: 64 bit                                                          |

| RUNNING ON: 4-CPU haider-pc: Unknown CPU, Windows NT 6.2 build 9200         |

 

 

Von: Glass [[hidden email]] Im Auftrag von Dale Henrichs via Glass
Gesendet: Dienstag, 11. Juli 2017 18:20
An: [hidden email]
Betreff: Re: [Glass] Info on implementation limits

 

Christian,

Could you send me the full topaz log file? We need that to understand what might be going on ...

Thanks,

Dale

 

On 7/11/17 1:07 AM, Christian Haider via Glass wrote:

Hi,

 

are there any information about implementation limits of Gemstone Smalltalk?

 

Concrete issue:

I try to input a source file (2.1. MB – can this work?).

Topaz dies (Windows reports that Topaz is not working anymore…)

Last thing in the log file is a method with 743 literals – is this an issue?

My naïve theory: Gemstone (Topaz?) cannot compile the method, but dies without error.

 

Any ideas?

 

Thanks,

                Christian

 

 

_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass

 

 

 


_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass
Reply | Threaded
Open this post in threaded view
|

Re: WG: Info on implementation limits

GLASS mailing list
In reply to this post by GLASS mailing list

Thank you for this helpful info!

I am relieved. I guess that I don’t have to suspect any problems in that area.

Thanks!

 

Von: Dale Henrichs [mailto:[hidden email]]
Gesendet: Mittwoch, 12. Juli 2017 21:50
An: Christian Haider <[hidden email]>
Cc: [hidden email]
Betreff: Re: AW: AW: [Glass] WG: Info on implementation limits

 

 

 

On 07/12/2017 07:11 AM, Christian Haider wrote:

Dale,

 

attached is the source method from VW – I found a much smaller one (4022 Byte literal string) with the same problem.

The setup is identical with the prior problem.

 

So, there are no simple answers to the limits questions?

From engineering:

  A string literal is limited to 5.2MB in 3.3.x .

  An array literal is limited to 10000 elements.

 

  compiled methods are limited by offset fields of branch

  bytecodes which cannot handle a branch displacement > +- 2e9 bytes.


Dale


_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass