After running Matlab for a period of time, there will be a crash phenomenon. Call the solver to solve the optimization problem for a fee

[dpb]

This is indicative that there is a null pointer in the mex inteface code; not an unusual error for novices.

As the error message says, if it is not a MATLAB-included mex file, the problem is in the code and will have to be corrected there. However, nobody here will be able to point out the specific problem without the source code; attach it as inline text and format it with the Code button so it is easily readable. You'll likely have better luck if you can make the comments in English with there being a larger audience...

And, of course, when beginning with mex, first study the examples of passing data to/from MATLAB through the gateway routine for the various agument type(s) you are using. There is where most often the issues arise.

[zheng]

This mex file is inside the solver and I cannot access it.

[dpb]

Which specific mex file is that?

Without code of what you're trying to do to look at, nothing anybody here can do to diagnose anything...

[Steven Lord]

@zheng, did you delete or edit away the body of your question? dpb's first comment suggests that it originally included some information that might have helped us diagnose the problem, but without that information I doubt there's any useful suggestion that we can give you for how to resolve the problem.

[zheng]

No, this mex file comes with cplex and is difficult to edit. Its main purpose is to facilitate MATLAB's integration with it. Now I suspect that the crash was caused by continuous calls