X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-9.3 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SPF_PASS X-Spam-Check-By: sourceware.org From: Shailesh Dadure To: "cygwin AT cygwin DOT com" CC: "mtix AT chevron DOT com" Date: Tue, 14 Apr 2009 19:36:40 +0800 Subject: GREP: Memory Exhausted Message-ID: <28A2EAFEF380B447AF9E3FBFA6387D3189704E525F@AA-EXMSG-C425.southpacific.corp.microsoft.com> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Hello All, I am a support engineer from Microsoft trying to help my Customer Maziyar S= amadzadeh. We have been notified by Maziyar that when they perform a Query = on a bigger database using GREP we get the following error GREP: Memory Exhausted We have figured that at one point during the Query the application starts a= llocating memory drastically till we get this error. This happens probably = within 30 seconds. On Further research we found that the GREP application h= as same behaviour on UNIX and LINUX environment. This seems to be same on W= indows Environment too. However, in Windows the application cannot grow bey= ond 2GB so it crashes at that mark. Do we have any know issues with GREP. If Yes, has this been taken care in l= ater updates? Please update us regarding the issue as soon as possible. ------------------------------------------------------- Thanks and Regards, Shailesh Dadure Support Engineer=A0| Microsoft Enterprise Platform Support | Windows Server= Performance Team -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/