I am totally with azslow3 on this, Alex.  I am also an IT professional.  I have owned my own business supporting other business IT infrastructures for the last 11 years.  I worked in corporate IT for 3 different companies for about 15 years in just about every position as well, and my degree is in Computer Information Systems (1989).
 
So we have now both marked similar territory.  This is not about my background or yours, but your statement that I didn't read your post and then stating "It can't be Sonar" is EXACTLY what I got from your post.  You were saying that it couldn't be Sonar, yet, I think your logic is completely wrong here, as stated by azslow3.
 
Maybe I'm just completely off-base on your Sonar bias.  I also choose this DAW over others, partly because I prefer the way it works, partially because this is what I invested my time in learning.  I only said this because there are often times on the forum that you tend to dismiss people's issues because you believe them to either not be real, the people to be incompetent, or their system to be flawed in some way that couldn't possibly include Sonar.  I understand that you are helping to build the list of others' experienced bugs and I respect the effort and how much time you spend here, but sometimes you just come off as a bit dismissive when it comes to people's issues.
 
No hard feelings :)

Blades
I only said this because there are often times on the forum that you tend to dismiss people's issues because you believe them to either not be real, the people to be incompetent, or their system to be flawed in some way that couldn't possibly include Sonar.

 
Not to speak for Alex, but the more time you spend on any forum like this, the more you run into people who clearly have not made even the most basic effort to solve their problem or describe it in sufficient detail to allow others to help. Fortunately, the Sonar forum is on a much higher level than most, and loaded with advanced users who really do know their stuff - as well as "newbies" who do try to figure things out for themselves before asking for assistance. But we are not immune to people who complain vociferously about some "horrible showstopper" Sonar flaw that turns out to be pilot error or a lack of understanding of the system (or computers in general).
 
We had quite a run of those people a few weeks back (or it may just have been one person with multiple alts and an agenda, who knows); for those here who genuinely try to help - and Alex is one of them - it's easy to lose patience given how many people are just going about their business making music with Sonar, sans drama.
 
This isn't to say at all that Sonar is without issues or potential incompatibilities. However, if you're into betting, you'd probably come out ahead if you bet that a "Sonar doesn't work! Software is broken!!!" thread was likely pilot error instead of a bug.
 
I'm not an IT professional, but I designed electronic projects that were sold as kits. Almost invariably, if someone sent in a kit for repair because the kit didn't work and said "I'm a professional engineer, and obviously something is wrong with your circuit, fix it or I'll report you to the Better Business Bureau" we could be pretty sure it was a cold solder joint or a diode put in backwards. On the other hand if the person said "Look, I'm new at this and I must have screwed up somehow because I've triple-checked everything and the circuit still doesn't work, I'm really sorry and can you please fix it" we could be pretty sure it was a bad part.
 
 
 
 
 

Another of my favorite Sonar stories was a review (in an actual print publication several years ago) that said Sonar was totally unacceptable for professional applications because the now time was often "off" by several samples compared to where it was supposed to be, making it "impossible" to set the now time on something like a precise measure boundary. So much for knowing enough to uncheck "Snap to nearest audio zero crossing"...

In the 30+ years of reading his bits, and building his stuff, I am now convinced that Craig is an alien.
 
He is everywhere, all the time
 
He knows everything before anyone else, even though he denies it, and it appears he is only "responding"   (time traveler, without doubt)
 
HE NEVER SLEEPS!!!!   ( proof: his post time stamps)
 
( My mother-in-law only slept about 4 hours a night.   I did not like her! )
 
My wife has eyelids thinner than properly-invisible slices of corned beef; Awake at dawn year round.  
 
( I need more beer.)
 
 
 
 
 
 
 

jm24
In the 30+ years of reading his bits, and building his stuff, I am now convinced that Craig is an alien.
 

 
https://www.youtube.com/watch?v=Nek43AmmtC8

He knows everything before anyone else, even though he denies it, and it appears he is only "responding"   (time traveler, without doubt)

 
https://www.youtube.com/watch?v=eDYkMiE_cTQ
 

CakeAlexS
I was doing a LOT of automated punch in/outs today and then all of the sudden the time line became jerky. I have no idea why. Not only that but volume knobs and loads of other controls became difficult to control (it was like the refresh rate was down to about 0.25 seconds). I was still able to carry on overdubbing but it was irritating.

The problem described here doesn't seem to be any way related to the disappearing now-line phenomena, with which there is no associated jerkiness or poor performance. When it occurs, the now-line in Track View becomes invisible, not only during playback, but totally for the remainder of the session, while everything else about Sonar continues to work normally. Closing and re-opening the project fixes the problem.

It may or may not be significant that I haven't experienced the problem lately, not since I recently updated my graphics card drivers. Anyway it seems to be purely a graphic issue.

Anderton
Another of my favorite Sonar stories was a review (in an actual print publication several years ago) that said Sonar was totally unacceptable for professional applications because the now time was often "off" by several samples compared to where it was supposed to be, making it "impossible" to set the now time on something like a precise measure boundary. So much for knowing enough to uncheck "Snap to nearest audio zero crossing"...

Yes... Very good example... I'm new to Sonar coming from Cubase and it took me half an hour to find out what was going on before I found "Snap to nearest audio zero crossing"... :-) At first I thought something was wrong but after some research found I was wrong myself. Most of the information is in the Help file.
 
