the weird thing happened, official 2.9 now works fine..i have no idea why. before it didn't work
but the version u gave me was bugged. it only draw on the top left corner. i have one 4k monitor and 2 hd

for me it my a15 always worked, until 2.9. and veikk didn't have any driver update.
it still work in 2.83 for me. so I'm not sure if it is purely viekk's problem.

In T80220#1008550, @Richard Antalik (ISS) wrote:

Do you have Veikk A15?

also i want to add
when your mouse goes from left node editor to right node editor the trigger area for resizing is only one pixel because it triggers scroll bar first, I think the trigger area for scroll bar should be further left, right now I think they overlap on top of each other

I do have enough ram, 32 gb in total.
did yours crash when pressing f12 in render mode?

i used normalize and it worked thanks

Btw it also happens on 2.80

hi, thanks for the reply, so u are saying that u didn't crash when painting. so how much memory were u using with my file. with file that small. using all 32gb of my memory is obviously a bug. the log file i acquired from the blender path file, along with other log files and .blend autosave. can this be the reason why i am crashing and using all my memory? one drive somehow messed thing up?

hi, i think i found the reason, eevee will crash when i turn on soft shadow, texture size and shadow map size will not affect anything. also i dont know how to save log, so i copied and pasted everything, but there is a portion at the top that got cut off, command prompt didnt show everything.
it looks like everytime the gpu usage dips down, the command prompt is showing the same group of text, then the gpu usage goes up to around 40%, at this time command prompt doesn't show anything. then it dips down and repeated the same lines.

i think i found out what the problem is. when i turn off the 28 light sources, eevee works fine. but when i turn them on, problem appears. gpu starts going up and down, blender freezes like i mentioned above.

I might have came out with some reasonable hypothesis

update: i get this viewport bug consistently when i try to rotate models in rendered view in cycles with one sample(or do anything that will update the rendered viewport like show or hide objects). it will lag then stop updating. the gpu usage and clock speed will spike up to max. then the top left where it shows all the calculations will say "canceled".

update: i upgraded my gpu ,cpu and ram problem stil exist.

{F7646522}some times it says this, illegal address