[mapguide-internals] MapGuide 1.2 RC2 and King.Oracle memory leak

Haris Kurtagic haris at sl-king.com
Wed Jul 4 18:10:21 EDT 2007


Hi Tom,

I believe I mixed up things with Oracle libraries ( 10.2.0.3 and
10.2.0.1 ).
I hope I solved it with 0.7.1 version of provider

Thank you,
Haris


-----Original Message-----
From: mapguide-internals-bounces at lists.osgeo.org
[mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Tom
Fukushima
Sent: Tuesday, July 03, 2007 11:30 PM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] MapGuide 1.2 RC2 and King.Oracle
memory leak

Hi Haris,

The source for RC2 in the tar file is the same as the source used to
build the binaries.

RC1 was built on June 9th and RC2 was built on June 15th, so you want
changes that went in on the 9th up to the 14th.  You should be able to
query subversion to get these submissions.

I'm not sure if RC1 and RC2 are FDO binary compatible, so you may want
to recompile the SL-King provider with the latest FDO Core as well.  The
RC2 version is available using the 3.2.2 RC2 links at
http://fdo.osgeo.org/downloads.html.

Cheers
Tom

-----Original Message-----
From: mapguide-internals-bounces at lists.osgeo.org
[mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Haris
Kurtagic
Sent: Tuesday, July 03, 2007 10:11 AM
To: MapGuide Internals Mail List
Subject: [mapguide-internals] MapGuide 1.2 RC2 and King.Oracle memory
leak

HI,

 

I hope someone can give me some idea, I saw a ticket for memory leak in
RC2 and King.Oracle and I can reproduce it easily, it is very obvious.

 

Problem is that if I use same provider (same binaries ) in RC1 I can't
see a leak, also if I run provider on MapGuide RC2 which I build ( debug
and release) I also can't reproduce error.

 

Could be that posted release of RC2 ( windows installer ) and posted RC2
source are not the same ? ( Long shot question but it really looks
strange to me ).

How can I see which files has been changed from RC1 to RC2 ?

 

Also I done testing in Fdo2Fo and after fixing memory leak in Fdo2Fdo
itself which was general leak ( no matter of provider ) I also can't
reproduce it.

 

Thanks,

Haris

_______________________________________________
mapguide-internals mailing list
mapguide-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-internals

_______________________________________________
mapguide-internals mailing list
mapguide-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-internals


More information about the mapguide-internals mailing list