Recent Posts

Pages: 1 ... 8 9 [10]
SlickEdit 2018 v23 Beta Discussion / rebuild slick c tag file got a stack error dump
« Last post by Graeme on October 17, 2018, 06:39:47 am »
My tag file had beta 5 files in it so I did rebuild all and got an error.
It worked the second time without an error.

Code: [Select]
Incorrect version
slickc.ex 6395 slickc:removeOldFiles(C:\SlickConfig\23.0.0\tagfiles\slickc.vtg,C:\Program Files\SlickEdit\Pro-23-0-0\\macros\)   p_window_id: 455   p_object: OI_EDITOR   p_name:
slickc.ex 7027 copyInstalledSlickCTagFile()   p_window_id: 459   p_object: OI_COMMAND_BUTTON   p_name: ctlrebuild_tag_file
slickc.ex 5880 _e_MaybeBuildTagFile(0,1,1)   p_window_id: 459   p_object: OI_COMMAND_BUTTON   p_name: ctlrebuild_tag_file
tags.ex 8939 MaybeBuildTagFile(e,1,1)   p_window_id: 459   p_object: OI_COMMAND_BUTTON   p_name: ctlrebuild_tag_file
tagform.ex 11993 TagRebuildAnyTagFile(C:\SlickConfig\23.0.0\tagfiles\slickc.vtg,e,0)   p_window_id: 459   p_object: OI_COMMAND_BUTTON   p_name: ctlrebuild_tag_file
tagform.ex 12625 _tag_form.ctlrebuild_tag_file.lbutton_up()   p_window_id: 459   p_object: OI_COMMAND_BUTTON   p_name: ctlrebuild_tag_file


I started to make a Java Project so I can see Live Errors. I think I ran into what you (Patrick) mentioned before:

I have found a bug with live error's jdk detection for openjdk 1.8 on linux that I need to work through.

In "JDK installation directory", I put the "bin" directory of my 1.8 JDK and also tried the parent dir of bin, and I get error: "Path to JDK 1.6 or later must be specified in order to use Live Errors". Is this the same problem you are tracking down?

I'm on RC1, Linux x64, CentOS 7.2
Fixed for RC2. This problem seems to occur with more than just Delete.
SlickEdit 2018 v23 Beta Discussion / Re: Bad crash with search
« Last post by Clark on October 17, 2018, 12:47:04 am »
I just tried this on a couple of my Windows systems. Looks like whatever algorithm Windows previously used is different now. I was able to allocate 16gig on my 16gig Windows 7 system. On my 8gig Windows 10 system, I was able to allocate 27gig. On older Windows OSes the OS would never let you allocate more than 1/3 of the total memory available.

In any case, it would be a good idea to try a much smaller buffer cache size to see if that fixes the problem. I'm still very suspicious.
Following up to say that my case was also fixed in RC1.  I've been using it all day without any issues so far.  Thanks!
Untar attached file.

With a clean config, go to Smart Open, right click at the top and check "Date modified" so that the date modified is showing.

Now go to the directory containing the hi.txt directory. Notice this directory has a date - 181012-1602.

Right click on hi.txt and choose "Delete". It gets the filename wrong in the dialog box, says: "Delete file '.../deletefileissue/181012-1602   2018-10-16T20:00:58hi.txt'". The delete then fails because smart open got the file name wrong.

Similar issue occurs when trying to rename the file. The filename populated in the Move/Rename Files dialog box is not correct.

RC1, Linux x64, CentOs 7.2
SlickEdit 2018 v23 Beta Discussion / Re: Bad crash with search
« Last post by Clark on October 16, 2018, 11:07:24 pm »
write a small 64-bit C++ app which calls malloc and attempts to allocate 8gig. It will fail. I think 4gig will work. It’s a very interesting exercise.

Let’s say the max memory the OS will give SlickEdit is 4gig. You can’t give all 4gig to edit buffers. Hope this all makes sense.
SlickEdit® / Re: Colored build output - a simple solution?
« Last post by Graeme on October 16, 2018, 10:47:44 pm »
Can you explain how you want the output coloured with some examples?
If slick regular expressions can find errors and warnings then it's not hard to colourize I suspect - assuming the output buffer is a normal read / write buffer.
SlickEdit 2018 v23 Beta Discussion / Re: Bad crash with search
« Last post by jporkkahtc on October 16, 2018, 10:39:20 pm »
Encoding: LF ACP
Extension: .log
I have 16GB of actual ram.

When I load the files in Slick, the Slick memory size tops out at around 8GB - just as I would expect.

Why would I need 32GB?
If I was running out of memory, then it should start swapping - so performance would get really terrible, but it shouldn't crash.

I wasn't running into problems with system memory - well, some apps are getting slow, but not really terrible like things get when the system is swapping like crazy.
Pages: 1 ... 8 9 [10]