Results 1 to 2 of 2

Thread: Direct transactions not cleaned up

    Success! Looks like we've fixed this one. According to our records the fix was applied for EXTJS-4626 in a recent build.
  1. #1
    Ext JS Premium Member
    Join Date
    Oct 2010
    Vote Rating

    Default Direct transactions not cleaned up


    Ext version tested:
    • Ext 4.0.7

    Browser versions tested against:
    • Firefox 7.0.1 (FireBug 1.8.3 installed)

    DOCTYPE tested against:
    • <|DOCTYPE html>

    I have a problem where Ext.Direct.transactions is retaining information about every call, and so the memory is never free'd. In the case of a form the transaction entry contains a reference to that form, so this is even more memory that hangs around.

    Steps to reproduce the problem:
    • Use the console to show the value for Ext.Direct.transactions.length, which should be 0.
    • Issue an Ext Direct call and wait for the callback to complete so show the result has been processed.
    • Use the console to show the value for Ext.Direct.transactions.length, which will now be 1.

    The result that was expected:
    The transaction entry should be removed from Ext.Direct.transactions after the response has been handled.

    The result that occurs instead:
    Ext.Direct.transactions retains an entry for the transaction.

    Test Case:
    Not provided as it requires server-side code. I find this happens with any Ext Direct transaction.


    Screenshot or Video:

    Debugging already done:
    The onData() method of RemotingProvider calls on line 298. This in turn calls getTransaction(), which checks for an isTransaction property on the transaction object. Since there isn't one it performs another look-up which fails and returns undefined. If I call using the original value for the transaction object that's passed into removeTransaction() then the item appears to be removed as expected. I can't find the isTransaction property referred to anywhere else in the framework.

    In the forum I was asked: "Looking at line 293 of RemotingProvider.js where the line is right before the getTransaction... what is the event?"
    My response: "It's an instance of, where the action and method properties match the direct function I called. The type property is "rpc" and the status property is true."

    Possible fix:
    This was suggested as a work around in the forum and it works for me.
    Code: = function(transaction){
        return transaction.isTransaction || Ext.isObject(transaction) ? 
            transaction : 

    Additional CSS used:
    • default ext-all.css
    • some icons used on trees and tabs
    • an override for x-fieldset-header-text
    Let me know if you want the details but I think they're not applicable and would just bloat the report.

    Operating System:
    • WinXP Pro 64-bit

  2. #2
    Sencha User mitchellsimoens's Avatar
    Join Date
    Mar 2007
    Gainesville, FL
    Vote Rating


    Thank you for the report.
    Mitchell Simoens @LikelyMitch
    Modus Create, Senior Frontend Engineer
    Need any sort of Ext JS help? Modus Create is here to help!

    Check out my GitHub:

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts