Please wait a few minutes and refresh this page.
Today’s tip shows how to bring the picture into a drawing so that it is not a reference and is therefore one less file to have manage… If you have dragged and dropped the image into the drawing or used the OLE method, you realize that file is being referenced and therefore the separate picture file needs to be included when you send the file to the client. But there are some logos that are not so simple and therefore using an embedded image is preferred. It would be better to convert the logo into a block object by tracing over the image in AutoCAD and applying hatching as needed. For example, a client logo that needs to be part of the title block. Closing SOLIDWORKS and opening it will reset this count.There are times when an image needs to be included in a drawing. How can this problem be avoided? Do not keep your assemblies open unless you need them to be, and monitor your task manager periodically to see how many objects you are using. Over a long period of time this could reach the 10,000 mark, especially if you open the top level assembly.
After opening and closing a part several times with an assembly open and then closing all documents it still used 1401 objects. When I originally opened SOLIDWORKS it used 939 objects with no documents open. Here is a table of a session I recorded on my computer: Description The problem is only encountered when a part is open in an assembly and it is opened in its own window and then closed. SOLIDWORKS releases all handles every time. If a part is opened and closed several times the number of GDI objects it uses does not increase. Open task manager (you can right click on the task bar and click task manager).As it turns out it is actually very easy to monitor. But since there is a specific number at which it closes if you can monitor that number you can predict when it will happen. This is simply windows saying SOLIDWORKS is being too much of a resource hog and closes it to get those resources back.
This is not caused by unhandled code error or memory sharing issues or anything else that causes a crash. Since SolidWorks does not release all objects when a document is closed that number it uses continuously increases with each new document opened.Ĭan this be used to predict when SOLIDWORKS will crash? Predicting a SOLIDWORKS CrashĪs mentioned earlier this is not technically a crash, if SOLIDWORKS reaches the 10,000 object limit windows terminates the process. What does all this have to do with SOLIDWORKS crashing? Windows has a default limit that a single process can only access 10,000 GDI objects. The default behaviour now is to release those handles, however not all of them are released. It does not seem that a group exists for the objects or the GROUP command failed to work. Prior so SOLIDWORKS 2011 SP4 if a part was open in an assembly and its own window when that window was closed it would not release those GDI objects. After using the GROUP command in AutoCAD to group several objects together, when trying to select the group, the individual items within the group are selected instead of the entire group. GDI objects are used for the chrome of the graphics area, so every time a new document is opened the number of GDI objects used by SOLIDWORKS will increase. For maximum performance the Graphics area takes advantage of OpenGL which gives more direct access to the video processing hardware. GDI objects are used to draw window elements that are not in the graphics area in SolidWorks. What I am showing is not technically a crash, but to users of SOLIDWORKS the result is the same.