Hi Linas,
I also wanted to say how much I like the improvements you the OXID team have
made to the shop initialization process in 4.7.0. When tracing the new core
through a full page cycle in Eclipse, the new structure makes it a lot easier
to understand
what’s going on in the early phases,
Hi folks,
several times I ran into the same issue with continuously increasing
memory consumtion if I loop a huge list of e g. article ids like this:
foreach ( $aOXIDs as $sOxid ) {
$oArticle = oxNew('oxarticle');
$oArticle-load($sOxid);
}
even if I try to clone an object it will have just
Hi,
Did you try to use unset on the object to force garbage collection?
This is all part of the garbage collection,
and this can not be triggered without releasing all references.
best
Hi Alex,
and this can not be triggered without releasing all references.
and this is what I mean. The oxid framework knows (or should) which
instances have been created, so it should offer a possibility to clean
up the whole chain back imho.
Would be not so problematic if memory consumption
Hi,
my solution and I dont have any bad results by doing it this way:
$oArticle = oxNew('oxarticle');
foreach ( $aOXIDs as $sOxid ) {
$oArticle-load( $sOxid );
}
So, I init the object before the foreach and use the same object on every
foreach iteration.
Mit den besten Grüßen aus Lünen
i.
hi,
oxarticle stores reference to objects if it has variants. search for static
in oxarticle.php and write the module to unset from that array
Sent from Mobile.
André Herrmann andre.herrm...@fatchip.de wrote:
Hi,
I can remember that I tried it like this some time ago and it did not
work
Hi André,
I don't know if this helps in your case but as far as we investigated this:
when loading article lists OXID by default also loads the parent product
and all of the variants of the parent product (although you just wanted
to load the given variant). This eats up memory.
Fortunately