I am application manager and more than once ask my customers very friendly to use the Help function of their application. The Help function in Sonar is a bit Old school but I like that and it is exellent! By the way... Cubase has the same option but it is switched off by default. Allso Cubase has imperfections but they are somewhere else in the program then in Sonar :-)
 
However... shortly I will do a few posts on things I cannot seem to find out. Allso application managers need help :-)

azslow3
And you still do not know what application can do to drive system crazy till it is rebooted? I do not mean bugs in the system, I mean wrong use of the system.
 
And if you think my question is theoretical, no. I was forced to work with one program which did that with graphic system. And many times with other system components as well. In one case you could simply wait 15 minutes before program restart instead of rebooting the computer, no system bugs involved, "following standards" pure (this example is from networking).

I do not claim there is this bug in SONAR. But I claim your statement is naive...

Sorry but what is a 'graphic system' or do you mean display adapter. What is 'bugs in the system'. What do you mean by an 'example from networking?' The drivers? The TCP/IP stack? What is a 'program restart' are you talked about processes? What specifically is a 'system bug'. What does 'driving the system crazy' mean? Is there voodoo somehow involved?

I suggest getting your terminology straight and getting a grip with the basics before coming up with a decent counter arguement that can be discussed in a sensible manner. The post is meaningless (what are you talking about?) and if you had read my post correctly, not relevant.

CakeAlexS

azslow3
And you still do not know what application can do to drive system crazy till it is rebooted? I do not mean bugs in the system, I mean wrong use of the system.
 
And if you think my question is theoretical, no. I was forced to work with one program which did that with graphic system. And many times with other system components as well. In one case you could simply wait 15 minutes before program restart instead of rebooting the computer, no system bugs involved, "following standards" pure (this example is from networking).

I do not claim there is this bug in SONAR. But I claim your statement is naive...

Sorry but what is a 'graphic system' or do you mean display adapter.

I mean Software Graphic System, which includes (graphic) driver, related OS components (core, window and desktop managers, etc.) and corresponding APIs.

What is 'bugs in the system'.

Either general mistakes in the framework concept or mistakes in concrete realization of that framework.

What do you mean by an 'example from networking?' The drivers? The TCP/IP stack?

I have not seen cases when waiting 15 minutes between closing and new starting of application could solve some problem in case the application had bugs in graphic related code. But I have seen that with network related programs. And yes, TCP/IP stack related. And I also think in case you have experience in network programming, you should understand why it is possible.

What is a 'program restart' are you talked about processes?

First closing some application and then starting it.

What specifically is a 'system bug'.

=='bug in the system'

What does 'driving the system crazy' mean?

When some particular application affect the (operation) system. Making it slow/unstable/crashing other applications.

Is there voodoo somehow involved? 

Computers are invented and implemented by normal people. No voodoo involved.
 

I suggest getting your terminology straight and getting a grip with the basics before coming up with a decent counter arguement that can be discussed in a sensible manner.

Too late, I have already written my previous post
 

The post is meaningless (what are you talking about?) and if you had read my post correctly, not relevant.

I have no problem with the fact that my post is meaningless and not relevant for you. But that was forum post, not PM.
 
Seriously, I know you really help many users and provide many informative statements. In that context you deserve big respect. But we all have bad days when we come to strange conclusions, using arguments like "my is bigger".
 
Reading your posts in this thread, I have understood you position as the following:
"In case program X has problem, but this problem disappear only after system restart and not after the program restart, the problem comes not from the program but from something else". I disagree with that statement. Taking your number of posts and activity, casual readers can accept your conclusion as a rule. That is why I have posted (with some explanation) my opinion.

Sorry I should not have come across as being negative here but I still don't see the point you are trying to make other than a list of generalistic symptoms and possible causes. You didn't troubleshoot the issue I did so it's hard for me to understand how you come to any conclusions, are you experiencing the issue? What were the steps you took to reach your conclusion? You say my conclusion is wrong but you don't really state clearly why it is wrong other than being pretty generalistic to be honest. You don't really provide any evidence or facts to draw your own conclusions on this specific issue.

I on the other hand troubleshooted a specific issue and managed to rule out that Sonar was being effected by something external to the application. I killed a number of processs in task manager and symptoms still persisted. Performance of the PC was fine. Furthermore it produced similar symptoms to what the op experienced. The time line was disappearing after a while and the symptoms would only clear upon a reboot. To come to a conclusion that Sonar is somehow at fault here would be totally wrong.

I wish I troubleshooted further to find out the root cause but did not have the time. Up until then I have never experienced such an issue and maybe I never will again. If I do I will be the first to post here. What I definately do know is this was some specific issue under the kernel most likely drivers, I would assume it would be my audio interface but that would be a speculation (something I try to avoid) not an actual conclusion. Of course it is possible it could be network related as well (I did say at or under kernel level didn't I?) , although I see it being extremely unlikely for the whole OS would have slowed down and other processes would have been seriously effected in this scenario. As Kev says it was not a performance issue. Oh and BTW I'm also keeping my eye on the mice drivers as that was a recent change to my system. Sure display drivers could be a factor as well.

BTW We all politely suggested to the OP that he updated his display drivers, even giving specific links, but all he did was complain about how busy he was (spending his time posting again and again here) and formed his own judgements without ruling it out so we gave up on him.