• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 54 subscribers
  • Views 1264 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Huge .sbl file

Brighton Feng
Expert 3410 points

One of my customer found a 1.99GB .sbl file in his project, which make the program loading/running very slow. After they deleted the file, the CCS becomes normal.

What is the .sbl file? Why it becomes so large? Should we manually delete it?

 Thank you very much!

  • 0
    TI__Guru**** 162255 points

    That is huge!  The sbl file is the codesense database file which is generated by the source scanner that is part of the CodeWright edtior in CCS.  You can delete the file.  CCS will create a new one.  If your customer finds that the file keeps getting huge they may need to turn off the codesense scanner in CCS.  There is an option to do that in the editor settings or you can just rename teh cwsense.dll file in cc\bin to something else.

    Regards,

    John

  • 0 in reply to JohnS
    TI__Genius 12670 points

    My customer just reported the exact same problem, see below. Do you have any additional information on what might cause this? The answer in this threas is helpful, but I wish there were a better tradeoff then just shutting off codesense. My customer will likely want to use this feature if the file doesn't seem to be growing so large. My concern is that if the problem happens again, the customer could go on for a while with a slow system before realising this is the cause. Anyway, let me know if any more info has become availeble.

    "Lately, every time I try to open a file in a CCS project, CCS would hang for what would seem like forever.  Matt noticed that that the .sbl file in the project directory was around 2GB in size (where it would normally be a few KBs) and suggested to delete it and see if that fixes the issue.  After continued testing, it looks like this issue is resolved."

    JohnS said:

    That is huge!  The sbl file is the codesense database file which is generated by the source scanner that is part of the CodeWright edtior in CCS.  You can delete the file.  CCS will create a new one.  If your customer finds that the file keeps getting huge they may need to turn off the codesense scanner in CCS.  There is an option to do that in the editor settings or you can just rename teh cwsense.dll file in cc\bin to something else.

  • 0 in reply to rperezti
    TI__Guru**** 162255 points

    Ruben,

    It is basically a bug somewhere in the CodeWright codesense source scanner that is building up its source info database.  It gets to some part of the code and gets stuck and adds a bunch of extra information to the database.  It is very hard to tell what source causes the problem as it doesn't jump right up to 2GB, it takes time for it to occur.  So there really isn't much of a workaround.  I guess you could get fancy and setup a final build step to delete the file or maybe something in the startup GEL file.  Startup GEL would likely be better, that way it gets clear each time you start CCS and quickly rebuilt but never gets out of control.

    John