Out Memory Error Powerbuilder
links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center. Forums Archive > PowerBuilder > DataWindow > "Out of memory when retrieving" Out of memory when retrieving 5 posts in DataWindow . Last posting was on 2010-08-19 04:54:02.0Z Jason L Posted on 2010-08-18 01:15:16.0Z Sender: 2cc8.4c6b3319.1804289383@sybase.comFrom: Jason LNewsgroups: sybase.public.powerbuilder.datawindowSubject: Out of memory when retrievingX-Mailer: WebNews to Mail Gateway v1.1tMessage-ID: <4c6b3424.2cdd.1681692777@sybase.com>NNTP-Posting-Host: 10.22.241.41X-Original-NNTP-Posting-Host: 10.22.241.41Date: 17 Aug 2010 18:15:16 -0700X-Trace: forums-1-dub 1282094116 10.22.241.41 (17 Aug 2010 18:15:16 -0700)X-Original-Trace: 17 Aug 2010 18:15:16 -0700, 10.22.241.41Lines: 9Path: forums-1-dub!not-for-mailXref: forums-1-dub sybase.public.powerbuilder.datawindow:91496 Article PK: 411097 Hi, Is there a limit on the number of rows retrieved for a datawindow? I have a datawindow with 3 nested datawindows and when i retrieve > 100k records it goes out of memory.Removing one of the nested datawindow however solves the problem. I have tried using the datawindow.storagepagesize = 'LARGE' setting but i get a smartheap error instead. I'm using PB 7.0.3. Please advice. Thanks. Jerry Siegel [TeamSybase] Posted on 2010-08-18 03:03:20.0Z From: "Jerry Siegel [TeamSybase]"
by cwong] I have read in some of the powerbuilder newsgroups that there are problems with memory leak. My application runs 24 hours a day and has many users. The application server has 512Megs of RAM. We are considering increasing that to 1GIG because we keep getting an out of memory error message. Your book says that the Web.PB cgi program is a memory hog. I have tried to use the Pbisa60.dll but I can't get it to work on our web server. Even though it is IIS on an NT machine. But we aren't getting the out of memory message on the web http://nntp-archive.sybase.com/nntp-archive/action/article/411102 server , it is on the application server. I have made sure that my application does a Destroy for every Create. Although I couldn't find a Create for my NVO and it does not have AutoInstantiate checked. I followed the example in your book for creating this NVO. PB6.5 is supposed to have automatic garbagecollection. I'm worried that perhaps the instances of my NVO are not being cleaned up. Should I https://forums.manning.com/posts/list/953.page put a Destroy or explicit garbagecollection call in the Connectionend script of my application? Thanks for all your help. This forum and your book have been invaluable. Catherine import-bot (20212) Offline May 27, 1999 @ 9:00 PM #2 Re: Out of Memory? [Originally posted by johnlatham] > I've also got a problem with my application slowly eating all of the memory on > an NT server. I am using IIS as the web server and ISAPI as the interface. > I've had a look at the memory management help that comes with PB and it is as > useful as "destroy objects before their instance variables go out of scope". > I've done this. It doesn't help. > I'd like to add my plea for help in tracking down memory leakage. Incidentaly, > the IIS installation on the server keeps dying (Dr Watson error) on > application inetinfo.exe. I suspect this is due to the memory problems of PB > but would like to hear if anyone has any other explanations. > Thanks. I forgot to add that my applications connection log shows a worrying amount of 'System Error 1004 - Null object reference'. I can't see a reason for this but suspect that it is involved in the memory leak
FORUMSFOR COMPUTER PROFESSIONALS Log In Come Join Us! Are you aComputer / IT professional?Join Tek-Tips Forums! Talk With Other http://www.tek-tips.com/viewthread.cfm?qid=418270 Members Be Notified Of ResponsesTo Your Posts Keyword Search One-Click Access http://www.powerbuildertv.com/index.php/en/archived-webinars/powerbuilder/272-best-practices-for-managing-exceptions-and-errors-in-powerbuilder-qaa To YourFavorite Forums Automated SignaturesOn Your Posts Best Of All, It's Free! Join Us! *Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail. Posting Guidelines Promoting, selling, recruiting, coursework and thesis posting is forbidden.Tek-Tips Posting Policies out memory Jobs Jobs from Indeed What: Where: jobs by Link To This Forum! Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.Just copy and paste the BBCode HTML Markdown MediaWiki reStructuredText code below into your site. Sybase: PowerBuilder Forum at Tek-Tips HomeForumsProgrammersDevelopment ToolsSybase: PowerBuilder Forum Memory use - smartheap error out memory error thread144-418270 Forum Search FAQs Links MVPs Memory use - smartheap error Memory use - smartheap error 2Fuzzy4U (Programmer) (OP) 2 Dec 02 05:04 Hi, Using PB 6.5 I'm trying to find out where all the memory goes. A window (containing 2 treeviews and 4 datawindows) looses memory until it crashes with a smartheap error. It doesn't retrieve to much rows and looses memory already with just the call of a function (arguments a handle and 2 datastores by reference).Any suggestions how what to look for? I'm running out of ideas. RE: Memory use - smartheap error tabhijit (Programmer) 14 Feb 03 20:26 Call Destroy If the datastore is created and call garbagecollect function.Abhijit. RE: Memory use - smartheap error 6112 (Programmer) 4 Mar 03 21:10 With 6.5, do not use SelectRow, ScrollToRow.. I found they have memory leaking in side. Addison Lu Red Flag This Post Please let us know here why this post is inappropriate. Reasons such as off-topic, duplic
PowerBuilderTV Account Contact Us The PowerBuilder Channel -Brought to you by Novalys Archives Archives PowerBuilder Best practices for managing exceptions and errors in PowerBuilder - Q&A Best practices for managing exceptions and errors in PowerBuilder - Q&A Details Created: Friday, 12 October 2012 08:19 You asked, he answered! Find below the questions and answers from Bruce Armstrong's (originally done by Oscar Tobar) presentation on Best practices for managing exceptions and errors in PowerBuilder. Q: Are there any performance benefits to using this?No. It does streamline the error handling and often allows you to handle recover from every handling earier. But it does nothing to improve performance. Q: Aren't you still going to end up with just as much code, just in a somewhat different order? (In fact, more code, because you have all those extra objects, e.g. your custom exceptions.) Not necessarily. Because you can move clean up logic (disconnect from database, destroy locally created objects) in the finally block, you can consolidate cleanup that might have to be repeated seperately without exceptions. However, the point of using an exception handling approach isn’t to reduce lines of code. The point is to streamline error handling. Note that you also don’t have to create the custom classes unless you want to trap for different specific exceptions from your code. You could simply create a local variable of type throwable or runtimeerror and throw that. Q: Stupid question: How does putting code in Finally differ from putting that same code immediately after End Try? Not stupid at all. First, code that comes after the finally block wouldn’t be executed if the routine raised an exception of its one. Secondly, you don’t normally have code after a finally section. The finally section in most cases would be the last part of the script. Q: Actually, RuntimeError has a lot more Properties than Throwable, so wouldn't it be better to inherit from it? Yes it would. For some reason I thought we ran into problems doing when we first started using it (on much earlier versions of PowerBuilder). Seems to work fine with 12.5. Runtimeerror does give you some additonal attributes (object, class, method, line of code). However, as I relate a bit further below, we simply added that information to the end of the error message. If you take that approach, I’m not sure basing the class on runtimeerror offers any advantage. The one case where it does make sense, brought up by another commenter below, is for those events (e.g., contructor, destructor) where PowerBuilder does not allow you to declare the exception type thrown by the script