System Resources Exceeded error

Hello all! I’m working with a method that sits and waits for commands from a LIMS. The method is meant to run over the weekend, listening. This past weekend, we got a “System Resources Exceeded” error during a file open command. I’m wondering if anyone else has hit this type of error before. Attached is a relevant snippet of the logfile. There is also a “No Such Interface Supported” error from the Labware Access library, something I"ve never seen before.

Hamilton is also looking into it, but I wanted to know whether anyone had seen this so I an hopefully implement a fix before the holiday.


2024-11-24 08:14:07> SYSTEM : Execute method - error; An error occurred while running Vector. The error description is: C:\Program Files (x86)\HAMILTON\Library\HSLLabwrAccess\HSLLabwrAccess.hsl(843) : An error occurred while running Vector. The error description is: Unhandled exception. (0x2f - 0x1 - 0x7) (0x23 - 0x2 - 0x39) ,
2024-11-24 08:14:07> USER : Trace - complete; LabwareID: temp_Liconic_Movement, LabwareCode: MTP_8_NUNC_TC_SW_FB
2024-11-24 08:14:07> USER : Trace - complete; HSLExtensionsFramework warning: _Method::HSLExtensions::File::Delete: The file does not exist
2024-11-24 08:14:07> SYSTEM : Execute method - error; An error occurred while running Vector. The error description is: C:\Program Files (x86)\HAMILTON\stardust_STAR_Shared\libraries\HX_Stardust_Functions\HX_Stardust_Functions.smt(272, 1) : System resource exceeded. (0x23 - 0x2 - 0x39) ,
2024-11-24 08:14:07> USER : Trace - complete; Error in Config_Retrieve_Labware_Parameter. Value: MTP_8_NUNC_TC_SW_FB not found in labware CSV
2024-11-24 08:14:07> SYSTEM : Execute method - error; An error occurred while running Vector. The error description is: C:\Program Files (x86)\HAMILTON\Library\HSLLabwrAccess\HSLLabwrAccess.hsl(843) : An error occurred while running Vector. The error description is: No such interface supported (0x2f - 0x1 - 0x0) (0x23 - 0x2 - 0x39) ,

1 Like

Are you 100% sure you are closing your files? I have a vague vague memory of getting this error years ago. It might that or are you adding tons of labware to the deck over the method?

I’ll double checked looking for files being left open, but I didn’t find any. There is a lot of JSON manipulation too so un-released objects was a concern.

I am doing a lot of labware manipulation over the method. Labware is being added on the fly in order to support dynamic labware types. Do you know why that would affect “system resources”? I was under the impression that once the dynamic labware was deleted that it would be fully in the past…

Check that you’re on the newest JSON library. How many JSON files do you have open at the same time?

I did have an issue once with the XML library using the same file IO object and maybe it is a similar error. What happened then was the two files streams were interlaced then error’d, but I can’t remember if it was this exact error. I think that is fixed in XML, don’t know if it was ever a problem in the JSON library.

We add 100s of tubes dynamically at run time and haven’t gotten that but maybe you’re adding way more labware?

we use json file and ton of them. i have a json file with 10,000 line and never saw this error

1 Like

I try not to have very many open at a time, but I do cycle through a ton of them over the method. So if I were to ever forget to release, then it could result in a lot being open.

I’m basically working with a deck layout of only carriers. When labware comes out of an automated incubator, I create add it to deck in the location where it was placed by the iSWAP. Its never very much labware at one time, but since it’s a multi-day method it ends up being a lot of add/removes.

The update here though is that Hamilton provided me with a modified version of Run Control. It apparently makes it “LARGEADDRESSAWARE”, allowing for larger memory allocation. Running with this over the holiday weekend seemed to work, it ran about twice as long as it originally took me to encounter the error.

That just rejogged my memory, that’s the run control we used when we ran into this issue. Sorry to send you on a goose chase. I do remember this fixed our issue. Did they say what addresses are too long?